Learn about the 12 common misconceptions about Product Owner. are you a victim of any of these misconceptions?
The current version of The Scrum Guide is getting updated. Here are the things I wish the new updates could address (a) Daily Scrum (b)Development Team (c) Product Owner (d) Sprint Backlog and incomplete PBIs at the end of the Sprint (e) Acceptance of Work by Product Owner (f) Increment (g) What is the Product
Scrum does not define a "product", and how you define your "product" has huge implications for the organization. Broader definitions of product
(a) focus on solving actual customer problems
(b) avoids local optimizations in the organization
(c) eliminates management of dependencies between different micro- "products"
(d) and hence enables organization to "be more agile"
Learn how to spice up your Daily Scrum
I have my own biases, having seen co-located teams work very well and having struggled with "dislocated" teams, I often recommend my clients to reconsider "dislocated" teams. And by "dislocation" I am not saying you cannot have teams ten time zones away. What I mean by a "dislocated" team is when three team members are… Continue reading Remote Teams and Virtual Facilitation
"Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team." - The Scrum Guide. When the whole Scrum Team is self-organizing (in addition to the Dev. Team being self-organizing in executing the Sprint Backlog), understanding the context of Product Owner -… Continue reading [Product Owner – Dev. Team] Ladder of Empowerment
Someone asked me this question in LinkedIn "In your opinion, how do you measure a scrum master’s performance?" There are some good answers in the comments, and I thought I will elaborate on my perspective a bit more. To answer this question, we have to understand the dimensions of Scrum Master's work and the context under… Continue reading Measuring the Performance of a Scrum Master