Authored by Preetam De, a blogagility.com contributing author.
In the last few days several people have asked me a question about stretched targets on Scrum sprints – not sure if it was a co-incidence or an ongoing vibe. So I will take a moment to explain it.
This article will not revisit the negative consequences in detail of having a stretch target. I will assume the obvious with a quick recap, so I can focus on the solution in detail rather than discussing the problem.
Quick Recap – Why do we think we need it?
- When we feel the need to manage a person rather than the work they do.
- When we focus on Efficiency over Effectiveness.
- When we focus more on tools and practices more than the principles behind them.
- To impress stakeholders they need everything “right now”
- To impress authority by over-estimating our capabilities
- When we assume – “What happened last sprint won’t happen again”
- When we don’t trust a team member and say “We need to keep them busy”
How can we avoid Stretch Targets?
A) By focusing on the flow of work that matches the business need Read the rest of this entry »
My client has been working hard to implement the Lean Portfolio Management functions of the Scaled Agile Framework. Part of that process is to identify value streams flowing through the organization and begin the process of identifying the work that is on the streams. The value streams were identified well over a year ago. The process of researching, analyzing and identifying all of the work has been challenging, but very fruitful. Read the rest of this entry »
Aside Posted on Updated on
I was just having a bit of fun this morning, but perhaps there is some way to enhance our learning?
From my original LinkedIn post.
“Business Value Bowling” everyone is ten pins and one frame away from accurately assessing business value at the end of the PI!
The Laws and the rules
“The average number of work items in a stable system is equal to their average completion rate, multiplied by their average time in the system.” ~ John Little, 1961
“A Proof for the Queuing Formula” by Little, J. D. C. (1961)
Aside Posted on
Thinking this morning about a conversation I had yesterday at happy hour with several truly impressive human beings.
Some characteristics of a high performance Lean-Agile team:
- no longer needs a scrum master or lean agile leader
- uses the best of Scrum as an empirical framework for an amazingly lean sustainable flow process
- also uses principles of Lean and a Kanban system
- has a natural affinity for pulling the right work at the right time
- possesses high trust within the team and externally known to consistently deliver successful outcomes; builds trust with other teams
- regularly pushes the boundaries of what is possible as innovators
- cares deeply about people and the organization
- committed to continuous learning and relentless improvement