Why don’t metrics apply to Agile development methodologies? Wrong! They Do, but you have to know how and when.

Find out in our quarterly webinar in special collaboration with the Chicago Quality Assurance Association (CQAA).

Agile, a development methodology, designed to allow team members to work iteratively during the development process instead of delivering a final product all at once, is now 20 years old. And when it comes to testing within an Agile process, there are those that use pyramids, and rectangles as mental models for where you should put your effort, or not.

Sometimes, software quality in Agile is mistranslated as the idea that everyone is responsible for software testing. But within Agile software development, ensuring quality is much more than testing and must include activities at different levels, including estimates for the workload for each iteration. Otherwise, testing happens last minute—or sometimes not at all, depending on time constraints. To have a successful Agile team, most software developers know that velocity is an essential component.

But it’s not just about measuring velocity, as velocity is only one factor or measurement for success. There are many other factors to measure when you want to assess the success of your Agile team in delivering a quality product. In this webinar, we specifically look at some key metrics for us the measure the success and progress of our quality in Agile.

Tune in with Philip Lew as he goes through ways you can gather insights in slicing, dicing, and analyzing (and interpreting) data. We’ll use Jira as an example, but you can do this with practically any issue tracking collaboration tool to help your team improve software quality.