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

1.2.1.1. sole person

1.2.1.2. managing Backlog

1.2.1.2.1. clearly expressing items

1.2.1.2.2. ordering items

1.2.1.2.3. ensuring The Development Team understands him correct

1.2.2. The Development Team

1.2.2.1. creates the product

1.2.2.2. cross-functional

1.2.2.2.1. writing code

1.2.2.2.2. testing code

1.2.2.2.3. delivering code

1.2.2.3. does not contains sub-teams

1.2.2.4. respects only The Product Owners item priorities

1.2.3. The Scrum Master

1.2.3.1. ensure Scrum is understood and applicable

1.2.3.2. serving The Development Team

1.2.3.2.1. couching The Development Team

1.2.3.2.2. teaching The Development Team

1.2.3.2.3. facilitates scrum events as needed

1.2.3.2.4. resolves conflicts

1.2.3.3. serving The Product Owner

1.2.3.3.1. provides techniques for backlog managment

1.2.3.3.2. long-term planning

1.2.3.3.3. 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

2.1.2.1. features

2.1.2.2. functional requirements

2.1.2.3. bugs

2.1.2.4. enchancements

2.1.3. ordered

2.1.3.1. by priority

2.1.3.2. by risk

2.1.3.3. by abstraction

2.1.4. every item has estimation

2.1.5. monitoring

2.1.5.1. the remaining work could be summed up

2.1.5.2. 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

2.2.3.1. the remaining work could be summed up

2.2.3.2. 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

3.1.2.1. what work should be done?

3.1.2.2. how will the chosen work get done?

3.1.3. planing estimates

3.1.4. time

3.1.4.1. 1 moth sprint

3.1.4.1.1. 8 hours meeting

3.1.4.2. 2 weeks sprint

3.1.4.2.1. 4 hours meeting

3.2. Daily Scrum

3.2.1. every day during the sprint

3.2.2. questions

3.2.2.1. what has been done during the last meeting?

3.2.2.2. what will be done before the next meeting?

3.2.2.3. problems to achieve sprint goals

3.2.3. aims

3.2.3.1. synchronize activities

3.2.3.2. create a plan for next 24 hours

3.2.3.3. ensuring scrum

3.2.3.4. monitoring product status

3.2.3.5. monitoring risks

3.2.4. time

3.2.4.1. 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

3.3.4.1. less then 1 month

3.4. Sprint Review

3.4.1. at the end of the sprint

3.4.2. questions

3.4.2.1. what has been done and what hasn't?

3.4.2.2. how preserve problems, discovered during sprint?

3.4.3. time

3.4.3.1. 1 moth sprint

3.4.3.1.1. 4 hours meeting

3.4.3.2. 2 weeks sprint

3.4.3.2.1. 2 hours meeting

4. philosophy

4.1. principles

4.1.1. peoples

4.1.1.1. more important then

4.1.1.1.1. instruments and processes

4.1.2. working product

4.1.2.1. more important then

4.1.2.1.1. documentation

4.1.3. customers

4.1.3.1. more important then

4.1.3.1.1. contract

4.1.4. requirement changes

4.1.4.1. more important then

4.1.4.1.1. plan

4.2. flexible

4.3. customers oriented

4.4. product delivered iteratively