And Agreement between the Product Owner and the rest of the Team that defines when a Story will be complete. The Agreement consists of the Acceptance Criteria, the Doneness Definition, and possibly additional General Agreements. This notion can be extended to Capabilities, Sprints, Releases, and so on… (synonym for Definition of Done)

The act of basing actions on current reality, as opposed to being predictive or plan-driven. 

Any iterative and incremental method or practice that produces Epics and/or Stories for the Backlog. We use agile analysis methods or practices as needed to find a way to proceed with building our product or ‘work result’.

Scrum uses a unique lexicon (glossary) that often confuses many people. These agile terms have been standardized and well defined here to help reduce that confusion and elevate conversation. Well defined terms, allow teams to focus on their work without an endless debate on meaning of the words they use to manage their work.A  Scrum team‘s work is complex enough and scrum’s glossary aim is to maximize the intellectual power that team brings to bear on their product/problem domain.

To be actionable a story must be small, well defined and ready to take to planning. Generally, this means that the Story’s Agreement is a ’10 minute discussion’ away from being agreed to. 

Acceptance Criteria: A description of the objective criteria the team will use to determine whether or not a story achieves the Value it represents. For functional Stories, this is usually a description of an Acceptance Test.

Scrum in a Nutshell is a short introduction to Scrum, describing how a product goes from vision to release. It introduces and defines the scrum team, the backlog and the basic sprint and release processes. It shows how teams use Scrum to develop Products in an agile way.
 

Here we present two ways to monitor the progress of a Sprint,
  1. the Task Hour BurnDown and (part of the original scrum framework)
  2. the Checklist Item BuildUp (which is our preferred solution)
We discuss the pros and cons of each these methods and why we have a preference for the Checklist Item BuildUp. We will also show a work-around that allows it to be generated with most tools when monitoring sprint progress.

 
The Daily Scrum is one of the most important parts of Scrum, as it allows for a daily inspect and adapt cycle. Many people misunderstand the Daily Scrum, and treat it as a simple status update. But, when it is done right these three scrum questions lead into further discussion of great value to the team.

 
Kanban is another agile method that has become popular recently years. It’s main strength is that it does continuous planning rather than batch planning. In this chapter we will describe how it can be integrated into a Kanban(ish) Variant of Scrum. We will see that this is another useful pattern for managing work.