- Jul 2019
-
Local file Local file
-
Iterative Life Cycles
Prototyping is key to this life-cycle.
-
The Predictive Model
These models will have the most number of decision or phase gates - formal steps where a stakeholder is signing off on what was acocmplished - some product or result.
Biggest flaw here is that once you complete a phase, you can't go back to anything in a previous step. In real life, this often is not the case... you modify designs, analyze more... learn things and change. This makes this difficult to handle when you learn things; model resists change.
-
Adaptive life cycles
Main difference here is shortness of cycles, and focus on process improvement / continuous improvement
-
Project management process group
PMI would argue that all life cycles and projects use these process groups. But, you are not required to do all of these things in perfect order. They argue that in most projects, there is a certain amount of iteration.
-
Project Management Process Groups are NOT project phases
Key distinction for exam questions... I think phases are going to be determined by the specific life cycle method. phase = logically related activities that culimate in completion of one or more deliverables.
-
PMBOK® Guide 6th Ed. p.18
-
Deming’s PDCA Cycle and the PMI® Process Model
Most frameworks are going to be based on this - most lifecycle approaches have at least 4 or 5 steps, and you are doing some version of these activities in each. Some have iterative looping phases, or don't loop (predictive model). Basically all other methodologies loop.
-
PMI® describes three types of PMOs that each have varying degrees of control and influence over the project. These include
-
Directive
This is the type of PMO likely found in a strong matrix organization, where the project managers report to the PMO (they do not report to the PMO in the other cases.
-
Supportive
Really just available resources. PMs don't report to this type of group. Has very little power or control over projects.
-
Iterative and Incremental
Looping projects...
-
Predictive
standard for engineering, or rigid software development. Unique in that a large percentage of time and effort goes into the planning, because everything must march along according to the set plan. 25% of schedule and budget could be spent here.
-
For the PMP® exam, it is important that you can compare and contrast projects and operations. Here are the common characteristics held by projects:
distinguish projects and operations -
-
Adaptive
Agile really fits in here. good for high levels of stakeholder involvmenet and change. Might not understand what the final product or deliverable really is. Distinguish from iterative or incremental because they are similar
-
Project Life Cycle
the most basic structure of project management. If you're really informal, you'd probably start by establishing a life cycle strategy of some kind
-
Management by Objectives (MBO)
Similar to KPI process - almost identical
-
It is different from iterative development because it does not focus on a single release of the product, service or result and it typically makes use a complete team instead of one broken by functional areas.
distinction from Iterative styles
-
prototype
Prototyping goes hand in hand with Spiral methodology.
-
PMI® describes life cycles as generally either being adaptive or predictive. In the simplest terms, these two concepts represent constantly evolving planning where the project is broken into small components over a less determined timeline versus project planning that is done in a linear fashion with a specific development plan structured specific scope, schedule and cost estimates.
Key distinction - adaptive vs. predictive
-
In general, you should imagine that you are leading a project that combines at least 50 to 100 resources from several continents and that lasts more than a year and has a value of greater than U.S. $1,000,000. Furthermore, you should assume that your project goes through a formal review and prioritization process within your organization.
Type of project to consider when answering questions
-
A portfolio is a grouping of related and unrelated projects and programs that are grouped for
...visibility and control purposes
-
A program is a group of related projects managed in a coordinated way.
The projects involved in the program are connected in some way that justifies adding the management expense and effort required to coordinate them.
-
Operations manage the existing processes, products, services, or
Operations Definition
-
-
faspa.ir faspa.ir
-
PMBOK® GuideKey Component
Review terms
Tags
Annotators
URL
-