Agile Manifesto
The Agile Manifesto favors this over "following a plan"
Responding to change
These are the three roles defined by Scrum
This artifact defines the work needed to build the product
Product Backlog
The purpose of this ceremony is to select valuable work that the team feels it can complete during the next Sprint
Sprint Planning
This is one of "Cliff's universal principles"
People Matter
Focus on Value
Frequent Feedback
Continuous Improvement
The Agile Manifesto favors this over "Processes and Tools"
Individuals and Interactions
This role is accountable for the Product Backlog
Who is the Product Owner?
This artifact represents the set of work required to achieve the Sprint's goals.
Sprint Backlog
The purpose of this ceremony is to establish and coordinate team priorities for the day
Daily Scrum
Daily Standup
This framework can be useful in thinking about how (or whether) self-direction/self-organization are ideal for a team.
Cynefin
This is the Agile Manifesto's highest priority
to satisfy the customer through early and continuous delivery of valuable software
This role helps the team continuously improve
Scrum Master
While not specifically called out as a separate artifact in Scrum, this concept describes the set of backlog items that are both:
- Valuable
- Ready for consideration in Sprint Planning
Prioritized Backlog
This ceremony occurs at the end of the Sprint and is attended by the Scrum Team, as well as any interested Stakeholders
Sprint Review
Demo
This person is generally considered to be the first to have described the "Waterfall" approach
Dr. Winston Royce
The Agile Manifesto holds that this is the most effective Method of conveying information within a team
Face-to-Face Conversation
This Role has autonomy on how to reach team commitments
Development Team
This artifact is the sum of all Product Backlog Items completed during the sprint.
Increment ( Product Increment )
This is the recommended duration range for the Sprint Retrospective
1-3 Hours
This is the decade during which Toyota began developing the Toyota Production System (from which many Lean concepts have been derived).
1940s
This is the location where the Agile Manifesto was written
Snowbird Resort, Utah
This is an important attribute of a Scrum Team
Cross-Functional
Self-Organizing
While not defined by Scrum, this is a common technique for expressing Project Backlog Items (PBIs)
User Stories
While not called-out by Scrum as a distinct ceremony, this activity often occurs iteratively throughout the Scrum lifecycle, but *must* occur during Sprint Planning.
Backlog Refinement
Although the Agile Manifesto is the best overall description of Agile, there are other approaches, all of which are complementary. This is the total number of approaches mentioned in this workshop.
6 total
Lean Manufacturing | Extreme Programming | Scrum | Agile Manifesto | Lean Software Development | Lean Startup