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 andContinue Reading…

Agile teams are expected to deliver business value on a regular basis. This focused and fast–paced session provides you with all the techniques you need to do so. We’ll discuss iteration planning, “done done,” velocity, slack, minimum marketable features, working on one thing at a time, risk–adjusted burn–up charts, andContinue Reading…

In this blog post, Tom Perry shares his thoughts about how the software project team productivity is influenced by change. Finding that combination of what works for a project can take time. However, when this happens, it will often produce a dramatic improvement in performance and not a slow gradualContinue Reading…

This article explains the usage of Earned Value Management (EVM) in software development projects. EVM is simply a way of calculating two pieces of data for a project: schedule performance and called cost performance.

Jeff Suther­land explains in this video that the Burn­down Chart is intended to monitor the simul­ta­ne­ous agile devel­op­ment meth­ods going on within a Scrum team. Like a fighter plane land­ing, there is no room for error, and the chart is intended to mon­i­tor such issues.

EVM is a simple quantitative technique that can be used to measure the schedule progress and optionally the budget progress of software projects. This article explains what EVM is and walks you through an example of using EVM to measure test-effort progress.

The article “Managing Schedule Flaws using Agile Methods” presents several symptoms and causes of schedule problems, describes metrics and diagrams that can be used to track your team’s progress against its schedule and proposes Agile approaches to mitigate these risks.

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 theyContinue Reading…