Difference between revisions of "Project Management"

From Glitchdata
Jump to navigation Jump to search
 
(21 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]]
+
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?==
+
* [[Project Governance]]
* Lack of a valid business case (Objective)
+
* [[Project Management Maturity]]
* Insufficient definition of requirements
+
* [[Project Management Measurements]]
* Poor communication
+
* [[Project Management Analytics]]
* Inadequate acceptance of responsibilities
+
* [[Project Management Technology]]
* Poor estimation of costs and schedule (Budget)
+
* [[Project Management Methodologies]]
* Inadequate planning
+
* [[Project Management Documentation]]
* Lack of control over progress
+
* [[Project Management Products]]
* Lack of quality control
+
* [[Project Management Industries]]
  
 +
==Related==
 +
* [[Programme Management]]
  
==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
 
 
==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]]
 
 
==Project Tools==
 
* [[Primavera]]
 
* [[Jira]]
 
* [[MS Project]]
 
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]
 
[[Category:Project Management]]
 
[[Category:Project Management]]

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