SCRUM

SCRUM

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

1. Artifacts

1.1. Product Backlog

1.2. Sprint Backlog

1.3. Increment

1.3.1. Definition of "Done"

2. Scrum Events

2.1. The Sprint

2.2. Sprint Planning

2.3. Daily Scrum

2.4. Sprint Review (or Demo)

2.5. Sprint Retrospective

3. Three Pilars of Scrum

3.1. Transparency

3.2. Inspection

3.3. Adaptation

4. Values

4.1. Courage

4.2. Focus

4.3. Commitment

4.4. Respect

4.5. Openness

5. Created by

5.1. Jeff Sutherland

5.2. Ken Schwaber

6. Main Roles

6.1. Scrum Master

6.2. Product Owner

6.3. Scrum Team

7. Pros and Cons

7.1. Advantages

7.1.1. One of the greatest benefits of Scrum is that it not only allows you to respond to change, it embraces change.

7.1.2. Scrum requires a culture of empowerment, self-organising teams, continuous change and improvement. This culture requires support at management-level downwards in order to instil the ethos into an organisation that can make it more Agile.

7.1.3. Scrum grew out of empirical process control theory, or empiricism. The fundamental principle of Empiricism is that knowledge comes from experience and making decisions based on what is known.

7.1.4. Scrum uses an iterative and incremental approach to optimize predictability and control risk.

7.2. Disavantages

7.2.1. Scrum often leads to scope creep, due to the lack of a definite end-date.

7.2.2. The chances of project failure are high if individuals aren't very committed or cooperative.

7.2.3. Adopting the Scrum framework in large teams is challenging.

7.2.4. The framework can be successful only with experienced team members.

7.2.5. If any team member leaves in the middle of a project, it can have a huge negative impact on the project.

8. Waterfall vs Agile

8.1. Waterfall works best for projects completed in a linear fashion and does not allow going back to a prior phase.

8.2. Agile focuses on adaptive, simultaneous workflows. Agile methods, like SCRUM or KANBAN, break projects into smaller, iterative periods.

8.2.1. Kanban is primarily concerned with process improvements.

8.2.2. Scrum is concerned with getting more work done faster.

9. ScrumBut

9.1. Syntax

9.2. Examples

9.2.1. "(We use Scrum, but) (having a Daily Scrum every day is too much overhead,) (so we only have one per week.)"

9.2.2. "(We use Scrum, but) (Retrospectives are a waste of time,) (so we don't do them.)"

9.2.3. "(We use Scrum, but) (we can't build a piece of functionality in a month,) (so our Sprints are 6 weeks long.)"

9.2.4. "(We use Scrum, but) (sometimes our managers give us special tasks,) (so we don't always have time to meet our definition of done.)"