Jetzt loslegen. Gratis!
oder registrieren mit Ihrer E-Mail-Adresse
SCRUM von Mind Map: SCRUM

1. Roles

1.1. Scrum Master

1.1.1. Not a Project Manager

1.1.2. Facilitator, kinda Delivery Manager whith some strict functions

1.2. Product Owner

1.2.1. ROI (Return On Investement)

1.2.2. Final Arbitier on Requirements

1.2.3. Focus on WHAT, not on HOW

1.3. Dev Team (4..9 persons)

1.3.1. Cross-functional

1.3.2. Make Shippable Product every iteration

1.3.3. Collaborative

1.3.4. Self-organizing

2. Artifacts

2.1. Independent Negotiable Valuable Estimable Small Testable

2.1.1. Specific Measurable Achievable Realistic Time-boxed

2.2. Product Backlog: anyone can add PBI (Product Backlog Items) - User Story or Use Case Scenario. PO sets Priority.

2.2.1. Item PBI1 priority 100

2.2.2. Item PBI2 priority 100

2.2.3. Item PBI3 priority 50

2.2.4. Item PBIn priority Pn

2.3. Sprint Backlog

2.3.1. Item SBI1 priority 100 Task 1 Task 2 Task N

2.3.2. Item SBI2 priority 50 Task 1 `Task 2 Task N

2.3.3. Item SBIm priority Pm Task 1 `Task 2 Task N

3. Meetings

3.1. Backlog Refinement Meeting (some days before Sprint's end).

3.1.1. Estimations of effort

3.1.2. Requirements clarification

3.1.3. Decomposition of large PBIs

3.2. Sprint Planning

3.2.1. Before we start. Commiting PBI to SBI. 4 hours.

3.3. Daily Scrums

3.3.1. Every morning. Discussing, what have we done yesterday, what are we going to do today, blokers, accents and so on. 15 mins. Allthe sidebar topics should be collected and discussed in other way and time.

3.4. Sprint Review

3.4.1. PSP demonstration. Acceptance criteria checks.

3.4.2. PO declares what's done or not (commited PBIs)

3.4.3. Measure velocity (optional) - the sum of Story Points in all the Done PBIs

3.4.4. Stakeholder feedback

3.4.5. Adding PBIs if needed

3.5. Sprint Retrospective Process <-> Product

3.5.1. Safety Check: every Team Member sets the status of comfort in SR meeting (anonimly).

3.5.2. Classic Scrum Retrospective What went well, what did we learn (pluses)? What could be improved, what sill puzzles us (deltas)? Actions (set after pluses and deltas discussed)

3.5.3. Focused Conversation Principles: Decisions Come Last (O)bjective questions - What happened? (R)eflective questions - How do we feel about it? (I)nterpretive questions - What does it mean? (D)ecision questions - What should we do?

3.5.4. Silent Writting Everyone writes a Post-It note of the finished Sprint, 10 mins Stick the notes on a board. Maybe group. Discuss every note. Write the Actions to impove discussed cases

3.5.5. Timeline Retrospective Draw a line for the Sprint's time Everyone recollects the events of the Sprint and sticks them on the timeline. Read&Discuss

3.5.6. Decisions After everything is discussed No Scrum Master, Team only

3.6. Release Planning = Sprint 0

3.6.1. Definition of Done

4. Criteria

4.1. Defenition of Done (for all of PBIs)

4.1.1. Properly tested

4.1.2. Refactored

4.1.3. Potentially shippable

4.2. Acceptance Criteria

4.2.1. Must be set for every Story

4.3. No "Partly Done", nothing is Done until it hits DoD and AC. All the inprovement of Done PBI shold be added as new PBIs.

5. Epics: large story that cannot be completed in a single sprint. It is a Story, so it has a single Acceptance Criteria.

6. Theme: group of user stories that share a common attribute, and for convenience they are grouped together. It is a group of Stories with all their own attributes. Kinda Subproject.