I was asked this question today and I think there is a clear answer, however it may change depending on the context of the question. “During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of “Done”, if appropriate and not in conflict with […]
Many folks believe that a Sprint is an arbitrary length of time in which you create and release software. They look at their continuous delivery pipeline and say to themselves; “Why would I limit myself to shipping only once every two weeks?” UPDATE: Scrum.org just posted my Scrum Tapas – Scrum and Continuous Delivery which […]
I recently had a conversation with a product owner that wanted to have the Scrum team broken up into smaller units so that less time was wasted on the Scrum Ceremonies! Their complaint was around the need in Scrum to have the entire “Team” (7+-2) involved in the sizing of the work during the “Sprint […]
In my last post about Professional software teams creating working software David Corbin made a good point. How do you determining what “Free from fault or defect” means? Since that is different for each Product and may change over time you need to focus on Quality and reflecting that quality in a Definition of Done […]
There is a better way than staggered iterations for delivery that will keep you on the path to agility.
I am always surprised at the number of teams that release undone work to production. I understand that one may need a few sprints, or many if you inherited something nasty, to pay back that debt, but if it’s more then you are not a Professional Scrum Team. The sheer amount of software that I […]
From the Home of Scrum To be effective, Scrum Masters need to have a rock-solid understanding of the practices and values of Scrum. The Professional Scrum Master (PSM) assessments allow people to validate and certify their understanding of those practices and values, and how they would respond to situations that challenge them. Schedule a free 30 […]
Many organizations want to gain a competitive advantage by improving the value they derive from software development. They desire to take advantage of opportunities, respond effectively and deliberately to challenges, all while controlling risk and optimizing the return on investment. These organizations often turn to Agile processes such as Scrum, and embrace initiatives to become […]
The Kanban Guide for Scrum Teams is the result of a collaboration between members of the Scrum.org community and leaders of the Kanban community. Together, they stand behind The Kanban Guide for Scrum Teams. It is their shared belief that professional product development practitioners can benefit from the application of Kanban together with Scrum. Schedule […]
Many organisations wrestle with the seeming incompatibility between agile and release management and they struggle with release planning and predictable delivery.