“Whenever you’re thinking high level, someone will bring you down to earth and ask you to get into the weeds. Whenever you’re in the weeds, someone will complain that you’re not being high level enough. It’s the burden we bear. Just when you think you’ve figured things out, you’ll encounter a person who needs to see your roadmap, or backlog, or “sprint backlog”, or “project”, or “plan” in a whole new way. So…changing delivery based on context is important. You could argue that it is the biggest challenge facing PMs. It is a design problem!” “11 Ways I Visualize Product Development Work” @johncutlefish
Success is not measured by points or project management type metrics; it’s measured by ‘is the organization meeting its purpose’ Tom Poppendeick
found at Twitter by @johncutlefish
found at Twitter @johncutlefish
Uncertainty is something we try to avoid – whenever possible. We want to know what we need to know, to be able to come up with reliable plans. Plans are supposed to keep deviations away from us, as they could make us struggle. Uncertainty can be seen to impose scepticism, doubt, mistrust. But it is always there and cannot be neglected, so we should anticipate it in favor of more robust plans.
When I was starting with agile teams many years ago, my main motivation has been to create more robust delivery processes. When I was looking at the findings, I was realizing, that I was not able to drive change by myself, so my motivation changed to empower the people in the teams to take actions on themselves. Now I realize, that my motivation has to be to foster a joint understanding of values and create room for the teams to take actions. Agile tools belong to the teams and not to me.
Agile methods are getting more and more grip in a fast-paced business world – mainly because they promise easy adaptation to change. But listening to people working in such agile setups, quite often they suffer from it than that they benefit. Why?