Will all improvement ideas from a retrospective consume capacity?
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
The Scrum Guide indicates "The Scrum Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint."
During a class which I was teaching this week, one of the learners asked: "Won't the ideas from a retrospective use up some of the team's capacity in the next sprint?".
As usual, it depends.
Here are a few scenarios and I'm sure there are many others.
If an improvement idea requires the team to learn a new skill or to perform a task which they wouldn't have done otherwise, then yes, it will consume capacity in the next sprint. Teams which aspire to be as transparent as possible will make these types of ideas visible to all stakeholders by explicitly adding them into the sprint backlog. When deciding on whether to implement these ideas, the team should balance the capacity costs against the potential delivery, quality or happiness benefits.
For those ideas which relate to improving behavior or interactions within the team or with the stakeholders supporting the team, there might be no capacity impacts beyond the team figuring out how they will remember to behave in a different manner. If the team was used to working virtually but saw some benefits in face-to-face interactions at least once a week, they could do so without reducing available capacity.
Some suggestions might require work effort from those outside of the team. For example, a dedicated testing environment might be desirable to reduce the impacts of limited access to a shared environment. An external person might provision the environment hence there would be no capacity impacts for the team beyond confirming that the new dedicated environment was setup correctly.
Finally, other suggestions might change the effort required to complete work items. If the team enhances their Definition of Done to include more criteria to improve product quality, this might increase their effort per work item.
Regardless of the nature of the improvements, there is a critical difference between retrospectives and traditional lessons learned practices. With the latter, only a small fraction of what was identified is immediately applicable, whereas with the former, the majority of the vital few ideas identified should get implemented before attention shifts and memories fade.
Thanks, Deepak, for inspiring this week's article!
Posted on: November 18, 2018 07:00 AM |
Permalink
Comments (11)
Please login or join to subscribe to this item
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates
New Westminster, British Columbia, Canada
Good points Kiron and interesting question indeed raised by the class.
Thanks Rami - that's what I love about teaching - even if it's a course I've delivered many times in the past, the learners always find a way to ask the most interesting questions and force me to think!
Drew Craig
Sr. Agile & Product Coach| Vanguard
Philadelphia, Pa, United States
Thanks, Kiron. Good points.
Anish Abraham
Privacy Program Manager| University of Washington
Auburn, Wa, United States
Good one, Kiron and thanks for sharing.
RAJESH K L
Project Manager, PMP| Bharat Electronics, Bengaluru, India
Bengaluru, Karnataka, India
Kiron, Interesting post. Thanks for sharing
Interesting insight Kiron, keep it coming.
My understanding of Agile practice is that the pace should be sustainable. If this is the case, then the team should include a bit of each sprint specifically to allow for the implementation of improvements identified in the previous retrospective. Is that correct or am I overthinking things?
Please Login/Register to leave a comment.
|
The only people who find what they are looking for in life are the fault finders.
- Foster's Law
|