Difference between revisions of "Project Management"

From Glitchdata
Jump to navigation Jump to search
(Project Methodology Matrix)
(Project / Development Tools)
Line 180: Line 180:
 
* [[Continuous Integration]]
 
* [[Continuous Integration]]
 
* [[Code Standards]]
 
* [[Code Standards]]
 +
* [[Burndown Charts]]
 +
* [[Burnup Charts]]
  
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]
 
[[Category:Project Management]]
 
[[Category:Project Management]]

Revision as of 21:25, 10 April 2012

ACTIVE DOCUMENTATION
  • 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 over a period of time.

Always consider a Feasibility Study Project for projects with high risks.

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)


Project Methodology Suitability
# Project Methodology Schedule Quality Time Cost Phases Project Size Comments
1 PRINCE2 Y Y Y Y Y M, L 1,2,3,4


2 PMBOK Y Y Y Y Y M, L 1,2,3,4
3 SDLC Y Y Y Y Y M, L 1,2,3,4
4 Waterfall Y Y Y Y Y M, L 1,2,3,4
5

Agile

Y N Y N N M, L 1,2,3,4
6 RUP Y Y Y Y Y M, L 1,2,3,4
7 ITIL - Service Management Y Y Y Y Y M, L 1,2,3,4


8 SixSigma Y Y Y Y Y M, L 1,2,3,4


9 Lean Y Y Y Y Y M, L 1,2,3,4


  • Small - < 12months
  • Medium - > 12months >1M
  • Large - > 12months

Assessment

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

Documentation


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 / Development Tools