Project Management

From Glitchdata
Revision as of 23:06, 28 July 2013 by Admin (talk | contribs)
Jump to navigation Jump to search
  • Project Management

Projects are the means by which an organisation brings about change. Projects are temporary with start and end dates. Most projects are unique. Usually with fixed budgets with a measure of tolerance. Change via projects need to be controlled/managed. Programmes consist of many projects typically over multi-year timeframes.

Always consider a Feasibility Study Project for projects with high risks. Here are some Project Management Comparisons

What is Project success / failure?

  • Lack of a valid business case (Objective)
  • Insufficient definition of requirements
  • Poor communication
  • Inadequate acceptance of responsibilities
  • Poor estimation of costs and schedule (Budget)
  • Inadequate planning
  • Lack of control over progress
  • Lack of quality control

Project Performance Measures

  • Scope
  • Cost
  • Time
  • Benefits
  • Risk
  • Quality
  • Business Expectations
  • Supplier Expectations
  • User Expectations
  • Team Expectations

Project Methodology Matrix

There are a number of project management methodologies. Project size, project nature, stakeholders, budgets, risk profiles, project interfaces will determine the type of project methodology to use. Some Project methods are:

  • PRINCE2 is strong on governance. Generally more strategic. Not used for Product Management. Good baseline product management.
  • PMBOK says nothing about governance. Focuses on assets.
  • MSP (Managing Successful Programs)


  • P3M3 - assesses project execution capability
  • CMMI - assessing computing maturity


Rules of Thumbs

  • A Project Manager typically can manage up to 6-8 team members/team managers.
    • Communication overheads overload when > 8 people
  • Verify and Validate is important

Project Analytics

Project Tools