Scrum / PMSI

Scrum - PMSI Exam

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

1. Sprint Planning / Planejamento da Sprint

1.1. time-boxed

1.1.1. 8 hours for a month-long sprint

1.2. Owner

1.3. Who / Attendees

1.3.1. Scrum Master

1.3.2. Product Owner

1.3.3. Development Team

1.3.4. The Development Team may invite other people to attend the Sprint Planning in order to provide technical or domain advice.

1.4. Tasks

1.4.1. remove or change selected produtc backlog items

1.4.2. Start the sprinit and monitoring progress. keep the product owner aware about the situation

1.4.3. what to do and how to do it

1.4.4. What can be delivered in the increment resulting from the upcoming Sprint?

1.4.5. How will the work needed to deliver the Increment be achieved?

1.5. Goal

1.5.1. Sprint Backlog

1.6. Results/output

1.6.1. Plan for the sprint

1.6.2. Sprint backlog (during the sprint not necessarily at the end)

1.6.3. Sprint Goal

2. Roles

2.1. Scrum Master

2.1.1. Size

2.1.2. servant leader

2.1.3. responsibilities / Responsabilidades

2.1.3.1. remove impediments

2.2. Scrum Owner / Dono do Produto

2.2.1. Size

2.2.2. responsibilities / Responsabilidades

2.2.2.1. Determine and detail the product features and work closely with stakeholders

2.2.2.2. Gather requirements for Product Backlog items

2.2.2.3. Inspect the product increment during the Sprint Review

2.2.2.4. Product backlog - Prioritized by business importance first: the items that result in biggest ROI must be prioritized first.

2.3. Development Team / Time de Desenvolvimento

2.3.1. Size

2.3.1.1. 6 plus or minus 3

2.3.1.2. 3 to 9

2.3.2. Tasks

2.3.2.1. Product backlog item estimated

2.3.2.2. resolving internal team conflicts

2.3.2.3. Organizing the work required to meet the Sprint Goal

3. Scrum Events

3.1. Sprint

3.1.1. time-boxed

3.1.1.1. no more than one month / Less than a month

3.1.1.2. short enough to be able to synchronize the development work with other business events

3.1.1.3. short enough to keep the business risk acceptable to the product owner

3.1.1.4. when does the Sprint end? : When the tome-box expires

3.2. Daily / Reunião Diária

3.2.1. time-boxed

3.2.1.1. fifteen minutes

3.2.2. Owner?

3.2.2.1. Development Team

3.2.3. Who / Attendees

3.2.3.1. Development Team

3.2.3.1.1. The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

3.2.4. Who Required

3.2.4.1. Development Team

3.2.5. Place

3.2.5.1. Effective daily scrum meetings should be held at the same time and at the same place

3.2.5.1.1. the consistency reduces complexity and overhead

3.2.6. Results/output

3.2.6.1. Impediments

3.3. Sprint Review / Revisão da Sprint

3.3.1. tiime-boxed

3.3.1.1. 4 hours for a monthly Sprint; proportionally less for shorter sprints

3.3.1.1.1. assuming a 2-week Sprint, Sprint Review = 2 hours at the enf od every sprint

3.3.2. Who / Attendees

3.3.2.1. scrum team

3.3.2.2. Scrum Master

3.3.2.3. Scrum Owner

3.3.2.4. stakeholders

3.3.2.4.1. The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting

3.3.3. What is?

3.3.3.1. it gives stakeholders an opportunity to inspect the product increments and progress to date, and to provide feedback

3.4. Sprint Retrospective / Retrospectiva da Sprint

3.4.1. time-boxed

3.4.1.1. three hours or less for a one month sprint

3.4.2. Results

3.4.2.1. Definition of "Done"

4. Pillars / Pilares

4.1. Transparency / Transparência

4.2. Inspection / Inspeção

4.3. Adaptation / Adaptação

5. Scrum Values / Valores do Scrum

5.1. Courage / Coragem

5.2. Focus / Foco

5.3. Commitment / Comprometimento

5.4. Respect / Respeito

5.5. Opennes / Abertura

6. Artefatos

6.1. Product Backlog

6.1.1. Owner

6.1.1.1. Product Owner

6.2. Sprint Backlog

6.2.1. Owner

6.2.1.1. Development Team

6.3. Software increment

6.3.1. When

6.3.1.1. whent it makes sense

7. Scrum Framework

7.1. a framework within which complex products in complex environments are developed

7.2. Scrum is a framework for developing, delivering, and sustaining complex product

7.3. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together

8. Terms

8.1. time-boxed

8.1.1. The Event can take no more than a maximum amount of time

8.2. Scrum Team

8.2.1. Scrum team has three roles: product owner, scrum master and the development team members.

9. Definition of "Done"

9.1. Responsible

9.1.1. Development team