SO, WHAT IS ‘AGILE’?
THE MAIN FOCUS OF THIS SOFTWARE DEVELOPMENT METHODOLOGY IS TO BREAK DOWN PROJECTS AND DELIVER THEM IN SHORT INCREMENTAL CYCLES, ALLOWING TEAMS TO RESPOND TO UNPREDICTABILITY.
WHY USE AN AGILE APPROACH?
We are here to give you our Top 8 points on what we enjoy most about the Agile method:
- Requirements over the course of a sprint are prioritised. Meaning that over the course of a project, the needs of the project and client are prioritised.
- The approach encourages flexibility, should requirements evolve.
- Daily scrums mean that all team members are across the status of tasks and can discuss any blockers. There is complete transparency across all tasks and the developers are accountable.
- Productivity is measured on the effort score and not by the number of tasks completed. Tasks are also scored by the individual, meaning that what is a small task for a senior developer could be a medium task for your junior developer and that is reflected at the end of the sprint.
- Tasks are broken down very clearly so that there is a clear idea of what each part of the development entails.
- Done means Done. Before a task can be counted as completed, it needs to be tested and signed off, no re-visiting halfway through the next sprint. This means you need to ensure that testing and reviewing is part of your tasks.
- The Kanban provides an easy visual for the project manager of the tasks that each team member is currently working on, and how the sprint is tracking.
- Retrospective meetings are a way for the team to reflect on what happened in the sprint, and how to improve moving forward. It means that all team members can get involved in the discussion and really identify what they think went really well, and what didn’t.