In part 1 of this series of articles we looked at the […]
Platform based teams worked fine for a long time, but we wanted to supercharge our progress. So we started to look at ways we could improve; our next experiment was project based development teams.
In this series of articles we look at the different ways that you can structure your teams in order to help you succeed with agile software delivery
As with all software development, you are almost certainly going to encounter bugs in your code, so how important are your bugs? And how do you decide when to fix them?
This article describes one simple method for how to incorporate bug fixes into your agile development process.
n this article we review how to measure team performance with a sprint score. The primary measure of progress for a scrum team is “working software”, however, by using some basic empirical data, you can get a quick overview on how your teams are doing in general. Armed with this data, you can decide as a team what to improve next.
In this article, we look at when scrum meetings occur in a typical 2 week sprint. In fact, this is the exact setup I use for one of my scrum teams. I hope it helps you plan your upcoming sprints.
I recently spent two days going through Mike Cohn’s “Better User Stories” course, and I wanted to write a quick review of how it went, so that you can decide if it’s right for you
This article will help you get started with how to run backlog refinement; the art of making your product backlog ready for development!
The purpose of the sprint review meeting is to ensure that we have an updated product backlog before we start the next sprint. We need to take some time to make sure we are building the right thing and heading in the right direction.
Today we tackle how to run the Sprint Planning meeting. It’s a tough cookie to get right; but this article should help get you started on the path to success.