Agile
This is a time-box during which development takes place (typically between 1-4 weeks), the duration of which may vary from project to project.
Sprint/ Iteration
A formal group of stakeholders responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, with all decisions recorded and communicated to stakeholders.
CCB or Steering Committee
This person authorizes the project and provides high-level support.
Sponsor
This document formally authorizes the project and gives the project manager authority to begin work.
Project Charter
This is a listt of project risks, their impact, and planned responses.
Risk Register or Risk Log/ List
This is a short daily meeting (typically no more than 15 minutes) for the development team to synchronize activities and plan for the next 24 hours. Each team member answers just three questions in this meeting.
Daily Stand Up, Stand Up, Daily Coordination Meeting, Daily Scrum
This is a reference point in the project. It is the original project plan, plus or minus approved changes. It is often used to compare actual progress to planned progress.
Baselines
This person leads the team and manages the project work day to day.
Project Mgr.
This traditional artifact breaks the project into smaller, manageable pieces of work.
WBS
This log tracks problems that are happening now and need action.
issues Log
This is an upgrade, enhancement, or replacement that enables a team to deliver the minimum value in the shortest time, making sense for both the business and the customer.
Minimum Business Increment (MBI)
This is a measure of schedule efficiency, expressed as the ratio of earned value to the planned value.
SPI
This person coaches the team and organization in agile practices and helps improve how they work.
Agile Coach
This document identifies project stakeholders and records key information about them.
Stakeholder Register
This extra budget or time is set aside for unexpected work that was not planned for in the risk register.
Management Reserve
This is a package of work that is too large for me to accurately assess in terms of cost. Epics can be broken down into smaller user stories; one is used to group user stories into a single theme.
Epic
This is a step-by-step project management technique for process planning that defines critical and non-critical tasks, aiming to avoid me-frame problems and process bottlenecks.
CPM Critical Path Method
This person helps gather requirements and makes sure business needs are clearly understood.
Business Analyst
This visual board shows work as it moves through stages like to do, in progress, and done.
Kanban Board
This tool ranks risks by how likely they are to happen and how serious their effect would be.
Probability and Impact Matrix
This is the process of reviewing items in the Product Backlog to ensure they are appropriate, prioritized, and estimated. This typically involves adding detail and estimates to items, as well as re-prioritizing and splitting large items.
Backlog Grooming/ Refinement
A distinct, scheduled portion of work performed during the course of a project. NOTE: Tasks are the same thing; however, the term “task” is associated almost exclusively with agile scenarios, while “THIS” is associated almost exclusively with predictive scenarios
Activity
This person is the "face of the customer" on Agile teams.
Product Owner
This chart shows the average amount of work an Agile team completes in each iteration.
Velocity Chart
This risk analysis technique calculates the average financial impact of uncertain events.
EMV Expected Monetary Value