How To Use Scrum in Your Team
A brief step by step guide on using Scrum
Why should I care about…Scrum?
Scrum offers the most popular, battle-tested recipe for building a successful product as a team. The product can be anything from a simple software to a Mars spaceship. You don’t need to reinvent the wheel - Scrum tells you what most (hyper)productive teams do to:
- stay productive and creative = happy team members 😊
- deliver a product that end users want = happy customers 😊
- minimize a waste of time and money = happy business owners 😊
Why would anyone create Scrum?
Scrum was a natural answer, to the problem in software development, that came in 1993. The problem was the waterfall model — a development process that could last years before customers got any value out of the final product. The waterfall model can be broken down into 6 steps, where each step can be started only after the previous step has been completed:
- business people => create a DETAILED requirements specification
- architects => create a DETAILED system architecture with all kinds of fancy diagrams
- developers => can finally start coding
- testers => get the finished code and can start testing the system
- devOps => a long, long time has passed and the system can be deployed
- now make sure it still works the next day
The main flaw with the waterfall model is that it doesn’t take into account any uncertainty. Everything is planned down to the last detail at the beginning, and it is assumed that the plan is correct. However, the initial plan is always incorrect and it’s complicated to change it later in the process. That’s why Scrum comes to save the day…or years of wasted effort and
