Chapter 3 - Project Management Processes Flashcards

1
Q

Project life cycle

A

The performing organization’s methodology for managing a project, i.e. the logical breakdown of what you need to do to produce the deliverables of the project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Development life cycle

A

The collective phases within the project life cycle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the development life cycle used for?

A

To ensure that the expected/planned result of each phase is achieved

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Difference between the project life cycle and project management process

A
  • The project life cycle is what you need to do the work
  • The project management process is what you need to do to mange the work
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Plan-driven project life cycle

A

Plan-driven projects have predictive development life cycles that require scope, schedule, and cost to be determined in detail early in the life of a project - before the work begins to produce the project deliverables

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Change-driven project life cycle

A
  • Change-driven projects use iterative, incremental, or adaptive (agile) development life cycles, and have varying levels of early planning for scope, schedule, and cost
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Incremental development life cycle

A

Delivers a complete, usable portion of the product for each iteration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Iterative development life cycle

A

The complete concept is built in successive levels of detail to create the end result

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Adaptive development life cycle

A
  • Involves a fixed schedule as well as fixed costs
  • Scope is broadly defined, with the understanding that it will berefined throughout the project
  • The customer’s requirements are documented and prioritized in a backlog
  • Work is planned in short increments to allow the customer to change and reprioritize requirements within the time and cost constraints
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Hybrid development life cycle

A

Combination of a predictive and adaptive life cycle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

In hybrid development life cycle approach, where to use preditive life cycle?

A

Used to manage the project requirements that are well defined

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

In hybrid development life cycle approach, where to use adaptive life cycle?

A

Used to manage the requirements that are less clear

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Phase gate

A
  • Occurs at the end of each phase
  • Involves analyzing the results of the completed phase by comparing the results of the phase with the business documents, the project charter, and the PMP
  • Based on the analysis, a decision is made whether to redo the phase, move forward with the next phase, or choose not to continue with the project
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Key points of Initiating phase

A
  • PM decides whether the business case and benefits management plan can be achieved, and does high level planning to see if project can be completed given the constraints, scope, risks, etc.
  • Stakeholders are identified
  • Stakeholder analysis is performed
  • Project is formally authorized when the sponsor signs the project charter
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Major actions in Initiating phase

A
  • Develop project charter
  • Identify stakeholders
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Outputs of Initiating phase

A
  • Project charter
  • Stakeholder register
17
Q

Progressive elaboration

A

The process of continually refining estimates and scope definition

18
Q

Reasons why project initiating is begun

A
  1. There’s a business need
  2. A new phase of the project has begun
  3. The project has so many problems that you reevaluate the business need
19
Q

Key points of Planning phase

A
  • PMP is developed, including plans for how to plan, execute, M+C, and close the project
  • When PMP is complete, the sponsor approves it
20
Q

Major actions of Planning phase

A
  • Develop PMP
  • Plan scope management
  • Collect requirements
  • Define scope
  • Create WBS
  • Plan schedule management
  • Define activities
  • Sequence activities
  • Estimate activity durations
  • Develop schedule
  • Plan cost management
  • Estimate costs
  • Determine budget
  • Plan quality management
  • Plan resource management
  • Estimate activity resources
  • Plan comms management
  • Plan risk management
  • Identify risks
  • Perform qualitative/quantitative analysis
  • Plan risk responses
  • Plan procurement management
  • Plan stakeholder management
21
Q

Reasons for entering project Planning

A
  • Project initiating is complete
  • Project executing necessitates ongoing planning
  • Project M+C necessitates additional planning
22
Q

Outputs of Planning phase

A
  • PMP
  • Project documents that guide execution and control of the project
23
Q

Rolling wave planning

A
  • A form of progressive elaboration, where the earliest parts of the project are planned in sufficient detail for work to begin
  • Later phases are planned at a high level
  • As the project progresses, plans are elaborated in sufficient detail to accomplish the work
24
Q

Project scope statement

A

Consists of the following:

  • Description of the project deliverables
  • Work required to complete the deliverables
  • Acceptance criteria for the deliverables
25
When to return to the Planning phase?
* **New stakeholders** are identified * **New risks** are identified * **Rolling wave planning** * **New info** becomes available through **progressive elaboration**
26
Key points of Executing phase
* Team **completes work** according to **PMP** * Focus is on **leading** and **managing** the project
27
Major actions of Executing phase
* **Direct and manage work** * **Manage project knowledge** * **Acquire resources** * **Develop team** * **Manage team** * **Manage comms** * **Implement risk responses** * **Conduct procurements** * **Manage stakeholder engagement**
28
Reasons for entering Executing phase
* **Project planning** is **completed** * **PICC results** in a **changed PMP**
29
Focus of Executing phase
**Managing** the **people, physical resources**, and the **work to accomplish** the project as planned
30
Focus of M+C phase
**Ensuring** the project is **progessing** according to the plan, and **approving necessary changes** to the plan to meet the organization's **strategic objectives** and **delvier the expected benefits**
31
Monitoring
* Requires the PM to focus their attention on **how the project is progressing** * PM must assess **how stakeholders** are **participating, communicating,** and **feeling about the project,** the **work,** and the **uncertainties that have been identified**
32
Controlling
Requires **evaluating hard data** on **how the project is conforming to the PMP** and taking action to **address variances** that are outside of acceptable limits
33
Key points of M+C phase
* **Progress is assessed** according to the **baselines** established in the PMP * If **variances** occur that warrant **changes**, the changes are evaluated in the **Perform Integrated Change Control (PICC)** process to **determine their impact** on the project, **identify** the **best options** for **dealing** with them, and decide whether they should be **approved/rejected/deferred**
34
Reasons for entering M+C phase
* **Requested changes, including recommended corrective and preventive actions and defect repair, from all sources** * **Work performance data** * **Deliverables**
35
Major actions of M+C phase
* **Monitor and control work** * **PICC** * **Monitor/control knowledge areas, i.e.,:** * **Validate/control scope** * **Control schedule** * **Control costs** * **Control quality** * **Control resources** * **Control procurements** * **Monitor comms** * **Monitor risks** * **Monitor stakeholder engagement**
36
Key points of Closing phase
* Includes **admin activities** and **technical work** to **confirm that the final product is acceptable** * Will also include any work needed to **transfer the completed project** to those **who will use it** and to **solicit feedback** from the customer
37
Reasons for entering Closing phase
* **Project phase is complete** * **Project is complete** * **Project is terminated**
38
In what phases can changes be requested?
**Executing** and **M+C,** and in **P****lanning**during**rolling wave planning**
39