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"
The concept of "undone" work does not exist in Scrum today, but nevertheless, it makes sense to understand this concept when Scaling Scrum . Most people confuse incomplete work and "undone" work. To understand the difference, please see here. Ideally, you should be able to get to a perfect definition of Done before your first… Continue reading Understanding “undone” Work
Every Sprint, the Development Team is responsible for building a "releasable" Product Increment. The Product Owner may choose to release it or may not choose to release the Increment at the end of the Sprint. Scrum does not prescribe a release frequency (i.e. PBIs can be released multiple, times a day, once a Sprint, once… Continue reading This is how you hit the ball out of the park in your first Sprint
All work that needs to be done by cross-functional (Product) Development Team is in the Product Backlog. Each item in the product backlog (product backlog item, PBI for short) is expressed in a way such that the value of PBI is transparent to the Product Owner. During the Sprint, the Development Team works on the… Continue reading Scrum: What is the difference between “Undone Work” and “Incomplete Work”?