APM - Module 1

?
View mindmap
  • Project Management - Project Context
    • What is a project?
      • A unique, transient endeavour undertaken to achieve planned objectives
    • Project or BAU?
      • Projects
        • Purpose:  Achieve objectives then terminates
        • Timescale: Limited, has defined start-end dates
        • Outcome: Unique product or service
        • People: Temporary teams, formed across organisational boundaries to meet project needs
        • Management: Dedicated Manager appointed for project duration
      • BAU
        • Purpose: Sustain organisation to meet business goals
        • Timescale: Ongoing
        • Outcome: Repetitive, non-unique results
        • People: Teams within organisation structure with aligned functionality
        • Management: Long term formal management
    • Organisation Structure
      • Permenant
      • Temporary
      • Matrix
    • Roles of the Project Parties
      • Project Sponsor
        • A delegated member of the steering group
        • initiating the project and appointing a Project Manager
        • Developing and maintaining ownership of the business case
        • Keeping SMT informed of the project progress
        • determining the relative priority of time, cost and quality
      • Project Manager
        • Delivering the project to time, cost and quality priorities
        • Managing sponsor and user expectations
        • monitoring and controlling the project progress
        • building, leading and motivating the project team
        • Keeping the Sponsor and SMT informed of progress/ problems / issues
      • Users
        • identifying project requirments, ensuring separation between 'musts' and 'wants
        • accepting and operating deliverables
        • providing practive assistance and guidance through users experience
        • informing PM of operation changes
        • Participating as member of team
      • Project Steering Group
        • Responsible for project feasibility, business case and achievement of outcomes
        • ensure project scope meets aligned requirements
        • usually made up of senior and authoratitve stakeholders
        • ensure effort and expenditure are appropriate to stakeholder expectations
        • ensure strategies to address potential threats have been reviewed and approved
      • Team
        • Primary role to support the PM to help project meet the objectives
        • managing communication with stakeholders
        • supporting the PM in solving project-wide problems, and identifying them
        • reporting progress of their assigned tasks
        • acting as a risk owner in their area of expertise
    • Why is Project Management Important
      • Control
      • Clarity
      • Scalability
      • Risk Mitigation
    • Why do Projects fail?
      • Poor Project Management
      • Unrealistic Expectations
      • Business Case not Sufficients
      • Project Team Lack Skills
      • Resistance by Employees
      • Inadequate sponsorship
      • Scope Uncertainty
    • Project Methodologies
      • Linear / Waterfall
        • Sequential series of steps in which each phase cannot begin until the previous is complete
        • Phases usually include: Concept, Definition, Deployment and Transition
        • Cons
          • Resistant to change and inflexible to corrections and rework
          • Diving knowledge into distinct phases can create barriers
          • When issues arise, those carrying out work tend to blame those in the previous phase
        • Pros
      • Iterative / Agile
        • Repetition of one or more phases before proceeding to the next in order to review and improve objectives
        • 6 phases include: Requirementsdesign, development, testing, deployment, review
        • Pros
          • Flexibility can be higher than traditional methods Changes (e.g. in prioritisation) can be introduced at almost any stage.
          • Agile encourages or requires frequent comms. gives us continual opportunities to learn via this feedback.
        • Cons
          • There can be less of a blueprint of what the final deliverable will be. This can make it harder to gain commitment to the project by stakeholders at the early stage.
          • It is less predictable what will be delivered at the end.
          • Agile requires high levels of collaboration and very regular comms which is not always feasible
    • Project Environment
      • SWOT
        • Strengths, Weaknesses, Opportunities, Threats
        • A Method to review the comparative analysis to test the options being considered for a project

Comments

No comments have yet been made

Similar Other resources:

See all Other resources »See all Project Management resources »