Infographics

1. scrum values
BOLD MOVER V 0.3
(Source: https://www.scrumalliance.org/why-scrum/core-scrum-values-roles )
Focus
Courage
Openness
Commitment
Respect
Because we focus on only a few things at a time, we work well together
and produce excellent work. We deliver valuable items sooner.
Because we work as a team, we feel supported and have more resources
at our disposal. This gives us the courage to undertake greater challenges.
As we work together, we express how we're doing, what's in our way, and
our concerns so they can be addressed.
Because we have great control over our own destiny, we are more
committed to success.
As we work together, sharing successes and failures, we come to respect
each other and to help each other become worthy of respect.
THIS IS SCRUM
INFOGRAPHICS
Agile Manifesto,
Scrum Values
Development Team,
Product Owner,
Scrum Master
Sprint, Sprint Planning,
Daily Scrum, Sprint Review,
Sprint Retrospective
01 Values & Principles
01 Roles
03 Events
Product Backlog,
Sprint Backlog,
Increment
03 Artefects
Product Vision,
Sprint Goal, Definition
of Done, Tracking
03 MISC
BOLD MOVER V 0.3
Agile Manifesto
BOLD MOVER V 0.3
We are uncovering better ways of developing software by
doing it and helping others do it. Through this work we have
come to value:
That is, while there is value in the items on the right, we value
the items on the left more.
This is the so called “Agile Manifesto”. It was written down and signed in 2001 near Salt Lake City in the United States by 17
people, e.g., Kent Beck, Alistair Cockburn, and Ken Schwaber. (Source: http://agilemanifesto.org)
Agile Values
Individuals and interactions over processes and tools Working software
over comprehensive documentation Customer collaboration over contract
negotiation Responding to change over following a plan
Sprint Retrospective
BOLD MOVER V 0.3
(Source: https://www.scrumalliance.org/why-scrum/core-scrum-values-roles )
An inspect and adapt event, where the Scrum Team
reects upon their last Sprint and creates actions to
improve their process.
Once at the end of a Sprint
(after the Sprint Review)
When
Dev Team, PO, SM (facilitates)
Attendees
Experiences From Current Sprint
Input
concrete actions to adapt the process
Output
Time Box:
3 h max./1 mo sprint;
2 h/1-2 w sprint