Scrum Agile Project Management

Slicing User Stories for the Sprint Hamburger

February 15, 2012 0

The “rightsizing” of user stories occurring during the planning of the next sprint in Scrum is not always an easy task to perform. Inexperienced teams have difficulties to split user stories into smaller chunks that still deliver business value and would rather use technical criteria. In this blog post, “Specifications by Example” author Gojko Adzic provides a new approach to achieve this goal using the hamburger as a reference. You identify the tasks making up a user story. Then you use this breakdown to identify different levels of quality for each step and create vertical slices to identify smaller deliverables, thus creating your next sprint’s hamburger.

A Planning Poker Tool for Collaborative Estimation in Distributed Agile Development

December 14, 2011 0

Estimating and planning are critical to the success of any software project, also in the case of distributed agile development. Research has acknowledged that conventional agile methods need to be adjusted when applied in distributed contexts. However, we argue that also new tools are needed for enabling effective distributed agile practices. This article presents eConference3P, a tool for supporting distributed agile teams who applies the planning poker technique to perform collaborative user story estimation. The planning poker technique builds on the combination of multiple expert opinions, represented using the visual metaphor of poker cards, which results in quick but reliable estimates.

Using Sagas as a Strategic View of Epics

December 6, 2011 0

Epics are used to get a bigger picture of user stories, but we need another level of abstraction. We need to bring together the various Epics that describe how our solution will evolve to its final endpoint, and how different functional teams and specialists will interact.

Scrum Expectation Line

November 14, 2011 0

The Scrum Expectation Line is defined by Zsolt Fabók as the line that follows the expectations of the Product Owner during each sprint. In this blog post, he discusses the difference between the team capacity to deliver and what the Product Owner wants in each Sprint and explains how his team deals with it.

Lean and Scalable Requirements Information Model

November 3, 2011 0

This article describes a Lean and Scalable Requirements Information Model that extends the basic team‐based agile requirements practices to the needs of the largest, lean‐thinking software enterprise. While fully scalable to all levels of the project, program and portfolio levels, the foundation of the model is a quintessentially lean and agile subset in support of the agile project teams that write and test all the code.

Lifecycle of User Stories

September 12, 2011 0

Henrik Larsson presents in this post the user stories lifecycle from their origin in a Minimum usable feature (MUF/MMF) to their validation by the product owner at the end of a Scrum sprint.

Uncompleted User Stories

September 1, 2011 0

In this blog post, Sten Johnsen discusses the impact of moving uncompleted user stories from one Scrum sprint to another. He focuses on the unfinished user stories, its impact on the team velocity and its influence on the ability of the team to change.

1 4 5 6 7 8