Artwork

محتوای ارائه شده توسط Jayme Edwards. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Jayme Edwards یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
Player FM - برنامه پادکست
با برنامه Player FM !

"Agile Signaling" is Gaslighting The Tech Industry

22:16
 
اشتراک گذاری
 

Manage episode 429457948 series 1756036
محتوای ارائه شده توسط Jayme Edwards. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Jayme Edwards یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal

Today most tech companies engage in agile signaling - without even knowing it. They do nothing to make it easy to adapt to change, but put on a show to pretend they're agile.

Many software developers and other professionals in the industry, even those with long careers, have never been on project with a truly agile software development process. And so it's not uncommon to hear software engineers and project managers talk about how much they "hate agile" behind closed doors.

A select few understand what being agile really means. It means working together in a way where adapting to change is easy. For those unfortunate people, it can feel like gaslighting to work for these companies. Tech workers all over the industry are expressing more disgust with scrum and agile than ever. And when the SAFe, or "Scaled Agile Framework" arrived - it signaled a final nail in the coffin of many companies ever being able to realize the true benefits of being agile.

In this episode I'd like to help you understand two things. First, we we need agile development more than ever today. With the arrival of AI, software projects are getting disrupted faster than ever and need to adapt. And who knows what the future could bring! I'll also help you understand 4 key events in the history of the software industry that caused the definition of the word agile to essentially mean "anything BUT change"!

Join my Patreon: https://thrivingtechnologist.com/patreon

Learn about one-on-one career coaching with me: https://thrivingtechnologist.com/coaching

TechRolepedia, a wiki about the top 25 roles in tech: https://thrivingtechnologist.com/techroles

The Thriving Technologist career guide: https://thrivingtechnologist.com/guide

You can also watch this episode on YouTube.

Chapter markers / timelinks:

(0:00) Introduction (1:31) 1. Do We Even Need Agile Development? (1:37) 1.1 Inability To Respond To Market Change (3:55) 1.2 Over Budget and Late Projects (5:50) 2. 4 Key Events That Co-Opted Agile (6:16) 2.1 Burn-Down Charts and Velocity Tracking (9:21) 2.2 Jeff Sutherland's Book (12:47) 2.3 Agile Certifications (15:51) 2.4 SAFe (Scaled Agile Framework) (21:12) Episode Groove

Visit me at thrivingtechnologist.com

  continue reading

168 قسمت

Artwork
iconاشتراک گذاری
 
Manage episode 429457948 series 1756036
محتوای ارائه شده توسط Jayme Edwards. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Jayme Edwards یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal

Today most tech companies engage in agile signaling - without even knowing it. They do nothing to make it easy to adapt to change, but put on a show to pretend they're agile.

Many software developers and other professionals in the industry, even those with long careers, have never been on project with a truly agile software development process. And so it's not uncommon to hear software engineers and project managers talk about how much they "hate agile" behind closed doors.

A select few understand what being agile really means. It means working together in a way where adapting to change is easy. For those unfortunate people, it can feel like gaslighting to work for these companies. Tech workers all over the industry are expressing more disgust with scrum and agile than ever. And when the SAFe, or "Scaled Agile Framework" arrived - it signaled a final nail in the coffin of many companies ever being able to realize the true benefits of being agile.

In this episode I'd like to help you understand two things. First, we we need agile development more than ever today. With the arrival of AI, software projects are getting disrupted faster than ever and need to adapt. And who knows what the future could bring! I'll also help you understand 4 key events in the history of the software industry that caused the definition of the word agile to essentially mean "anything BUT change"!

Join my Patreon: https://thrivingtechnologist.com/patreon

Learn about one-on-one career coaching with me: https://thrivingtechnologist.com/coaching

TechRolepedia, a wiki about the top 25 roles in tech: https://thrivingtechnologist.com/techroles

The Thriving Technologist career guide: https://thrivingtechnologist.com/guide

You can also watch this episode on YouTube.

Chapter markers / timelinks:

(0:00) Introduction (1:31) 1. Do We Even Need Agile Development? (1:37) 1.1 Inability To Respond To Market Change (3:55) 1.2 Over Budget and Late Projects (5:50) 2. 4 Key Events That Co-Opted Agile (6:16) 2.1 Burn-Down Charts and Velocity Tracking (9:21) 2.2 Jeff Sutherland's Book (12:47) 2.3 Agile Certifications (15:51) 2.4 SAFe (Scaled Agile Framework) (21:12) Episode Groove

Visit me at thrivingtechnologist.com

  continue reading

168 قسمت

すべてのエピソード

×
 
Loading …

به Player FM خوش آمدید!

Player FM در سراسر وب را برای یافتن پادکست های با کیفیت اسکن می کند تا همین الان لذت ببرید. این بهترین برنامه ی پادکست است که در اندروید، آیفون و وب کار می کند. ثبت نام کنید تا اشتراک های شما در بین دستگاه های مختلف همگام سازی شود.

 

راهنمای مرجع سریع