The team was eager to launch into their first release planning exercise. Wisely, the Scrum Master and Product Owner (PO) did not hand the team a list of already-written user stories. They knew that while it would take the team a little more time to identify and write the basics of each story, it would … Continue reading User Stories – What’s in a Name?
One of the most challenging aspects of adopting agile is requirements gathering and definition. The challenge is not because agile has complex methods for describing requirements, rather quite the opposite. Agile methods such as writing a user story on an index card and then relying on conversations between developers, product owners, and users to carry … Continue reading Does Agile Make Business Analysts Obsolete?
Experienced agile practitioners take for granted that detailed requirements are captured as user test cases. For organizations transitioning to agile, this is one of the more challenging practices for them to adopt. Some product owners or business analysts still view the traditional “requirements document” as the way to capture detailed requirements. Because of their attachment to … Continue reading Who Should Write UATCs?
On a large-scale agile project/program with multiple Scrum teams working toward the same overall goal, having user stories sized in a way that makes it easier to re-assign them from one Scrum team to another provides provides a planning and execution advantage when balancing work across teams to optimize delivery dates. Before adopting a common story points scale, there are a couple … Continue reading Normalizing Story Points Across Teams