Agile On The Skids
Greg Tutunjian
I help people improve their performance in the workplace and gain greater fulfillment from the experience.
On The Skids: failing or getting worse: in a bad state or situation that is likely to result in failure (Merriam-Webster Dictionary)
I read The State of Agile Report focusing on where responders share their challenges with Agile.? (I’ve read each edition and many of them more than once.) I follow other Agile, DevOps, and related reports (and will share my experiences with them here in the future.)
The sections of this report I’m most interested in used to be called Barriers and Challenges. These data are indicative of:
Whether these are truly immovable, unexpected, and hostile (and why) is what I’m focused on in addition to developing effective remediation strategies.
I summarized the most recent 5 reporting years of Barriers and Challenges to identify the Top 5, above. (Note: Leadership Participation has only been “surveyed” for the past 4 reporting years.) I made some assumptions based on experience and common use of industry terminology to associate report data with these themes:
Why Are These the Top 5?
My theory:
领英推荐
Top, Some Middle, But Little to No Down
I’ve repeatedly found management and leadership making key decisions (and assumptions) impacting these five areas without engaging their teams or others impacted. Some examples:
Food For Thought
When Resistance to Change is the leading Barrier or Challenge to effective Agility year over year, management and (especially) leadership should:
Future Planning
I’m barely scratching the surface so far (and there’s more than one surface and much more scratching, digging, and advocating ahead.) Share your impressions, thoughts, and recommendations. I plan to expand on the Top 5 individually and then their inter-relationships.
Cheers,
Greg
Change Manager ? Program Manager ? Process Improvement Specialist ? Insurance ? Banking ? Healthcare ? Technology ? #EngageForAdoption
10 个月Thank you for underscoring the importance of change management, Greg. Agile transformation is properly a change effort, not just an IT or project management effort. Change management recognizes each of your top five challenges and has tools to address them. I would also add that some executives ordered up agile transformations without recognizing the fundamental changes they would bring to organizational structure, values, and culture -- and then balked at those changes. In short, a true agile transformation must address change in attitudes and behaviors at all levels of the organization.
Business Strategist. Focus on Community Building and health. Synthesizing digital and traditional tools of communications. Human translator for the strategic power of vCON | SCITT
10 个月top management buy in will set the pace. Looking forward to you diving deeper as all of the top 5 reasons resonate!
Agile Coach / Scrum Product Owner / Agile Scaling Professional. Product-Focused & Customer-Centric | Passionate About AI & Product Management to Drive Innovation, Empower Teams, and Accelerate Business Growth
10 个月I've noticed a common issue why teams face challenges and quite frankly give up, mostly due to top management resisting Agile, (e.g., fearing loss of control and or doubting its benefits). This resistance spreads through the organization, holding back Agile adoption. To make matters worse, middle managers micromanage Agile teams, killing their creativity. And, without strong leadership support, Agile doesn't deliver the value promised. I believe bringing leaders on board is key for success (and leadership touches on all 5 issues you report in your article), shaping company culture and management style. I agree that overcoming resistance is crucial for Agile to work. Thank you for sharing your insights and your point about teams accepting this stall as normal hits home, it's a deep-rooted issue that needs a people-first approach to fix.?
Agile Consultant, Software Marketing and Communications and Adjunct Professor at Boston College
10 个月Greg, you're absolutely right about the importance of upfront engagement and buy-in. People are more likely to embrace change when they understand the reasons behind it and feel like they have a voice in the process. Creating a "safe to fail" environment is also crucial. Agile thrives on experimentation and learning from mistakes and we need to let teams know that it's OK if the first few sprints don't go as well as planned. Without that psychological safety, teams become hesitant and less innovative and tend to stall. Great insights, keep them coming!