This document provides an overview of implementing Scrum within an organization in 10 steps: 1) Get your product backlog in order, 2) Estimate your product backlog, 3) Conduct sprint planning for requirements, 4) Conduct sprint planning for design, 5) Create a collaborative workspace, 6) Conduct the sprint, 7) Hold daily stand-ups, 8) Track progress with a daily burn down chart, 9) Finish when you said you would with a sprint review and retrospective, 10) Repeat the process with review and reflection. Key concepts to embrace include active user involvement, empowering self-organizing teams, capturing requirements at a high level, and delivering working software frequently through iterations.
4. KEY CONCEPTS TO Active user involvement is imperative
EMBRACE FIRST... The team must be empowered to make
decisions
Requirements evolve but the timescale is fixed
Capture requirements at a high level;
lightweight & visual
Develop small, incremental releases and iterate
Focus on frequent delivery of products
Complete each feature before moving on to the
next
Apply the 80/20 rule ( Pareto’s Law )
Testing is integrated throughout the project
lifecycle – test early and often
A collaborative & cooperative approach
between all stakeholders is essential
7. high‐level estimates estimate in points estimate as a team
use a point system review priorities
stick with the programme
2. estimate your product backlog
11. 6. sprint!
agile teams must be empowered
time waits for no man!
done means DONE!
testing is integrated throughout the lifecycle
no interference
aborting a sprint
17. agile principles ( 1‐6 )
1. Our highest priority is to satisfy the customer
through early and continuous delivery of valuable
software
2. Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage
3. Deliver working software frequently, from a couple
of weeks to a couple of months, with a preference to
the shorter time scale
4. Business people and developers must work together
daily throughout the project
5. Build projects around motivated individuals. Give
them the environment and support they need, and
trust them to get the job done
6. The most efficient and effective method of
conveying information to and within a development
team is face‐to‐face conversation
18. agile principles ( 7‐12 )
7. Working software is the primary measure of
progress
8. Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely
9. Continuous attention to technical excellence and
good design enhances agility
10. Simplicity – the art of maximizing the amount of
work not done – is essential
11. The best architectures, requirements, and designs
emerge from self‐organizing teams
12. At regular intervals, the team reflects on how to
become more effective, then tunes and adjusts its
behaviour accordingly
19. communication
agile values
agile values
communication
respect
Feedback
respect
Courage
respect
simplicity
feedback
courage