A good analogy to describe agile working is to imagine how a house is built. First the foundations are put in place, then the structure comes, followed by the roof, the windows, the electrics and the interior design.
But feedback and assessment is required at every stage to ensure stability.
If the builders had used the Waterfall method, the house would have been fully built, and only after completion and the new owners moving in would they discover a problem with the foundations.
What is agile working?
Agile working is about bringing people, processes and technology together to find the most effective way of delivering a task or project. The Agile Manifesto explains that work should be about:
- Focusing on individuals and interactions, not processes and tools
- Collaboration, not negotiation
- Responding quickly to changes
Within agile, there are core frameworks that deliver these goals: Scrum, Scrumban, Kanban, DAD and Crystal.
At 6B, we always use the scrum framework because of the experience we have in our team. It’s a framework we use to deliver high value products for complex projects, releasing the solution in stages to improve quality and listen to customer feedback.
Scrum follows a set of roles, responsibilities, and meetings that never change, such as sprint planning, sprint retrospectives and daily standups. We use task boards and charts to show progress or explain feedback.
This sort of agile working allows us to break a project down into phases (or sprints), and focus on getting the best product at each stage. You build, test, amend and move on to the next section.
Aside from avoiding a ‘big bang’ deployment of a project, agile holds a lot of other benefits for our customers – here’s our top four summary…