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.
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.
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.
The Team Retrospective is one of the most valuable Scrum meetings and has one clear purpose, to identify at least one improvement that will be enacted during the next sprint. In this article, we’ll get you started on how to run a great Team Retrospective
Today, we focus on the daily stand up, a meeting held every day to ensure the whole team is aligned towards completing the sprint goal.