2. Organizational Influences and Project Lifecycle

Laten we beginnen. Het is Gratis
of registreren met je e-mailadres
2. Organizational Influences and Project Lifecycle Door Mind Map: 2.  Organizational Influences and Project Lifecycle

1. Stakeholder

1.1. Individual, group or org. who may affect or be affected by the project

1.2. Internal / external

1.3. Responsibility & authority may change

1.4. Continuous identification process

1.5. Expectations to be managed by the stakeholder

1.6. Examples

1.6.1. Sponser

1.6.1.1. Provides resources & support

1.6.2. Customer / user

1.6.2.1. Approve project

1.6.3. Sellers / Business partners

1.6.4. Organizational group / Fnctal mngr

2. Project governance

2.1. Oversight function aligned with governance model & encompasses life cycle

2.2. Provides structure, processes, decision-making models & tools for managing

2.3. Controls the project while assuring success by defining & documenting

2.4. Defined by portfolio, program or sponsoring

2.5. Separate from org's governance

2.6. Describe in PM plan

3. Project success

3.1. Completion

3.2. Scope

3.3. Time

3.4. Cost

3.5. Quality

3.6. Resources

3.7. Risk

3.8. Include test period

4. Project Lifecycle

4.1. Phases from initiation to closure

4.1.1. Broken down by objectives, results or milestones

4.1.2. Time-bounded

4.2. Documented within a methodology

4.3. Kinds

4.3.1. Predictive

4.3.1.1. Product & deliverables defined at beggining & changes are managed

4.3.1.2. "Fully plan-driven"

4.3.1.3. Scope, time & cost determined ASAP

4.3.1.4. Sequential/overlapping

4.3.1.5. CHanges carefully managed and have to be accepted after re planning

4.3.1.6. Preferred when product's well understood

4.3.1.7. "Rolling wave planning"

4.3.1.7.1. More general plan is available and more detailed planning is done when it arrives

4.3.2. Adaptative / Change-driven / Agile methods

4.3.2.1. Product's developed over iterations and scope is defined with detail when began

4.3.2.2. If scope and reqs are tough to define in advance

4.3.2.3. Respond to lots of change & stakeholder involvement

4.3.2.4. ALSO ITERATIVE & INCREMENTAL

4.3.2.4.1. But iterations are GAVE fast (2-4 weeks)

4.3.2.5. Small incremental improvements that add value

4.3.3. Iterative & Incremental

4.3.3.1. To reduce complexity with objectives & scope change

4.3.3.2. Project phases repeat

4.3.3.3. Sequential/overlapping

4.3.3.4. High-level vision & detailed scope's done 1 iteration at a time

4.4. Generic structure

4.4.1. DIFFERENT FROM PM PROCESS GROUPS

4.4.2. Costs are low, peak and drop quickly

4.4.3. Start

4.4.4. Organize & prepare

4.4.5. Carry out

4.4.6. Close

4.5. Independent from product lifecycle

5. Project phases / iterations

5.1. Collection of logically related project activs. that end in deliverables

5.2. Used when nature of the work is unique to a portion of the project or linked to a bigger deliverable

5.3. May overlap (might be beneficial)

5.4. State gate = milestone = phase review = phase gate = kill point

5.5. NO single ideal structure

5.6. Types of Project-Phase relationships

5.6.1. Sequential

5.6.1.1. Phase starts when previous's complete

5.6.1.2. Eliminates reducing- time option

5.6.2. Overlapping

5.6.2.1. Phase starts prior to previous completion

5.6.2.2. Fast tracking - Schedule compression technique

5.6.2.3. Possible additional resources

5.6.2.4. May increase risk or rework

6. Organizations

6.1. Systematic arrangements of entities (people or depts) aiming to accomplish purposes while overtaking tasks

6.2. Cultural Norms

6.2.1. Group of phenomena that develop over time

6.2.1.1. Organizational Culture

6.2.1.1.1. Shaped by common experience

6.2.1.1.2. Unique

6.2.1.2. Styles

6.2.2. Established approaches to initiating and planning projects

6.2.3. Acceptable means to get work done

7. Organizational Structures

7.1. Enterprise environmenal factor

7.2. Affects resources

7.3. Types

7.3.1. Functional

7.3.1.1. (Clear Hierarchy)

7.3.1.2. (Grouped by specialty)

7.3.1.3. (Independence)

7.3.2. Matrix (dedicated & part-time)

7.3.2.1. Weak Matrix

7.3.2.1.1. (Coordinating PM)

7.3.2.2. Balanced Matrix

7.3.2.2.1. (PM under Functional mngr)

7.3.2.3. Strong Matrix

7.3.2.3.1. (Full-time PM)

7.3.3. Projectized

7.3.3.1. (Virtual collaboration)

7.3.3.2. (Depts)

7.4. Project Characteristics

7.4.1. Project mngr's authority

7.4.2. Resource availability

7.4.3. Who manages project budget

7.4.4. PM's role

7.4.5. PM Administrative Staff

7.5. * Composite organization

7.5.1. Involves all structures at diff. levels

7.6. Include

7.6.1. Strategic

7.6.2. Middle Mngmnt

7.6.3. Operational levels

8. Organizational Process Assets

8.1. Plans, processes, policies, procedures & knowledge bases

8.2. Lessons learnt

8.3. Historical info

8.4. Inputs to planning

8.5. 2 categories

8.5.1. Processes & Procedures

8.5.1.1. For conducting project work

8.5.1.2. Include:

8.5.1.2.1. Initiating & Planning

8.5.1.2.2. Executing, Monitoring & Controlling

8.5.1.2.3. Closing

8.5.2. Corporate knowledge base

8.5.2.1. For storing & retrieving info

8.5.2.2. Include:

8.5.2.2.1. Baselines, standards, labor hours, costs, budgets, databases, files from previous projects

9. Environmental Factors

9.1. Conditions not under team's control that influence the project

9.2. Inputs to planning processes

9.3. e.g. Organizational culture, governance, geog. distrib., infrastructure, risk tolerance, PM info syst.

10. Project team

10.1. PM

10.2. PM staff

10.2.1. Scheduling, budgeting

10.3. Project staff

10.3.1. Create deliverables

10.4. Supporting experts

10.4.1. Activities required to develop PM plan

10.4.2. Financial, logistics, legal, engineering, testing, TQM

10.5. User / Customer rep's

10.5.1. Accept product / deliverables

10.5.2. Sellers, business (partner) members

10.6. Basic Project team compositions

10.6.1. Dedicated

10.6.1.1. Full-time members

10.6.1.2. Report to PM

10.6.1.3. Clear authority

10.6.2. Part-time

10.6.2.1. Functional mngrs keep control