When a team plans a sprint they make a commitment to complete the user stories they select from the product backlog. It's not a come-hell-or-high-water commitment,
Sprint planning meetings typically go into deeper detail than is appropriate for product backlog item estimating (whether in story points or ideal days).
I was asked recently how to go about writing user stories for a back-end financial system. This is an interesting example and is a question I get asked a lot, so I thought I should answer it here.…
This article addresses the issue of how much detail should be included in product backlog items and when that detail should be added. In answering that question it provides guidance on how to…
Sticky ideas and stories aren't necessarily bad; they are just things that change our attention at just the right time and that are so intriguing/compelling/interesting that they spread like…
There are many ways to transition to an agile process. Choosing the approach that is most likely to work best for your organization can be critical to a smooth transition.
What my friend had found is that his product owners had evolved in adaptation to their environment, just as the fire ants had evolved in adaptation to theirs
