Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
23 Cards in this Set
- Front
- Back
|
Project Def |
A project is a temporary endevour undertaken to create a unique product, service, or result. |
|
|
Project Vs Program |
Project is one task to accomplish one thing, a program is a group of projects to complete an overarching goal |
|
|
Five parts of a project |
1. Objective 2. Defined lifespan 3. Inolve lots of people and departments 4. Typically Doing what has not been done before 5. Specific time, cost, and performance goals. |
|
|
Project life cycle.(stages) |
1. Define stage 2. Planning stage 3. Executing stage 4. closing stage |
|
|
Drivers of Project managers |
1. Compression of project life cycle 2. Knowledge explosion 3. Tripple bottom line(Planet, people, profit) 4. Corperate downsizing 5. Increased customer focus |
|
|
Technical and sociocultural aspect of PM |
A PM must be both technically savy and culturaly senstive to individuals and the project. |
|
|
Why do PM's need strategy? |
Duh |
|
|
The strategic management process |
From here to there. 1. Review and define the original misson 2. Analyze and formulate strategies 3. Set objectives to achieve strategy 4. Implement stragies through projects |
|
|
Smart Goals (Criteria) |
S. Specific M. Measureable A. Assignable R. Realistic T. Time related |
|
|
Benifits of project portfolio management |
Portfolio management keeps the org on track and helps to keep politics down. Like Investment portfolio it keeps you centered on the goals |
|
|
non financial strategic criteria |
1. To capture market share 2. To snub the competitors 3. To develop and enabler product 4. To develop core products 5. To reduce dependancy on unreliable suppliers 6. To prevent government intervention |
|
|
Org culture |
Shared system of norms, beliefs, values, and assumptions. |
|
|
Cultural charicteristics |
1. Physical Characteristics 2. Read about org 3. Observe people 4. Interpret Stories |
|
|
Scope statement |
1. Project objective 2. Devliverables 3. Milestones 4. Technical Requiremets 5. Limits and exclusions 6. Reviews with customer |
|
|
Project charter(scope creep) |
Gives the PM authority to manage the project, which helps the to keep scope creep to a minimum |
|
|
Project trade-off |
Primary role of the PM is to manage trade-off |
|
|
Work break down structure |
The work break down structure is an outline of the project with different levels of detail |
|
|
Responsibility matrix |
Summarizes the tasks to be accomplished and who is responsible for them |
|
|
Micro Vs Macro Estimates |
Micro focuses on individual tasks, macro estimates based on general overview |
|
|
Methods of estimating |
Top-Down Consensus Ratio Apportion Bottom up Template Range estimates |
|
|
Types of costs |
1. Direct a. Labor b. Materials c. Equipment d. Other 2. Direct Overhead 3. General Overhead |
|
|
Apportion method |
Each task is given a portion of the total project cost so as to limit the amount spent on each task. |
|
|
Function Point method |
Time and cost estimates are made based on complexity of each task. |
