treinamento scrum - english
TRANSCRIPT
![Page 2: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/2.jpg)
WASTE
Never Rarely Sometimes Frequently Always
Research of the Standish Group in the largest US project development firms,
revealed that 64% of features requested by customers are rarely or never used
![Page 3: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/3.jpg)
![Page 4: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/4.jpg)
![Page 5: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/5.jpg)
![Page 6: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/6.jpg)
![Page 7: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/7.jpg)
12 AGILE PRINCIPES
![Page 8: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/8.jpg)
01Continuous delivery and early software
with value: customer satisfaction
![Page 9: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/9.jpg)
02Changes are welcome: competitive
advantage for the customer
![Page 10: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/10.jpg)
03Development in short cycles: frequent
delivery of working software
![Page 11: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/11.jpg)
04Business people and developers must
work together
![Page 12: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/12.jpg)
05Motivated individuals, with support and
confidence
![Page 13: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/13.jpg)
06Face to face conversation is the most effective method of communication
![Page 14: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/14.jpg)
07Working software is the best measure of
the project progress
![Page 15: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/15.jpg)
08Sustainable work pace, no rush and
overtime
![Page 16: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/16.jpg)
09Technical excellence and good design
![Page 17: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/17.jpg)
10Simplicity:
The art of maximizing the unrealized work is essential
![Page 18: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/18.jpg)
11Self-organized teams:
empowerment!
![Page 19: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/19.jpg)
12Continuous improvement: inspection and
adaptation
![Page 20: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/20.jpg)
![Page 21: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/21.jpg)
![Page 22: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/22.jpg)
SCRUM
• Scrum is based on empirical process
• Defined processes say how they should be executed
• When processes are very complicated to define how, empirical processes are recommended
![Page 23: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/23.jpg)
SCRUM
• Transparency
• Inspection
• Adaptation
![Page 24: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/24.jpg)
![Page 25: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/25.jpg)
ROLES: THE SCRUM TEAM
![Page 26: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/26.jpg)
![Page 27: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/27.jpg)
PRODUCT OWNER- Responsible for the backlog and the
value- Ensures the value of work being done
by the team- Ensures that the team understands the
items in the backlog
![Page 28: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/28.jpg)
SCRUM MASTER- Teach Scrum and ensures that it is
followed- Remove impediments
- Eases management of the backlog- Helps in communication
- Facilitates Scrum events as needed
![Page 29: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/29.jpg)
DEVELOPMENT TEAM
- Auto organized;- Multi-functional;
- Does not contain sub-teams.
![Page 30: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/30.jpg)
![Page 31: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/31.jpg)
SCRUM EVENTS
![Page 32: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/32.jpg)
SPRINT• Scrum heart;
• Fixed time (one month or less);
• No changes affecting the sprint goals are performed;
• Does not put or remove people from the team during an Sprint;
• The scope can be renegotiated when more is learned;
![Page 33: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/33.jpg)
PLANNING
• It answers two questions:
• What will be delivered on the next Sprint?
• How the work to achieve the result will be done?
![Page 34: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/34.jpg)
DAILY SCRUM
• What has been achieved since the last meeting?
• What will be done until the next meeting?
• What are the impediments?
![Page 35: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/35.jpg)
SPRINT REVIEW
• Inspects the result of Sprint and adapts the Product Backlog if necessary;
• It is recommended four hours to one month Sprint;
• The Product Owner finds out what was done and what was not done;
• The group collaborates on what to do next;
![Page 36: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/36.jpg)
RETROSPECTIVE• It inspects up as was the Sprint as:
• People
• Relationships
• Processes
• Tools
• It creates a map of gaps and an improvement plan
![Page 37: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/37.jpg)
SCRUM ARTIFACTS
![Page 38: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/38.jpg)
PRODUCT BACKLOG
• Ordered: items are sorted according to priority implementation - in order to maximize customer ROI
• Estimable: judge and form an opinion on the size of the product backlog or a relevant part of it (eg next Sprint or Release.)
![Page 39: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/39.jpg)
PRODUCT BACKLOG
• Emerging: incomplete and dynamic list. The environment evolves and customers and Development Team learn about the product
• Gradually refined: according to the priority
• Top items: smaller granularity, more detail
• Down items: high granularity, minor detail
![Page 40: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/40.jpg)
![Page 41: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/41.jpg)
![Page 42: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/42.jpg)
DYNAMICMyths and Facts
![Page 43: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/43.jpg)
MYTHS AND FACTS: PRODUCT OWNER1. The PO is the "proxy" or customer representative, conveying their wishes to the Development Team
2. Although it should be influenced by different people, the PO is the only one who can modify the Product Backlog
3. The PO must balance the needs and desires of different stakeholders of the project
4. The best PO's own client or someone chosen by him
5. The PO should be only one person - there should be only a decision point on the product to the Development Team
6. The PO usually can accumulate the role of ScrumMaster smoothly
7. The PO should collaborate closely with the Development Team to maximize the value delivered to the customer
8. The PO should charge the Development Team are committed to all items selected for the Sprint are developed
9. The presence of the PO is not mandatory in the Sprint Planning Meeting - simply the Development Team choose items from the top of the Product Backlog
10. The PO is responsible for defining the right product to be developed
![Page 44: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/44.jpg)
1. Myth: The PO is the "proxy" or customer representative, conveying their wishes to the Development Team
2. Although it should be influenced by different people, the PO is the only one who can modify the Product Backlog
3. The PO must balance the needs and desires of different stakeholders of the project
4. Myth: The best PO's own client or someone chosen by him
5. The PO should be only one person - there should be only a decision point on the product to the Development Team
6. Myth: The PO usually can accumulate the role of ScrumMaster smoothly
7. The PO should collaborate closely with the Development Team to maximize the value delivered to the customer
8. Myth: The PO should charge the Development Team are committed to all items selected for the Sprint are developed
9. Myth: The presence of the PO is not mandatory in the Sprint Planning Meeting - simply the Development Team choose items from the top of the Product Backlog
10. The PO is responsible for defining the right product to be developed
MYTHS AND FACTS: PRODUCT OWNER
![Page 45: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/45.jpg)
MYTHS AND FACTS: SCRUM MASTER1. To be effective, the ScrumMaster must have worked as a member of a Development Team
2. The ScrumMaster works for the Scrum be correctly used by teaching and reinforcing the values and rules
3. The ScrumMaster should work to remove impediments to the work of the Development Team, but only those that do not require organizational changes
4. ScrumMaster is the most important role in a project that uses Scrum
5. The ScrumMaster should have good interpersonal skills to facilitate the resolution of conflicts and promote good communication
6. The ScrumMaster must protect the Development Team from outside interference
7. The ScrumMaster must manage the work of the Development Team
8. The ScrumMaster works toward becoming increasingly necessary
9. ScrumMasters who work all hours in that role better carry out their work
10. In an opinion, impose or interfere with work decisions of the Development Team, the ScrumMaster becomes less efficient as facilitator
![Page 46: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/46.jpg)
MYTHS AND FACTS: SCRUM MASTER1. Myth: To be effective, the ScrumMaster must have worked as a member of a Development Team
2. The ScrumMaster works for the Scrum be correctly used by teaching and reinforcing the values and rules
3. Myth: The ScrumMaster should work to remove impediments to the work of the Development Team, but only those that do not require organizational changes
4. Myth: ScrumMaster is the most important role in a project that uses Scrum
5. The ScrumMaster should have good interpersonal skills to facilitate the resolution of conflicts and promote good communication
6. The ScrumMaster must protect the Development Team from outside interference
7. Myth: The ScrumMaster must manage the work of the Development Team
8. Myth: The ScrumMaster works toward becoming increasingly necessary
9. ScrumMasters who work all hours in that role better carry out their work
10. In an opinion, impose or interfere with work decisions of the Development Team, the ScrumMaster becomes less efficient as facilitator
![Page 47: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/47.jpg)
WHAT A USER STORY ISN'T
![Page 48: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/48.jpg)
A MOCKUP
![Page 49: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/49.jpg)
USE CASE
![Page 50: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/50.jpg)
REMINDER
![Page 51: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/51.jpg)
SIMPLE TASK GROUP
![Page 52: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/52.jpg)
WHAT IS USER STORY
![Page 53: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/53.jpg)
WHO?
WHAT?
WHY?
As an <ROLE>, I can/should/would
<FUNCTIONALITY> to <VALUE>
As an buyer, I can SEARCH BOOKS to CHOOSE ONE
AND BUY
![Page 54: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/54.jpg)
ACCEPTANCE CRITERIA
• What will be the format of the alert?
• In which way the alert will be shown?
• Constantly means which frequency?
• How we can know that the order is late?
AN ALERT SHOULD BE CONSTANTLY SHOWN AS THE SOFTWARE DETECTS
AN LATE ORDER
![Page 55: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/55.jpg)
ACCEPTANCE CRITERIA
• Defined the limits of what should be developed for each User Story;
• The Acceptance Criteria guide the team to avoid adding features without value in the functionalities, and at the same time, at the same time ensures the minimum needed to deliver value;
• Are expressed in short and simple phrases;
![Page 56: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/56.jpg)
ACCEPTANCE CRITERIA
• The Acceptance Criterias are added to the User Stories in the refinement sessions of the Backlog;
• Should be written by the Product Owner together with the Team, to obtain a shared understanding of what must be done;
![Page 57: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/57.jpg)
ACCEPTANCE CRITERIA
• The acceptance criteria also guide the team in the definition of Acceptance Tests;
• Acceptance Criteria are part of the Definition of Done.
![Page 58: Treinamento Scrum - English](https://reader031.vdocuments.mx/reader031/viewer/2022013004/55cec5ddbb61eb1e308b464d/html5/thumbnails/58.jpg)