Are you looking for a one-page summary of Agile principles and the Scrum framework? Look no further.
We’ve developed this one page summary and hand it out during our agile and scrum training sessions to promote agile learning.
Download this handy desk reference to get a well-formatted and print-ready PDF. The document contains the 4 Agile Values, 12 Agile Principles and a quick summary of the Scrum Roles and Events from the Scrum Framework. Teams that are new to Agile and Scrum have found this summary as a tool to help the improve how they work together
The 4 Agile Values
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
We follow these principles:
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity–the art of maximizing the amount of work not done–is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Summary of the Events in the Scrum Framework
- Sprint Planning – Generally two parts or topics. Part one is the focus on WHAT the Product Owner wants the team to work on. Part two is for the team to determine how to get the work done.
- Daily Scrum – The Daily Scrum is a short meeting for the Development Team to synch their efforts, assess progress toward their sprint goal, and plan for the day ahead.
- Backlog Refinement – Backlog refinement is a Scrum Team activity where the Development Team works with the Product Owner and Stakeholders to refine future backlog items and get them ready for the sprint.
- Sprint Review – The Sprint Review is an inspection of the output of the sprint. It allows the team to demonstrate their progress and showcase product and get feedback.
- Sprint Retrospective – The Retrospective is an event where the Development Team meets to discuss how to improve their process to make it more effective and enjoyable.
Download Your Agile Principles and Scrum Cheat Sheet Now
You can download your copy of this the Agile Principles and Scrum Cheat Sheet here. Please let us know if you find it helpful.
If you like this, you might also find the links on our Agile Coaching Resources page helpful. We’ve created a concise index to all our posts related to Scrum Mastering and Agile Coaching.
Here are some additional posts on the Scrum Framework that you might find helpful: