Would better user stories improve software delivery? Gojko Adzic thinks applying small changes to the way teams manage their user stories can have a huge impact on the actual outcomes of their software delivery. He announced that he wants to write a book about improving user stories if at least 5000 people show that they are interested by pre-registering themselves in January.
The product owner role from Scrum is used to interface between the business and development. In larger organization with complex products and many decisions that need to be made, having this role filled in by one person is often not feasible. InfoQ did an interview with Timo Punkka about the role of the product owner, lean portfolio management, and customer collaboration.
The purpose of backlog grooming is to keep the product backlog up to date and clean. Different approaches are used by product owners and teams to do this.
Agile teams sometimes struggle with the planning of pure technical tasks that have no direct value for the user of a system, but have to be done to deliver working software. Should you create user stories to handle such technical tasks and technical debt, or not?
Henrik Kniberg has developed “a 1 day product ownership course compressed into a 15 minute animated presentation”. Based upon this video and some other on-line resources about the product owner role, collaboration between product owners and teams is examined.
A new "Scrum Kickoff Planner" has just been released by Adam Weisbart with the aim of facilitating team discussion around the important facets of starting a new Agile team or project.
A product backlog left unattended can become large and unmaintainable. The common approach of reviewing and updating the backlog regularly might be ineffective in the longer term, demanding alternatives to backlog grooming.
The Product Owner role is regularly debated and discussed. The challenges of the role and the responsabilities encompased by it are a frequent source of discussion and advice. Recently there has been discussion about common aspects of the role and the important activities a product owner needs to ensure happen on an agile project, and the difference between the product owner and product manager
What are the advantages and disadvantages of having the same person fill both the Product Owner and the ScrumMaster role on the same Scrum project? Is this really a workable option?
Scrum works most effectively with a prioritized product backlog. Prioritizing the backlog is part of the product owner role, but what can you do when your product owner won't prioritize the backlog because he or she doesn't see the value in prioritization?
Mainstream Agile is an idea whose time appears to have arrived. Larger consulting services firms are now touting "agility", with firms like IBM Global Business Services and Cap Gemini pitching Agile-related service offerings. Given this kind of sudden mainstream popularity, what does it mean for Agile in general? What does "mainstream" Agile look like? What's in mainstream Agile?
Backlogs have been under constant criticism for quite some time now. Mary Poppendieck suggested that the product backlog should be eliminated if it is not satisfying the desired purpose. Serge Beaumont suggested an interesting way of partitioning the backlog such that it maps to a flow and makes the backlog worthy for existence.
An often asked question is how does Scrum recommend a team to handle bugs? Should they be placed on the product backlog? Or on a separate bug list? If they’re on the backlog, does the Product Owner get to set their priority or are they automatically the most important items? Should there be a separate bug fixing sprint?
In this interview with Jeff Patton at Agile 2008, he talks about three strategies that can help product owners do their job more effectively by embracing the inherent uncertainty in all software development. Namely they are understanding the ultimate goals of the project, delaying decisions until the last responsible moment, and scaling up by building quality.