Module2/3_Chapter 3: Development Approaches and Project Life Cycles

Development approach

method used to create and evolve the product, service, or result during the project life cycle, such as predictive, iterative, incremental, adaptive, or hybrid method

Cadence

rhythm of activities conducted throughout the project

Iterative approach

customer provides feedback after every iteration, often done in a set amount of time (e.g., one week, one month, etc.)

Incremental approach

each increment builds on top of the previous one

Project life cycle

series of phases that a project passes through from its start to its completion

Project phase

collection of logically related project activities that culminates in the completion of one or more deliverables

Initiating processes

the actions to begin projects and project phases

Planning processes

the actions that involve devising and maintaining a workable scheme to ensure that the project meets its scope, schedule, and cost goals as well as organizational needs

Executing processes

the actions that involve coordinating people and other resources to carry out the project plans and produce the deliverables of the project

Deliverable

any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project

Monitoring and controlling processes

the actions taken to measure progress toward achieving project goals, monitor deviation from plans, and discuss future plans

Closing processes

the actions that involve formalizing acceptance of the project or phase and bringing it to an orderly end

Template

a file with a preset format that serves as a starting point for creating various documents, so that the format and structure do not have to be re-created

Champion

a senior manager who acts as a key proponent for a project

Project Management Office (PMO)

an organizational entity created to assist project managers in achieving project goals

Stakeholder register

a document that includes details related to the identified project stakeholders

Stakeholder analysis

a technique for analyzing information to determine which stakeholders’ interests to focus on and how to increase stakeholder support throughout the project

Project charter

a document that formally recognizes the existence of a project and provides a summary of the project’s objectives and management

Enterprise environmental factors

conditions, not under immediate control of the project team, that influence, constrain, or direct the project, such as government and industry standards, legal/regulatory requirements, marketplace, conditions, and organizational culture

Organizational process assets

plans, processes, policies, procedures, and knowledge bases, such as templates and lessons-learned reports

Landing

measuring how well the delivered project met the success criteria

Kick-off meeting

the 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

Sprint

a fixed-length event of one month or less where teams work to accomplish the sprint goal

Product owner

person responsible for maximizing the value of the product resulting from work of the development team by managing the product backlog

Scrum master

person responsible for promoting and supporting the Scrum process as defined in The Scrum Guide

Development team

professionals who do the work of delivering a potentially releasable increment of ‘Done’ product at the end of each Sprint

Product vision or product vision statement

a short statement that describes the desired future state that would be achieved by developing and deploying a product

Product strategy

a high-level plan describing what the organization hopes to accomplish with this product and how it plans to do so

Product backlog

an emergent, ordered list of what is needed to improve the product

User story

a description of what a customer or user would want from a product or solution

Product release plan

a tactical document that spans only a few months and is used internally for the development teams

Features

services that fulfill user needs

Assumption log

document used to record and track assumptions and constraints throughout the project life cycle