Term
|
Definition
| An approach to managing projects that includes an iterative workflow and incremental delivery of software in short iterations. |
|
|
Term
|
Definition
| A useful object created by people |
|
|
Term
|
Definition
| A chart that shows the cumulative work remaining in a sprint on a day-by-day basis. |
|
|
Term
|
Definition
| Formalizing acceptance of the project or project phase and ending it efficiently. |
|
|
Term
|
Definition
| A short meeting in which the team shares progress and challenges. |
|
|
Term
|
Definition
| Coordinating people and other resources to carry out the project plans and create the products, services, or results of the project or project phase. |
|
|
Term
|
Definition
| Defining and authorizing a project or project phase. |
|
|
Term
|
Definition
| A meeting held at the beginning of a project so that stakeholders can meet each other, review the goals of the project, and discuss future plans. |
|
|
Term
|
Definition
| A description of how things should be done. |
|
|
Term
| Monitoring and controlling processes |
|
Definition
| Regularly measuring and monitoring progress to ensure that the project team meets the project objectives. |
|
|
Term
|
Definition
| Devising and maintaining a workable scheme to ensure that the project addresses the organization’s needs. |
|
|
Term
|
Definition
| A series of actions directed toward a particular result. |
|
|
Term
|
Definition
| A single list of features prioritized by business value. |
|
|
Term
|
Definition
| The person responsible for the business value of the project and for deciding what work to do and in what order when using a Scrum method. |
|
|
Term
| Project management process groups |
|
Definition
| The progression of project activities from initiation to planning, executing, monitoring and controlling, and closing |
|
|
Term
| PRojects IN Controlled Environments (PRINCE2) |
|
Definition
| A project management methodology developed in the United Kingdom that defines 45 separate subprocesses and organizes these into eight process groups. |
|
|
Term
| Rational Unified Process (RUP) framework |
|
Definition
| An iterative software development process that focuses on team productivity and delivers software best practices to all team members. |
|
|
Term
| Scrum team or development team |
|
Definition
| A cross-functional team of five to nine people who organize themselves and the work to produce the desired results for each sprint. |
|
|
Term
|
Definition
| A person who ensures that the team is productive, facilitates the daily Scrum, enables close cooperation across all roles and functions, and removes barriers that prevent the team from being effective. |
|
|
Term
|
Definition
| DMAIC (Define, Measure, Analyze, Improve, and Control) is used to improve an existing business process, and DMADV (Define, Measure, Analyze, Design, and Verify) is used to create new product or process designs. |
|
|
Term
|
Definition
| A set period of time, normally two to four weeks, during which specific work must be completed and made ready for review when using Scrum methods. |
|
|
Term
|
Definition
| The highest-priority items from the product backlog to be completed in a sprint. |
|
|
Term
|
Definition
| A document that includes details about identified project stakeholders. |
|
|
Term
|
Definition
| Best practices for what should be done. |
|
|
Term
|
Definition
| Short descriptions written by customers of what they need a system to do for them. |
|
|
