Difference between revisions of "Project Management"

From Glitchdata
Jump to navigation Jump to search
(Project Analytics)
Line 36: Line 36:
 
* Verify and Validate is important
 
* Verify and Validate is important
  
==Project Analytics==
 
* Project Diagrams
 
* [[Gantt Charts]]
 
* [[Network Charts]]
 
* [[Continuous Integration]]
 
* [[Code Standards]]
 
* [[Burndown Charts]]
 
* [[Burnup Charts]]
 
  
  

Revision as of 23:08, 23 May 2016

ACTIVE METHODOLOGIES
  • 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 especially for Software Development.

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


Assessment

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


Rules of Thumbs

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