Creating the product backlog

Previously I blogged about what user stories in scrum should look like, providing an overview of their format and principles, but not really covering a how you come up with them all or how you decide what order to do them in.

This post covers who needs to be involved and recommends a practical 10 step approach for creating the Product Backlog.

Quick and accurate high-level estimates in Scrum

So Agile is all about working software over comprehensive documentation right? But if I don’t know the detailed requirements up front, how can I estimate for a task? And if I can’t estimate for a task, how can we figure out how long the project will take and how much it will cost?

This post covers techniques for quickly and easily creating reasonably accurate, high-level estimates in the project kickoff meeting that are sufficient for resource planning and scheduling.

What’s the Story?

The who, what, when, where and why of user stories for Scrum.