Player FM 앱으로 오프라인으로 전환하세요!
"Agile Signaling" is Gaslighting The Tech Industry
Manage episode 429457948 series 1756036
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
168 에피소드
Manage episode 429457948 series 1756036
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
168 에피소드
همه قسمت ها
×플레이어 FM에 오신것을 환영합니다!
플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.