Difference between revisions of "Project Management"

From Glitchdata
Jump to navigation Jump to search
(Project Tools)
 
(27 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
<div style="float:right; width:200px; border:solid 1px #cc0000">
 
<div style="float:right; width:200px; border:solid 1px #cc0000">
<font style="color:#cc0000"><center>ACTIVE DOCUMENTATION</center></font>
+
<font style="color:#cc0000"><center>ACTIVE METHODOLOGIES</center></font>
 
* Project Management
 
* Project Management
 
</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 over a period of time.
+
[[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.
+
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 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)
 
 
 
{|class="wikitable sortable" width=100%
 
|+ Project Methodology Suitability
 
!#!!Project Methodology !!Schedule !!Quality !!Time !!Cost !!Phases !!Project Size !!Comments
 
 
|-
 
||1
 
||[[PRINCE2]]
 
|style="background: white;"|Y
 
||Y
 
|style="background: #66EE44;"|Y
 
||Y
 
||Y
 
||M, L
 
||1,2,3,4
 
 
 
|-
 
||2
 
||[[PMBOK]]
 
|style="background: white;"|Y
 
||Y
 
|style="background: #66EE44;"|Y
 
||Y
 
||Y
 
||M, L
 
||1,2,3,4
 
 
|-
 
||3
 
||[[SDLC]]
 
|style="background: white;"|Y
 
||Y
 
|style="background: #66EE44;"|Y
 
||Y
 
||Y
 
||M, L
 
||1,2,3,4
 
 
|-
 
||4
 
||[[Waterfall]]
 
|style="background: white;"|Y
 
||Y
 
|style="background: #66EE44;"|Y
 
||Y
 
||Y
 
||M, L
 
||1,2,3,4
 
 
|-
 
||5
 
||
 
[[Agile]]
 
* [[Extreme Project Management]] - following on the tail of Extreme Programming
 
* [[Scrum]]
 
* [[Rapid Application Development]]
 
* [[Lean Development]]
 
* [[Kanban]]
 
 
|style="background: white;"|Y
 
||N
 
|style="background: #66EE44;"|Y
 
||N
 
||N
 
||M, L
 
||1,2,3,4
 
 
|-
 
||6
 
||[[RUP]]
 
|style="background: white;"|Y
 
||Y
 
|style="background: #66EE44;"|Y
 
||Y
 
||Y
 
||M, L
 
||1,2,3,4
 
 
|-
 
||7
 
||[[ITIL]] - Service Management
 
|style="background: white;"|Y
 
||Y
 
|style="background: #66EE44;"|Y
 
||Y
 
||Y
 
||M, L
 
||1,2,3,4
 
 
 
|-
 
||8
 
||[[SixSigma]]
 
|style="background: white;"|Y
 
||Y
 
|style="background: #66EE44;"|Y
 
||Y
 
||Y
 
||M, L
 
||1,2,3,4
 
 
 
|-
 
||9
 
||[[Lean]]
 
|style="background: white;"|Y
 
||Y
 
|style="background: #66EE44;"|Y
 
||Y
 
||Y
 
||M, L
 
||1,2,3,4
 
 
 
 
|-class="sortbottom"
 
|}
 
 
* Small - < 12months
 
* Medium - > 12months >1M
 
* Large - > 12months
 
 
 
'''PMBOK - pros and cons'''
 
PMBOK is short for Project Management Body of Knowledge. Users of this system find that it has more substantial frameworks for contract management, scope management and other aspects which are arguably less robust in PRINCE2. However, many users of PMBOK find that they are not entirely happy with the way this system limits decision making solely to project managers, making it difficult for handing over aspects of the management to other parties and senior managers. With PMBOK, the project manager can seemingly become the primary decision maker, planner, problem solver, human resource manager and so on.
 
 
'''PRINCE2 - pros and cons'''
 
PRINCE2 stands for Projects in a Controlled Environment and this is a project management program that shares more of the functional and financial authority with senior management, not just the project manager. This program has a focus on aiding the project manager to oversee projects on behalf of an organisation's senior management. On the pros side, PRINCE2 provides a single standard approach to the management projects, which is why many government and global organisations prefer this option. It is also favoured because of its ease of use, which makes is easy to learn, even for those with limited experience. On the downside, there are users who feel that PRINCE2 misses the importance of “soft skills” that should be a focus for a project manager.
 
 
'''Agile - pros and cons'''
 
Agile is a more distinct program from PMBOK and PRINCE2. The Agile methodology is more flexible, making it better able to produce deliverables without the need for substantial changes and reworking. Tasks can be broken down into smaller stages and this allows for substantial risk reduction through earlier assessment, testing and analysis. The main drawback of Agile is that if it is not fully grasped, the methodology could lead to unattainable expectations.
 
 
==Assessment==
 
* P3M3 - assesses project execution capability
 
* CMMI - assessing computing maturity
 
 
==Documentation==
 
* [[Project 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 Analytics==
 
* Project Diagrams
 
* [[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