Home » Archives

Content tagged with: metrics

[12 Jan 2012 | Comments Off on Measurements for Agile Software Development Organizations | ]

This video presents an agile framework for organizational measures based around the improvement goals of Better, Faster, Cheaper.

[27 Oct 2011 | Comments Off on What’s Wrong With Agile Methods | ]

Current agile methods could benefit from using a more quantified approach across the entire implementation process :t development, production and delivery. The main benefits of adopting such an approach include improved communication of the requirements and better support for tracking progress and getting feedback. This article first discusses the benefits of quantification in software development projects, then outlines a proposed approach (Planguage) and finally describes an example of its successful use.

[11 Oct 2011 | Comments Off on Metrics for Better Software Teams | ]

The article “Moneyball for software engineering” explains how metrics-driven decisions can build better software teams. The basic idea is that organizations can use statistical data to build more competitive teams. Most of us work in software project teams, but we rarely use metrics to identify strengths and weaknesses, set and track goals, or evaluate strategies.

[16 Aug 2011 | Comments Off on Evaluate Your Project Performance with TSP | ]

The Team Software Process (TSP) provides a framework to predictably and effectively build software-intensive products. It relies on data collected by team members to provide insight into how a software project is operating.

[13 Jul 2011 | Comments Off on Quantitative Project Management Framework Integrating Six Sigma, PSP and TSP | ]

This article proposes a framework where software engineers and project managers can quantitatively manage software projects to improve the software development process applying Six Sigma in conjunction with the Personal Software Process (PSP) and Team Software Process (TSP).

[4 Jan 2011 | Comments Off on The Land that Scrum Forgot | ]

As Scrum teams quickly release new software, Bob Martin recommends to monitor that the team is not hyper-productively making a mess! You have to make sure they are practicing the disciplines that produce data that can be measured. You use that data to measure the quality of the code they are producing and you provide incentives for keeping that code clean.