a blogblogest 2007

field notes

Telling Executive Stories

0 comments

Delivery teams manage and deliver value supported by the tool user stories. These teams tell stories about who, what, why, and acceptability using standard form, “As a <persona>, I want <capability> so that <delivered value> occurs,” and behavior acceptance form, “Given < context>, when <action occurs>, then < consequence >.” These stories form the foundation […]

read more

Acceptance Criteria

3 comments

Did We Build the Right Product? And, Did We Build the Product Right? Acceptance criteria are an important yet, in my experience, often overlooked or undervalued aspect of the iterative planning process. Acceptance criteria are super important because projects succeed or fail based on the ability of the team to meet their customers documented and […]

read more

Don’t Estimate Stories In Sprint Planning

3 comments

This is part three in a series on estimating. Part one was “Don’t Estimate Software Defects” and Part two was “Don’t Estimate Spikes”. I don’t estimate stories in sprint planning. Nor do I re-estimate stories in sprint planning. I estimate stories in a separate estimating meeting and usually at least a couple sprints in advance, […]

read more
1 2 186