GoConqr hat ein neues Design! Sag uns, wie es dir gefällt.

Karteikarten

Ohne Titel

Cat M Englisch 18 Karten

Karten in diesem Stapel (18)

  1. 1Project ScopeScoping is the processes to ensure the project includes all the work required, and only the work required to complete the project successfully
    Project scope is the work performed to deliver a product/Service, or result with the specified features/functions
  2. 2Product ScopeThe features and functions that characterise a product, service, or result
    the term project scope is sometimes viewed as including product scope
  3. 3Scope RiskWhen the scope is:
    -not well thought out
    -not properly documented
    -Little Buy-in or understanding from stakeholders
    -Lack of tracking mechanism to monitor scope changes
  4. 4Scope CreepA process where additional work is added to the project after the scope has been established
  5. 5Project StakeholderAn individual, group or organisation that is involved in a project whose interests might be influenced as a result of a project's achievements
    -PMs have to manage all stakeholders
    -Clarify the project's scope, info needs to be collected
  6. 6Business Environment(External) Wider Environment - No influence/control
    (External) Outer Environment - No control/Can influence
    Internal Environment - Can control/influence
  7. 7Stakeholder Analysis Process1. Identify stakeholders - network, primary/secondary; internal/external
    2. Prioritise stakeholders based on power/interest map
    3. Plan type and frequency of communication - monitor, keep satisfied, manage closely, keep informed
  8. 8Organisation Breakdown StructureTypes - Functional, Matrix, pure project
    Defines communication channels, responsibilities and the level of autonomy/authority
  9. 9Work Breakdown StructureDivides deliverables into smaller, manageable components called the work package
    1.defines what needs doing
    2. how long it will take
    3. required resources
    4. cost
    5. person responsible
    6. measure of progress
  10. 10WBS Rules100% ruke
    mutually exclusive items
    outcomes not actions
    key stages can be identified using logic/network diagrams
  11. 11Project Scheduling-Scheduling is deciding the time each activity/tasks will take and the sequence in which they will be carried out
    -Useful to identify dependency/delay
    -Critical Path method - route with longest duration
    -Gantt chart - duration as bar chart
  12. 12Critical PathThe set of activities on a path (from start to finish events) that if delayed, will delay the completion date of the project
    -the longest path that gives the shortest delivery time
  13. 13Critical timetime required to complete all activities on the critical path
  14. 14Critical Path 8 Basic Rules1. Network flows left from left and right
    2. Activities cannot begin unless all preceding connected activities have been complete
    3. Arrows indice precedence/flow
    4. ID number for each activity
    5. Activity ID must be larger than any preceding activity
    6. Looping is not allowed
    7. Conditional statements are not allowed
    8. It is good practice to use a start/end nodes
  15. 15CrashingShifting of resources to reduce the slack time
  16. 16Risk Management ProcessStep 1 - Risk Identification
    Step 2- Risk Assessment
    Step 3- Risk Development
    Step 4 - Risk Response Control
  17. 17Risk Assessment-Severity of Impact
    -Likelihood of occurring
    -Controllability
  18. 18Project Monitoring

Informationen

Beschreibung
Karteikarten am Ohne Titel, erstellt von Cat M am 21/05/2019.
Erstellt von
Cat M
Aufrufe
0
Bewertung

Feedback

Worum geht es?

Wie gefällt dir das neue Design?

Dein Eindruck