The blog posts explains how to set up a Scrum team as a “startup” within an established enterprise to create a new product, and to pilot a new way of working.
User stories are great at capturing product functionality in isolation. But they are not well suited to describe the interactions between different features and to describe workflows. This blog posts shows how context and activity diagrams can used successfully to complement individual stories.
Using the product backlog can be challenging, and many product owners wrestle with overly long and detailed backlogs. This blog post provides ten tips that help you work with your product backlog effectively.
High-priority product backlog items must be ready to be transformed into working software. Find out what does “ready” means and benefit from Yoda’s advice
.
User stories are probably the most popular agile requirements description technique. It’s comparatively easy to write, decompose, and refine user stories. But writing good stories can be hard. This blog post helps you tell great stories.
This blog posts explores four useful factors to prioritize the product backlog: value; risk and uncertainty; releasability; and dependencies.
Find out if user stories or use cases are more appropriate to capture product backlog items.
The product owner role in Scrum attracts a lot of interest and controversy. This post attempts to demystify this important role.
RSS