BT

Rocket to Mars: A Sprint Planning Game

by Ben Linders on  Dec 11, 2013 5

“Many team and their product owners believe that the team's unique job is to deliver more and more story points, but we consider this to be a complete misunderstanding of the relation between the team and the product owner” said Damien Thouvenin and Pierrick Revol. They ran a sprint planning game on investing time to produce stories, investigate issues, reduce technical debt, or do training.

How Individuals Can Adopt an Agile Way of Working

by Ben Linders on  Aug 01, 2013

Organization mostly do an agile transformation for a whole team, project, or organizational unit, given that agile is a team driven approach. But there are also professionals who start using agile practices individually, or who are working agile as a one person team. How can individuals adopt agile, and what kind of benefits can it give them?

The Flexibility of Agile: Flaw or Strength?

by Ben Linders on  Jul 18, 2013 4

The principle of “responding to change over following a plan”, is it a strength or a flexibility that can’t work in practice? For example, what about agile projects that had difficulties managing changes and customers who expect too much flexibility? Can agile not live up to its promises, or is it the way that teams and organizations have adopted agile that is causing the problems?

Scrum Project Management Practices Support the CMMI

by Ben Linders on  May 31, 2013 7

An exploration on how project management with Scrum and the project management process areas of the Capability Maturity Model Integration for Development are related.

Product Backlogs with Process Maps or Story Maps

by Ben Linders on  Apr 11, 2013

When you have a large backlog with many user stories, structuring a product backlog with story maps or process maps can help to keep an overview and see the bigger picture.

The Planning Poker Prevents Fallacies in Effort Estimates

by Michael Stal on  Aug 10, 2012 15

In his recent blog posting “Planning Poker: Avoiding Fallacies in Effort Estimate” Hayim Makabee discusses a common problem of effort estimation called planning fallacy and why planning poker helps to avoid it.

The right time for decision making

by Marta Jasinska on  Jun 28, 2012 1

Earlier this week Jim Bird from BIDS Trading Technologies posted a blog article about the differences between Agile and Lean approaches to planning and decision making.

Seven Options for Handling Interruptions on Agile Teams

by Craig Smith on  Jan 26, 2012 1

Interruptions are something that every team has to deal with and, if not managed appropriately, they can potentially have a detrimental affect on their ability to deliver. In a recent post on the Agile Advice blog, Mishkin Berteig described seven options that teams could consider to deal with interruptions when using Scrum or iterative Agile approaches.

Do We Need an Iteration Zero?

by Vikas Hazrati on  Jun 07, 2011 1

There are usually multiple things which need to be done before the start of a project. Teams usually use 'Iteration Zero' to put all necessary systems in place in order to start delivering business value in subsequent iterations. Is this the right way?

How Should a Product Owner Participate in a Planning Poker Session?

by Dan Puckett on  Aug 09, 2010

During planning poker, a product owner should explain the user stories to the development team, but he or she should not try to unduly influence the development team's estimates.

Do Story Points Relate to Complexity or Time?

by Vikas Hazrati on  Jul 06, 2010 7

Many Agile teams use the terms Story points and Complexity points interchangeably. Agile teams believe that they are better than hours just because they are based on complexity and relative size. Mike Cohn suggested that it is wrong to use story points to depict the complexity of developing a feature, they are all about the effort.

What is Story Point? Are they Necessary?

by Mark Levison on  Mar 05, 2010 5

Michael de la Maza asks the question what exactly is a Story Point? He went looking for an answer and found many: “Story points represent nebulous units of time.” or “Story point is a random measure used by Scrum teams. This is used to measure the effort required to implement a story.”

Estimating Business Value

by Chris Sims on  Jan 04, 2010 2

The traditional agile approach to prioritization is that user stories of higher business value should be implemented before ones of lower business value. The concept is simple, but implementing it well relies on having a mechanism to assess business value. Pascal Van Cauwenberghe has recently described an approach to defining business value, called "Business Value Modeling", which may help.

Sprint Planning: Story Points Versus Hours

by Vikas Hazrati on  Sep 22, 2009 11

There is a constant, long drawn debate on the benefits of using either story points or hours for sprint planning. Mike Cohn is big on breaking User Stories down into tasks, which are then estimated in hours. Jeff Sutherland on the other hand suggested that some of the best teams that he has worked with burn down story points.

Throw Away Your Bug Tracking System?

by Mike Bria on  Mar 18, 2009 5

Elisabeth Hendrickson, A.K.A "testObsessed", presents a thought-provoking stance on triaging bugs in an agile project. She discusses her feelings that problems found during the iteration are not "bugs", that only the Product Owner has the right to call something "bug", and that a healthy agile team might likely have no need for a bug tracking system.

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2013 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT