Get Started. It's Free
or sign up with your email address
SCRUM by Mind Map: SCRUM

1. team

1.1. should

1.1.1. be self-orginized

1.1.2. be cross-functional

1.1.3. deliver product iteratively

1.2. roles

1.2.1. The Product Owner sole person managing Backlog clearly expressing items ordering items ensuring The Development Team understands him correct

1.2.2. The Development Team creates the product cross-functional writing code testing code delivering code does not contains sub-teams respects only The Product Owners item priorities

1.2.3. The Scrum Master ensure Scrum is understood and applicable serving The Development Team couching The Development Team teaching The Development Team facilitates scrum events as needed resolves conflicts serving The Product Owner provides techniques for backlog managment long-term planning monitoring progress towards the goal

2. artifacts

2.1. Product Backlog

2.1.1. can be updated at any time by The Product Owner

2.1.2. contains features functional requirements bugs enchancements

2.1.3. ordered by priority by risk by abstraction

2.1.4. every item has estimation

2.1.5. monitoring the remaining work could be summed up burndown chart

2.2. Sprint Backlog

2.2.1. subset of Product Backlog selected for current sprint

2.2.2. only The Development Team could change it during sprint

2.2.3. monitoring the remaining work could be summed up burndown chart

2.3. Increment

2.3.1. all Product Backlog items that has been completed

2.3.2. at the end of the Sprint must be done

3. events

3.1. Sprint Planning Meting

3.1.1. before beginning of the new sprint

3.1.2. questions what work should be done? how will the chosen work get done?

3.1.3. planing estimates

3.1.4. time 1 moth sprint 8 hours meeting 2 weeks sprint 4 hours meeting

3.2. Daily Scrum

3.2.1. every day during the sprint

3.2.2. questions what has been done during the last meeting? what will be done before the next meeting? problems to achieve sprint goals

3.2.3. aims synchronize activities create a plan for next 24 hours ensuring scrum monitoring product status monitoring risks

3.2.4. time 15 minutes

3.3. The Sprint

3.3.1. heart of scrum

3.3.2. developing phase

3.3.3. leads to new minor release

3.3.4. time less then 1 month

3.4. Sprint Review

3.4.1. at the end of the sprint

3.4.2. questions what has been done and what hasn't? how preserve problems, discovered during sprint?

3.4.3. time 1 moth sprint 4 hours meeting 2 weeks sprint 2 hours meeting

4. philosophy

4.1. principles

4.1.1. peoples more important then instruments and processes

4.1.2. working product more important then documentation

4.1.3. customers more important then contract

4.1.4. requirement changes more important then plan

4.2. flexible

4.3. customers oriented

4.4. product delivered iteratively