If you carefully study Agile Manifesto and the principles behind it, you can classify them broadly as two groups, product-value delivery and internal working of the team/organization when building the product. The two major ideas in the "product-value delivery" group would be "deliver high value frequently" and "welcoming change/responding to change" Viewing it through the… Continue reading Scaling Scrum: Agility and Value Delivery is a “learning problem” – Part 1
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”?