Do Story Points Relate to Complexity or Time?

by Vikas Hazrati Follow 0 Followers on  Jul 06, 2010 8

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 Follow 0 Followers 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 Follow 0 Followers 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 Follow 0 Followers 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 Follow 0 Followers 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.


Presentation: Planning with a Large Distributed Team

by Abel Avram Follow 7 Followers on  Oct 19, 2008 1

In this presentation filmed during Agile 2008, Wes Williams and Mike Stout share their recent experience with a large distributed team, the planning hurdles they encountered and how they passed them, and their recommendation: avoid large distributed teams.


Presentation: Prioritizing Your Product Backlog

by Geoffrey Wiseman Follow 0 Followers on  Oct 06, 2008 3

Choosing the right features can make the difference between the success and failure of a software product. Mike Cohn presented 'Prioritizing your Project Backlog' at Agile 2008 on how a project backlog should be organized and prioritized and non-financial techniques for prioritization such as kano analysis, theme screening/scoring, relative weighting and analytic hierarchy process.


What is Sprint Zero? Why was it Introduced?

by Mark Levison Follow 0 Followers on  Sep 25, 2008 14

Some teams use a Sprint 0 to prepare their product backlog, the infrastructure (development environment, CI server), ... .Is this part of Scrum? Is it useful?


Prioritizing (the Backlog) For Profit

by Derek Longmuir Follow 0 Followers on  Aug 08, 2008

Having difficulty prioritizing the backlog? Luke Hohmann has described a method to make quantitative decisions about which backlog items should be considered first. In addition to the usual attributes such as implementation effort, Luke suggested adding attributes to measure stakeholders needs, strategic alignment and to ask whether the item is driving profit.


TargetProcess Offers a Free 5-User Community Edition

by Abel Avram Follow 7 Followers on  Jul 04, 2008

TargetProcess has released a free 5-user Community Edition of its Agile project management software. The Community Edition contains the same features as the full edition of the product with two limitations: a maximum 5 users, and no support.


A Preview of Mingle 2.0

by Ben Hughes Follow 0 Followers on  Apr 11, 2008 2

On April 15th Thoughtworks will release Mingle 2.0, nine months after the initial release of Mingle. InfoQ got some time with product manager Adam Monago to talk through the new functionality provided by Mingle 2.0.


Agile Project Management ScrumWorks Pro 3.0 released

by Mark Levison Follow 0 Followers on  Mar 31, 2008 1

Danube Technologies has just released the 3.0 Release of ScrumWorks Pro, last mentioned in August 07. ScrumWorks Pro is an Agile Project Management tool that help track team(s) progress through individual iterations and whole releases. In this release changes focused on two areas: usability improvements and the use of MySQL as the backend database.


Should the Customer Care about Agile?

by Vikas Hazrati Follow 0 Followers on  Mar 13, 2008 2

The involvement of customer in an Agile project is taken for granted, however in many situations, intentionally or unintentionally, the customer may not follow the Agile practices. An interesting discussion on the Extreme Programming group tries to decipher the situation and find possible solutions.


Interview: Johanna Rothman on Schedule Games and other Organizational Dysfunctions

by Deborah Hartmann Preuss Follow 0 Followers on  Mar 13, 2008 1

Johanna Rothman is an organizational consultant, coach and co-creator of the AYE conference (Accelerate Your Effectiveness). Deborah Hartmann interviewed her at Agile2007 about her third management book - and discovered that there are names for some of the the scheduling games that cause us to spin our wheels, including: Bring Me A Rock, Queen of Denial and Pants on Fire!


InfoQ Presentation: Selecting the Right Methodology and Steering it to Success

by Deborah Hartmann Preuss Follow 0 Followers on  Feb 12, 2008

It's easy to agree with "anything more than 'barely sufficient' in is waste," but it's more complicated when we actually need to customize a process for a particular project. At Agile2006 Todd Little shared a model to help leaders choose the right flavour of Agile based on project and team attributes, and he emphasised the need to actively steer projects as development progresses.

Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you