Project Management Framework Flashcards
Enterprise environmental factors
Company culture and existing systems (e.g. organization structure, hierarchy)
Organization process assets
An organization’s existing processes, procedures and historical information - Processess, procedures, policies -
Corporate knowledge base
assume the organization has information such as historical records and lessons learned from previous projects and the the company has incorporated those records into an indexed corporate knowledge base available to all
Historical information
record of past projects: activities, lessons learned, WBS, benchmarks, reports, risks and risk response plans, resources used, estimates, project management plans, correspondence
Lessons learned
Lessons learned include the causes of the issues, change requests, workarounds, reestimating, preventive and corrective actions and defect repair the project faced and reasoning behind the change implemented
- technical aspects of the project:what was right and wrong about how we completed the work to produce the product
- Project management: how did we do with WBS creation, risk planning, etc
- Management: How did I do with communication and leadership as a PM
Constraints
time, cost, risk, scope quality, resources and customer satisfaction
Matrix Org Structure
both functional and projectized structure (two bosses - PM & functional manager).
Communication from team > both bosses.
Do project work in addition to department work.
- weak - PM hold little power over personnel. Expeditor or coordinator
- balance - authority is balance btwn functional & PM. Resources focused on project part-time. Power of Pm is comparable to project coordinator or expediter
- Strong - PM has control + budget authority.
Functional Org Structure
Functional - organizations grouped by a function e.g. Departments “silos”.
Projects generally occur within a single department. Communication from employee to department head > department head (from second functional group). Communication stays within the project. Team complete project + department work.
- PM authority - little to none
- resource control - little to none
- Budget control - functional manager
projectized Org Structure
the entire company is organized by projects and the PM has control of the project. (“No home”). Communication primarily occurs within the project.
- PM authority - High to total
- Resource Control - high to total
- budget control - PM
Project expediter
acts primarily as a staff assistant and communications coordinator. He expediter cannot personally make or enforce decisions.
Project coordinator
this position is similar to the project expediter, except the coordinator has some power to make decisions, some authority and reports to higher level manager.
Predictive project life cycle
predictive - plan-driven project have predictive life cycles, and will have varying levels of early planning for scope, schedule and cost.
- clearly different work takes place in each phase
- major changes to team composition often take place at project milestones
- preferred when deliverable is well understood, based on established practices, and lacks value until fully complete
Incremental project life cycle
incremental - involve early planning ofhigh-level scope sufficient enough to allow for preliminary estimates of time and cost; scope is developed a little more with each iteration. Incremental delivers a complete, usable portion of the product for each iteration.
iterative project life cycle
iterative - Same as incremental. With iterative, the complete concept is build in successive levels of detail to create the end result
- develops product through series of repeated cycles
- Incremental development process with careful change mangement
- Helpful when objectives and scope are subject to change
Adaptive project life cycle
adaptive - Involved fixed time and cost, and scope is broadly defined with the understanding that it will be refined as the project progresses. Work is planned in quick, brief increments to allow the customer to change and reprioritization requirements within time and cost constraints.
- similar to iterative model, but on a faster pace, often 2-4 week cycles
- ideal in rapidly changing environments when scope is hard to define fully in advance
- often used when partially completed products offer value to stakeholders as development continues