Difference between revisions of "Project Management"

From Glitchdata
Jump to navigation Jump to search
(Assessment)
 
(15 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
</div>
 
</div>
  
[[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.
+
[[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 timeframe.
  
 
Always consider a [[Feasibility Study Project]] for projects with high risks. Here are some [[Project Management Comparisons]] especially for [[Software Development]].
 
Always consider a [[Feasibility Study Project]] for projects with high risks. Here are some [[Project Management Comparisons]] especially for [[Software Development]].
  
 +
* [[Project Governance]]
 +
* [[Project Management Maturity]]
 +
* [[Project Management Measurements]]
 +
* [[Project Management Analytics]]
 
* [[Project Management Technology]]
 
* [[Project Management Technology]]
 +
* [[Project Management Methodologies]]
 +
* [[Project Management Documentation]]
 +
* [[Project Management Products]]
 +
* [[Project Management Industries]]
  
 +
==Related==
 +
* [[Programme Management]]
  
==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 Methodologies==
 
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)
 
* [[ITIL]] Serivce Management
 
* [[Waterfall]]
 
 
==Assessment==
 
* [[P3M3]] - assesses project execution capability
 
* [[CMMI]] - assessing computing maturity
 
 
==Documentation==
 
* [[Project Documentation]]
 
 
 
 
==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
 
 
==Project Analytics==
 
* Project Diagrams
 
* [[Gantt Charts]]
 
* [[Network Charts]]
 
* [[Continuous Integration]]
 
* [[Code Standards]]
 
* [[Burndown Charts]]
 
* [[Burnup Charts]]
 
  
  

Latest revision as of 21:24, 19 December 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 timeframe.

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

Related