Extras Flashcards
Program and the project hierarchy
Projects within programme or portfolio > sub projects or sub content ads within a project > work packages within a sub project > activities within a work package
Stakeholder identification
Stakeholder identification is performing a brainstorming exercise to list all possible stakeholders
Rationalise stakeholders into groups of common interest
Clarity of scoping
Scoping must ensure that the requirements stated by the clients are Smart
Bottom up estimation
Activities > work packages > phase > project
Activity on arrow
Circle with 1 points to circle with 2
Activity on node
Arrow then box with A and time then arrow pointing away
Risk register
The risk register provides a record of identified risks related relating the project, including their status and history
Risk identification techniques
Risk identification techniques:
Review lessons
Risk checklists
Risk prompt lists
Brainstorming
Risk estimation techniques
Probability trees - a graphical rep of possible events and their associated probabilities
Expected value - quantification or risk by combining the cost of the risk impact with its associated probability giving a tangible risk value
Pareto analysis - tank or Oder risks once they have been assessed to determine the order in which they should be addressed
Probability impact grid - a grid containing ranking values that may be used to rank threats and opportunities qualitatively
Risk budget
A risk budget is a sum of money set aside to fund specific management responses to the projects threats and opportunities
Fast tracking
Project to be completed in less than 70% of the time required to do a traditional project
Stakeholder mapping
Interest low and power:
Low low monitor
Low interst high power keep satisfied
High interest low power keep informed
High high manage closely
Audience prioritisation Matrix
Importance of the issue to the audience
Influence of the audience on the issue
Anything high for both would be priority audience
Anything mid would be secondary
Anything low would be ignore
Traditional pm approach
Concentrated on thorough, upfront planning of the entire project
Requires a high degree of predictability to be effective
Agile project management
Relies on incremental iterative development cycles to complete less predictable projects
Is ideal for exploratory projects in which requirements need to be discovered and new technology tested
Focuses on active collaboration between the project team and customer representatives
Dis of agile pm
It does not satisfy topmanagement needs for budget, scope and schedule control
It’s principles of self organisation and close collaboration can be incompatible with cooperate cultures
It requires active customer involvement and cooperation