Scrum Mindmap

Scrum Mindmap

Get Started. It's Free
or sign up with your email address
Rocket clouds
Scrum Mindmap by Mind Map: Scrum Mindmap

1. Scrum Theorie

1.1. Transparency

1.1.1. Significant aspects of the process must be visible to those responsible for the outcome.

1.2. Inspection

1.2.1. Scrum users must frequently inspect Scrum artifacts and progress towards a Sprint Goal to detect undesirable variances.

1.3. Adaptation

1.3.1. If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted.

2. The Scrum Team

2.1. Product Owner

2.1.1. The Product Owner is responsible f or maximizing the value of the product resulting from work of the Development Team.

2.2. Development Team

2.2.1. The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint.

2.3. Scrum Master

2.3.1. The Scrum Master is responsible for promoting tand supporting Scrum as defined in the Scrum Guide.

3. Scrum Events

3.1. The Sprint

3.1.1. The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created.

3.2. Sprint Planning

3.2.1. The work to be performed in the Sprint is planned at the Sprint Planning.

3.3. Daily Scrum

3.3.1. The Daily Scrum is a 15-minute time-boxed event for the Development Team. At it, the Development Team plans work for the next 24 hours.

3.4. Sprint Review

3.4.1. A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed.

3.5. Sprint Retrospective

3.5.1. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

4. Scrum Artifacts

4.1. Product Backlog

4.1.1. The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product.

4.2. Sprint Backlog

4.2.1. The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

4.3. Increment

4.3.1. The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be “Done,” which means it must be in useable condition and meet the Scrum Team’s definition of “Done.”