AGILE & SCRUM CHEAT

4 AGILE VALUES
SHEET 12 AGILE PRINCIPLES
We are uncovering better ways of [Link] highest priority is to [Link] projects around 9. Continuous attention to
4 SCRUM ROLES
SCRUM TEAM
developing software by doing it and helping SATISFY THE CUSTOMER motivated individuals. Give TECHNICAL The Scrum Team is 10 or
others do it. Through this work we have them the environment and fewer people including one
through early and continuous EXCELLENCE and good Product Owner, one Scrum
come to value: delivery of valuable solutions. SUPPORT they need, AND Master and Developers.
design enhances agility.
TRUST them to get the job
INDIVIDUALS & done.
2. WELCOME CHANGING PRODUCT OWNER
INTERACTIONS [Link]--the
REQUIREMENTS, even late A single decision-maker who
Over Processes [Link] most efficient and art of maximizing the is responsible for prioritizing
in development. Agile
and Tools. effective method of conveying amount of work not done-- the backlog and maximizing
processes harness change
for the information to and within a is essential. the
WORKING SOFTWARE development team is FACE-TO- value delivered by the Scrum
Over Comprehensive Documentation. customer's competitive
FACE CONVERSATION. Team.
advantage.
[Link] best architectures, DEVELOPERS
requirements, and Cross-functional team of 3-9
CUSTOMER COLLABORATION [Link] WORKING 7. WORKING
designs emerge from people who plan, adapt and
Over Contract Negotiation. SOLUTIONS FREQUENTLY, SOLUTIONS hold each other accountable
from a couple of weeks to a SELF-ORGANIZING
are the primary measure of TEAMS. to deliver a usable increment
couple of months, with progress. each sprint.
RESPONDING TO CHANGE a preference to the shorter
Over Following a Plan. timescale. [Link] regular intervals, the SCRUM MASTER
8. Agile processes promote
SUSTAINABLE DEVELOPMENT. team REFLECTS on how to A True Leader who serves,
That is, while there is value in the items on [Link] people The sponsors, developers, and become more effective, coaches and supports the
the right, we value the items on the left and developers must users should be able to then tunes AND ADJUSTS Scrum Team, Product Owner
more. WORK TOGETHER maintain a constant pace its behavior accordingly. and Org to adopt Scrum as
daily indefinitely. defined in the Scrum Guide.
throughout the project.
5 SCRUM EVENTS
THE SPRINT SPRINT PLANNING DAILY SCRUM SPRINT REVIEW RETROSPECTIVE
PURPOSE – The sprint is a fixed PURPOSE - Understand WHY the PURPOSE – Inspect progress PURPOSE - Demonstrate progress, PURPOSE - Allow the Scrum team to
length event up to a month in length Sprint is valuable, WHAT prioritized toward the sprint goal, coordinate inspect the team results and get pause, reflect and plan ways to
where all the work is completed to items the team will work on and HOW efforts and adapt plans. feedback for future adaptations. improve team quality and effectiveness.
turn ideas into value. Considered the team will complete the work.
the heartbeat of Scrum. 1. The Scrum 1. Retrospectives are FOR
1. The SCRUM TEAM IS 1. The Team should show actual THE SCRUM TEAM and
RESPONSIBLE for planning Daily Scrum is for the working RESULTS FROM the team decides who
1. Every Sprint should
DEVELOPERS to THE USER’S should attend.
be the SAME each backlog item and taking
improve communication PERSPECTIVE.
LENGTH. on a realistic amount of work and decision-making. Don’t show lines of code
based on their capacity and 2. NO BLAMING OR
past performance. or
2. As soon as one [Link] format can PowerPoint. COMPLAINING. Assume
Sprint ends, the NEXT vary but the FOCUS is that everyone did the
SPRINT BEGINS. 2. The Scrum Team PLANS on hitting the SPRINT best
THE WORK TOGETHER with 2. GET ORGANIZED,
GOALS. they could under the
start circumstances.
the goal of completing the on time and be succinct.
3. The meeting should
work together. Plan for 4-5 minutes per 3. Use ROOT CAUSE
3. The Sprint is a last
completed backlog item and ANALYSIS to go beneath
container for all the LESS THAN 15
3. The Sprint Goal, selected leave time for engagement the surface. Select just
other SCRUM MINUTES
Backlog Items and plan for with stakeholders. one or two improvement
EVENTS. and be held at the same
delivering them is called the actions each sprint.
time and place every
SPRINT BACKLOG. 3. EXPECT FEEDBACK
working day of the sprint.
including new requests.
W W W .V I TA LI TYCHI CA [Link] DECEMBER 20 2
1