| Agile PM | A family of incremental, iterative development methods for completing projects.
|
 |
|
|
| Feature | A piece of a product that delivers some useful functionality to a customer.
|
|
|
|
| Iterative incremental development (IID) | A cyclical development process in which a project gradually evolves over time.
|
|
|
|
| Product backlog | A prioritized list of project requirements with estimated time to turn them into complete product functionality.
|
|
|
|
| Product owner | The person responsible for managing the product backlog in Scrum so as to maximize the value of the project. The product owner represents all stakeholders.
|
|
|
|
| Release burndown chart | The trend of work remaining across time. In a release or product, the source of data is the product backlog with work remaining tracked on the vertical axis and number of sprints on the horizontal axis.
|
|
|
|
| Scaling | Adapting Agile PM to large, multi-team projects.
|
|
|
|
| Scrum master | The person responsible for the Scrum process and its correct application.
|
|
|
|
| Scrum meeting | A short status meeting held daily by each team during which the team members synchronize their work and progress as well as report any impediments for removal by the Scrum master.
|
|
|
|
| Self-organizing team | A semi-autonomous team that manages itself.
|
|
|
|
| Sprint backlog | A list of tasks that defines a Scrum team's work for a sprint. Each task identifies those responsible for doing the work and the estimated amount of work remaining on the task on any given day during the sprint.
|
|
|
|
| Sprint burndown chart | The trend of work remaining across time in a sprint. The source of data is the sprint backlog with work remaining tracked on the vertical axis and days of a sprint on the horizontal axis.
|