Você está na página 1de 7

1. What is Scrum? What is Agile?

- Scrum (n): A framework within which people can address complex adaptive
problems, while productively and creatively delivering products of the highest
possible VALUE.
- Scrum has set of Sprint.
- Scrum is founded on empirical process control theory, or empiricism.
- Three pillars uphold every implementation of empirical process control:
transparency, inspection, and adaptation.
- Scrum prescribes four formal events for inspection and adaptation
o Sprint Planning
o Daily Scrum
o Sprint Review
o Sprint Retrospective
- There are three roles in a Scrum project; no less, and no more. We are not allowed
to define any other roles, because it is harmful to the unity of the team, and it is
not compatible with the philosophy of Scrum:
o Product Owner
o Development Team
o Scrum Master
2. What is Sprint?
- Sprint is the heart of Scrum.
- Sprint time-box often from 2 to 4 weeks and limited to one calendar month.
- Sprints contain and consist of the Sprint Planning, Daily Scrums, the development
work, the Sprint Review, and the Sprint Retrospective.
- During the Sprint:
o No changes are made that would endanger the Sprint Goal.
o Quality goals do not decrease.
o Scope may be clarified and re-negotiated between the Product Owner and
Development Team as more is learned.
- In normal, Sprint is over when time-box expires, but ab-normal case, Sprint can be
cancelled before Sprint time-box is over. Only the Product Owner has authority to
cancel Sprint.
- A Sprint would be cancelled if the Sprint Goal becomes obsolete
- When Sprint was cancelled, any completed Product Backlog item are reviewed. If
it releasable, the Product Owner typically accepts it. All incomplete Product
Backlog item are re-estimated and put back to Product Backlog.
3. Responsibilities of the Product Owner, Development Team and Scrum
Master?
a. Product Owner
- The Product Owner is responsible for maximizing the value of the product and the
work of the Development Team.
- The Product Owner is the sole person responsible for managing the Product
Backlog.
- Management includes:
o Clearly expressing Product Backlog items
o Ordering the items in the Product Backlog to best achieve goals and
missions
o Optimizing the value of the work the Development Team performs
o Ensuring that the Product Backlog is visible, transparent, and clear to all,
and shows what the Scrum Team will work on next
o Ensuring the Development Team understands items in the Product Backlog
to the level needed
- The Product Owner is one person, not a committee
b. Development Team
- 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
- Only members of the Development Team create the Increment
- Have following characteristic:
o Self-organizing
o Cross-functional: All of the skills of them necessary to create a product
Increment.
o All team member have only one title role: Developer
o No sub-team in the Development Team.
- Team size require 3-9 person. Optimizing is 7 person +/- 2 person
c. Scrum Master
- The Scrum Master is responsible for ensuring Scrum is understood and enacted
- Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory,
practices, and rules.
- Scrum Master helps Product Owner:
o Finding techniques for effective Product Backlog management
o Helping the Scrum Team understand the need for clear and concise Product
Backlog items
o Understanding product planning in an empirical environment
o Ensuring the Product Owner knows how to arrange the Product Backlog to
maximize value
o Understanding and practicing agility
o Facilitating Scrum events as requested or needed
- Scrum Master helps Development Team:
o Coaching the Development Team in self-organization and cross-
functionality
o Helping the Development Team to create high-value products
o Removing impediments to the Development Teams progress
o Facilitating Scrum events as requested or needed
o Coaching the Development Team in organizational environments in which
Scrum is not yet fully adopted and understood
- Scrum Master helps to the Organization:
o Leading and coaching the organization in its Scrum adoption
o Planning Scrum implementations within the organization
o Helping employees and stakeholders understand and enact Scrum and
empirical product development
o Causing change that increases the productivity of the Scrum Team
o Working with other Scrum Masters to increase the effectiveness of the
application of Scrum in the organization
4. Definition of Product Backlog, Sprint Backlog
a. Product Backlog
- The Product Backlog is an ordered list of everything that might be needed in the
product and is the single source of requirements for any changes to be made to the
product
- The Product Owner is responsible for the Product Backlog, including its content,
availability, and ordering.
b. Sprint Backlog
- 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.
- The Sprint Backlog is a forecast by the Development Team about what
functionality will be in the next Increment and the work needed to deliver that
functionality into a "Done" Increment.
- The Development Team modifies the Sprint Backlog throughout the Sprint, and
the Sprint Backlog emerges during the Sprint.
- Only the Development Team can change its Sprint Backlog during a Sprint.
c. Increment
- 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.

5. Scrum event?

a. Sprint Planning Meeting


- Time-box to maximum of 8 hours for one-month Sprint
- Attended by the Product Owner, Scrum Master, and the Development Team.
- Meeting content:
o What can be delivered in the Increment resulting from the upcoming Sprint
o How will the work needed to deliver the Increment be archive.
b. Daily Scrum Meeting
- Time-box always 15 minutes
- Attended Development Team (require), other role (optional)
- Meeting content:
o What did I do yesterday that helped the team meet the Sprint Goal
o What did I do today to help team meet the Sprint Goal
o Do I have any impediment that prevents me or team from meeting Sprint
Goal
- Scrum Master ensures that Development Team has the meeting.
- Scrum Master teaches the Development Team to keep the Daily Scrum the 15
minutes time-box.
c. Sprint Review Meeting
- Time-box to maximum of 4 hours for one-month Sprint.
- Attended by Scrum Team, key stakeholders invited by the Product Owner.
- Meeting content:
o Product Demonstration
o Product Owner define done and not done
o (Optional) Measure velocity
o Stakeholder feedback
d. Sprint Retrospective Meeting
- Time-box is 3 hours for one-month Sprint
- Attended includes Scrum Team
- Meeting content:
o Inspect how the last Sprint went with regards to people, relationships,
process, and tools
o Identify and order the major items that went well and potential
improvements
o Create a plan for implementing improvements to the way the Scrum Team
does its work
e. Backlog Refinement Meeting (optional)
- Time-box 2 hours for two-week Sprint
- Also call Product Backlog Grooming, Backlog Estimation, and even Story Time.
- It helps the Product Owner get the top of the Product Backlog ready for the next
Sprint Planning Meeting.
- It includes estimation of effort, clarification of requirements, and decomposition of
large Product Backlog items into smaller of a Sprint. Each one should be INVEST
(Independent, Negotiable, Valuable, Estimable, Small, Testable)
6. Practice

1 What is a Scrum Development Team expected to do during the first Sprint?


(choose two)
A. Build a thin slice of potentially shippable functionality
B. Develop a detailed plan for the rest of the project
C. Nail down the architecture
D. Test the product

Scrum teams attempt to build a potentially shippable (properly tested) product


increment every iteration
A team that has not yet learned how to do this should reduce the feature scope it
commit to, or they will soon be hampered by technical debt
2 Who owns Sprint commitments? (Choose one)
A. The Scrum Master
B. The Team owns them collectively
C. Individuals, as determined during the Sprint Planning Meeting
D. Individuals, as assigned by the Scrum Master

During Sprint execution, team member should develop an intrinsic interest in


shared goals and learn to manage each other to achieve them.
3 How is the Product Backlog arranged?
A. Items are random arranged
B. Into categories P1, P2, P3
C. Most important items at the top to least important items at the bottom
D. Large items at the top to small items at the bottom
4 Which is NOT an effective way to encourage collaboration between the Scrum
Development Team and Product Owner?
A. Act as a go-between for them
B. Listen to their communications
C. Teach the Product Owner about technologies the team uses
D. Teach the team to talk in terms of business need and objectives

The Product Owner and Team should talk directly


5 What should happen in the Sprint Review Meeting? (choose three)
A. Declaration by the Product Owner which items are done vs. not done
B. A PowerPoint presentation about hypothetical things
C. Live demonstration of a potentially shippable (properly tested) product
increment.
D. Report about what happen during the Sprint
E. Applause
F. Feedback from stakeholders resulting in additional items added to the
Product Backlog
6 In a Scrum organization, which is a responsibility of management external to the
Scrum Team? (choose one)
A. Help resolve Team-reported impediments and improve the large
organization
B. Monitor the Daily Scrum meetings and reward team players
C. Monitor the Sprint Burndown Chart to ensure individuals are contributing
D. Setup performance appraisals
E. Coordinate activities between Scrum Teams
7 In a good Retrospective, when are decision made?
A. At the end of the meeting, after all Team members have expressed
themselves
B. During the meeting, as soon as someone suggests them
C. At the beginning of the meeting, to avoid discomfor
8 Most organizations that claim to be doing Scrum___
A. Have modified the difficult, uncomfortable parts that could have led to
breakthroughs
B. Are doing it as well as possible

7. g

Você também pode gostar