What are the tipping points for your agile transformation?
From the Easy in theory, difficult in practice Blog
by Kiron Bondale
My musings on project management, project portfolio management and change management.
I'm a firm believer that a pragmatic approach to organizational change that addresses process & technology, but primarily, people will maximize chances for success.
This blog contains articles which I've previously written and published as well as new content.
Recent Posts
Leading Through Crisis Means Leading Through Context
"It's the end. But the moment has been prepared for." - retirement lessons from the Doctor
Just because they are non-critical, doesn't mean they are not risky!
Just because they are non-critical, doesn't mean they are not risky!
How will YOU avoid these AI-related cognitive biases?
Categories
Agile,
Artificial Intelligence,
Career Development,
Change Management,
Communications Management,
Decision Making,
Governance,
Hiring,
Kanban,
Lessons Learned,
Personal Development,
PMO,
Portfolio Management,
Project Management,
Resource Management,
Risk Management,
Risk Management,
Schedule Management,
Scheduling,
Tools
Date
I've frequently said that agile transformations are marathons and not sprints. But when someone runs a marathon there are mile markers to understand how far they've come and to help them get their second (or third or fourth) wind.
While there is no single model for how a company will progress through its agile transformation, it is a good idea for transformation teams to proactively identify tipping points where previously unique outcomes or behaviors have become commonplace. While such milestones won't help them forecast how much longer it might take to reach their ultimate goals, it can provide a leadership team with proof that things are continuing to move in the right direction. Such evidence is critical if there is to be sustained commitment and investment in the transformation.
This list is not exhaustive nor is it in chronological order. Depending on what the starting point is for the organization and where the transformation team chooses to focus their efforts, there may be additional milestones and the sequence of when those are accomplished will vary.
- Team social pressure encourages appropriate agile behaviors without the need for sustained external coaching
- Delivery frequency matches stakeholders' change appetite
- Zero defects
- Empowered Product Owners with sufficient capacity, capability, knowledge and influence
- Team allocation shifts from maximizing utilization to maximizing value delivered
- You don't hear team members say "the business" anymore (we are all "the business"!)
- Pivots in product or solution direction are praised, not punished
- Teams provide accurate and current updates to information radiators and stakeholders effectively pull information from those radiators
- There is NO one size fits all for ceremonies, practices or tool
- Overtime and weekend work is the exception not the rule
- Hiring practices and performance measurement systems emphasize the "how" as much as the "what"
What would you add to this list?
Posted on: November 04, 2018 07:00 AM |
Permalink
Comments (10)
Please login or join to subscribe to this item
Drew Craig
Sr. Agile & Product Coach| Vanguard
Philadelphia, Pa, United States
Thanks, Kiron. Strong list. I'd suggest having an established safety zone.
Thanks Andrew - evidence of widespread psychological safety within teams is certainly a significant accomplishment!
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates
New Westminster, British Columbia, Canada
Good Points Kiron but I am not sure about the Zero Defects point because to achieve Zero Defects which is more than 6 Sigma, it will be extremely costly. What’s your thoughts ?
RAJESH K L
Project Manager, PMP| Bharat Electronics, Bengaluru, India
Bengaluru, Karnataka, India
Thanks Rajesh!
Rami, zero defects is achievable in certain industries such as software development once development and quality practices have matured sufficiently. I'd agree that in some other industries the cost might be too high to justify the people/process/technology changes required to achieve this.
Kiron
Anish Abraham
Privacy Program Manager| University of Washington
Auburn, Wa, United States
Good one, Kion and thanks for sharing.
I would agree that social pressures need to replace coaching over time, which is a good way for Agile behaviors to sink into the collective mindset.
Very interesting, thanks for sharing
Pench Batta
Enterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.
Bentonville, Ar, United States
Kiron, Excellent insights! Thanks for sharing.
I would add the Product Owner needs to have the ability to sell/influence.... get past the logic center of the brain and to the limbic center -- tell/sell the story to make it to the next level.
Please Login/Register to leave a comment.
|
"If they have moving sidewalks in the future, when you get on them, I think you should have to assume sort of a walking shape so as not to frighten the dogs."
- Jack Handey
|