In last week?s updateÃ¡we introduced Scrum methodologies and outlined how, at automaton, we?ve effectively adapted this management paradigm to our own development environment. This week we?d like to take the opportunity to demonstrate how Scrum benefits us as well as our clients.
At automaton, we adopted Scrum a few years ago to enhance the way we work and the way we output. In a rapidly changing market place, it made sense to adopt a method that was flexible, as opposed to reactive. Working in two-week sprints, our teams not only respond more immediately to change, they anticipate it. In that way, we?re more equipped to deal with the challenges that come with change.
With its hands-on approach, Scrum extols transparency so that not only are our teams kept on track with daily ?scrums? (15 minute standup meetings), but our clients remain closely involved throughout the process. Delivering shippable products after each two-week sprint allows our clients to review and assess our work so that the best possible outcomes are achieved.
Here?s what a couple of team members at automaton who use Scrum on a daily basis had to say about its benefits:
David Moyer: ?The sprint planning meetings ? get everyone on the same page, and help break the big picture down into smaller, more manageable tasks.Ã¡Having less tasks to focus on at once gives you much better clarity on what needs to be done, how it can best be achieved, and how long it will take to do it. It generally results in a higher quality, more stable product, and the regular release schedule keeps the clients happy.?
Jelena CurcicÃ¡: ?I adore the fact that it?s people over processes and the hands-on engagement of everyone with the product ? it?s a small team so everyone?s engaged with the product. I love the immediacy of seeing the product grow instead of waiting for a long time. I think in the long run, if it?s utilised properly, it?s actually cheaper because you can prioritise your team so no time is wasted. I just love the dynamics of it, the speed of the delivery, and the transparency.?
Summary of benefits
1. Sprint planning sessions = achievable tasks set out for teams
2. Daily ?scrum? standup meetings to review progress = greater transparency for both teams and clients
3. People over processes = teams don?t get bogged down in process documentation so more time is spent on writing code
4. Small teams = face-to-face collaboration with clear communication
5. Ownership of roles = no micro-management for teams
6. Two-week sprints = allows teams to quickly respond to and adapt to change
7. Regular release schedules = clients see fast, tangible results
8. Close collaboration and review with teams and clients = evolve and improve the product for quality output
9. Incremental output = decreased chance of delivering outdated products therefore cheaper in the long run for clients
10. Higher-quality output = team pride and happy clients
Tune into our ?updates? next week when we explore the question of whether marketers should be getting on board with Scrum.