program selection system

User stories play a central role in Agile requirements, planning and implementation. However, experts have different formulas for crafting stories and teaching others how to do it.

In this session, Jennitta Andrea, Gil Broza, Mike Cohn and Ron Jefrries will share their unique, similar or different perspectives on such issues as:

• Format: Do stories have a typical format or does that just get in the way?
• Scope: What is / is not a User Story?
• Size: Does size matter?
• Splitting: What is it? Is it needed? If so, when?
• Authors: Who writes or changes User Stories?

How do you quickly and effectively develop a healthy product backlog which you can use as a basis for iteration and release planning?

One of the central tenants of Agile practices is the emphasis on customer value. That’s great, but if you’re a product company then focusing on business value alone isn’t enough. You need to convert business value into actual money flowing into your company.

Product owners often find themselves stuck in the middle of a complex and swirling set of political, organizational, and customer forces when dealing with their backlogs. Each of the stakeholders who interact with the product owner want different levels of detail, degrees of traceability, and understanding of practical and strategic intent.

The biggest risk to most projects is building the wrong product. Regardless of how fast your agile team becomes, how brilliant your technical solutions are, or how many automated tests run continuously, nothing matters if you’re building the wrong product.

In this tutorial we’ll look at non-financial ways of both prioritizing product backlog items and choosing among competing project ideas. Included are relative weighting, theme screening, theme scoring, and Kano analysis.