Metrics in modern projects

Modern Agile processes are geared toward continuous improvement. But how do you know what exactly is worth improving? How can you work faster and deliver better quality by raising your effectiveness? How do you reliably judge whether an improvement has actually helped? That’s what the many metrics and diagnostics are for: they can help you answer these questions.

Everyone runs into complaints from the customer or management about the quality, output, or speed of their work: “you’re too slow,” “do better,” “your quality is poor,” and so on. Yet neither side has a clear definition of “slow,” “better,” or “poor.” Sound familiar? In essence, these are just someone’s subjective impressions, and without measurements, facts, and figures, that’s all they will ever be.

A less obvious but hugely important point is that by introducing measurement, you get your work processes and tooling in order along the way, which raises the maturity of both your people and the company as a whole. All of this brings very concrete business benefits: it improves control over the project, gives you a clearer picture of where the project stands, and, importantly, cuts costs and strengthens the company’s reputation.

Agile methodologies (Scrum, Kanban, Lean, XP) are becoming more and more popular today. In these processes, too, metrics are important for tracking the success of the project and of the development process. There are also a number of metrics that apply directly to code and can be used in any development process.

In this training, you’ll get a concentrated dose of knowledge and skills in the discipline of measurement. It spares you the months, if not years, it takes to learn it all the hard way through trial and error. The overall focus is on practical application. Theory is presented interactively and combined with group work, plenty of hands-on exercises, and real-world cases. The training is aimed at helping project teams put metrics into practice.