Product Backlog and User Stories

Correct Answer: Group related stories into feature sets while maintaining individual story independence

In Disciplined Agile, grouping related stories into feature sets while maintaining individual story independence is the optimal approach for handling dependent user stories. This approach is best because it: - Preserves the agile principle of small, independent deliverables - Enables parallel work when possible - Maintains visibility of relationships between stories - Allows for flexible prioritization and delivery - Supports incremental value delivery The other approaches are incorrect because: - Combining all dependent stories into a single large story violates the principle of small, manageable chunks and reduces flexibility - Creating separate Product Backlogs fragments the product vision and complicates coordination - Strict sequential delivery based on technical dependencies reduces agility and may delay value delivery unnecessarily The correct approach balances the need to recognize dependencies while maintaining agile principles and delivery flexibility.

Correct Answer: Use relative sizing with story points based on team velocity and past experiences

In Disciplined Agile, relative sizing with story points is the recommended approach because: Strong points of relative sizing: - It allows teams to estimate based on their own context and experiences - Story points account for complexity, uncertainty, and effort - It promotes team discussions and shared understanding - It leverages the team's historical velocity for better predictions Why other approaches are less effective: - Detailed time estimates in hours are too precise and often inaccurate for complex work - Calculating precise work hours based on past stories fails to account for unique contexts and variations - Using standard industry averages overlooks team-specific factors and capabilities Relative sizing encourages: - Team collaboration in estimation - Focus on value delivery rather than precise timing - Continuous learning from past experiences - Adaptive planning based on team capacity

Correct Answer: It is prioritized based on business value and dependencies

In Disciplined Agile, an effective Product Backlog is prioritized based on business value and dependencies. This is essential because: A prioritized backlog helps teams: - Focus on delivering the highest value items first - Consider technical and business dependencies properly - Maintain flexibility while delivering value - Support adaptive planning The other options are incorrect because: Detailing all requirements upfront contradicts agile principles and limits adaptability to change. Organizing by technical components focuses on implementation details rather than business value, which goes against agile principles of customer-centricity. Strict FIFO ordering is too rigid and fails to account for changing business priorities and value delivery optimization.