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!
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
Just in from the blogagility.com laboratory...
One of the many challenges faced by coaches in a Lean-Agile transformation is convincing resource owners/managers to relinquish the “control” part of command & control (see Capt. David Marquet on “Greatness”) to people & teams for the purposes of –self-organization & self-management. Or as I prefer to describe it, getting out of the way of people’s innate creativity and ability to innovate. Capt. Marquet offers pillars of competence and clarity as the recipe, of which I wholeheartedly agree.
As in the value systems of Scrum and the SAFe® – respect for people and culture, openness, and transparency are part of the fresh culture we are driving. Without these basic human elements of successful relationships and communication, trust doesn’t exist. The dual combo “T’s” of trust and truth are the kingpins in any long-lived organizational change / transformation. Read the rest of this entry »
If you are a coach, scrum master or team having trouble with sizing your user stories and consequently estimation of effort and collaboration in story points (volume, knowledge, complexity, uncertainty, dependencies, risk) try out the triangulation technique. This technique also works for no-estimate teams operating in non-enterprise environments. Additionally, teams that experience significant changes in velocity from iteration to iteration or story point inflation may need to use this calibration technique. Read the rest of this entry »