Using Complexity Measurements to Improve Software Quality

by Ben Linders on  Oct 24, 2014 3

Complexity is a direct indicator of software quality and costs: if the complexity for any code is high, the quality of that code will be lower and it will cost more to manage it. Complexity measurements can be used to estimate development and test activities and to decide where refactoring is needed to improve quality and prevent problems.

Agile Estimation for Release Planning

by Ben Linders on  Apr 24, 2014

Estimations are used by agile teams and product owners for prioritizing work and to plan releases of products. They can be done on different levels and in various ways.

Are There Better Estimation Techniques for Experienced Teams?

by Vikas Hazrati on  Oct 26, 2010 6

The results of software estimation are important for stakeholders to take care of team allocation and budgeting. A widely prevalent technique to estimate in Agile has been Planning Poker, which is a consensus based. Does this way of estimating take too much time? Are there other methods which can be employed by experienced practitioners?

Re-estimate Completed User Stories for a More Accurate Velocity?

by Dan Puckett on  Sep 02, 2010 2

In a recent thread on the Scrum Development mailing list, Paul Battison asked whether his team should re-estimate completed stories after the sprint is done, so as to have the team's velocity reflect the actual effort that went into completing the stories.

Is Estimating A Wasteful Practice?

by Mike Bria on  Aug 13, 2008 23

The age old problem of software "estimation" has generated some interesting discussion lately in the agile community. J.B. Rainsberger, Arlo Belshee, Josh Kerievsky, David Anderson, and others ask the question "Are estimates really needed at all?"

Article: User Story Estimation Techniques

by Floyd Marinescu on  Jul 07, 2008 17

One of the great things about working as a consultant is the ability to try out many different ideas and adapting your personal favorite process to include things that work. This article gives the details about user story estimation techniques that Jay Fields has found effective.

Evidence Based Scheduling and FogBugz 6.0

by Ben Hughes on  Nov 29, 2007 3

Joel Spolsky recently posted an article about Evidence Based Scheduling. The post focuses on managing and identifying good estimates, in turn allowing the project manager to forecast the probability of delivering on a given date, adding a new method of measurement to the agile project manager's toolbox. InfoQ investigates the theory behind the practice, and its implementation in FogBugz 6.0.

General Feedback
Marketing and all content copyright © 2006-2016 C4Media Inc. hosted at Contegix, the best ISP we've ever worked with.
Privacy policy

We notice you’re using an ad blocker

We understand why you use ad blockers. However to keep InfoQ free we need your support. InfoQ will not provide your data to third parties without individual opt-in consent. We only work with advertisers relevant to our readers. Please consider whitelisting us.