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
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, and
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 gradual
Jeff Sutherland explains in this video that the Burndown Chart is intended to monitor the simultaneous agile development methods going on within a Scrum team. Like a fighter plane landing, there is no room for error, and the chart is intended to monitor such issues.