New page

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 71: Line 71:
  
  
|style=" width: 20%; background-color:white; vertical-align:top; text-align:left;border-right:solid 2px #474099; border-bottom:solid 2px #474099; width: 20%; height: 200px;" |'''2. Designing teams:'''
+
|style=" width: 20%; background-color:white; vertical-align:top; text-align:left;border-right:solid 2px #474099; border-bottom:solid 2px #474099; width: 20%; height: 200px;" |'''2. Teaming:'''
 
* '''Group vs teams'''
 
* '''Group vs teams'''
 
*[[ High performing teams]]
 
*[[ High performing teams]]

Revision as of 10:21, 3 June 2022

As a part of the ongoing development of our basic course on project management I am looking for wiki articles on specific tools and concepts within each of the four perspectives: Purpose, People, Complexity, and uncertainty. Some of the topics are already covered in the ConceptBox but not all live up to our expected standards as discussed in class in terms of structure, content, references and use of “own” figures (i.e. no unauthorized copy & pasting from internet sources).

In general, we strongly recommend focussing your Wiki-article on a specific tool. So instead of, say, trying to write about "risk management", write about "Monte Carlo Simulations for Cost Estimation" (risks in project -> risk management -> risk assessment -> quantitative methods -> Monte Carlo simulation -> Monte Carlo for Cost Estimation). At that level of detail, it will be much, much easier for you to write actionable advice with good examples.

If you cannot find something that interests you on the following list, we suggest to review the table of contents of the project, program and portfolio management standards that we share as part of the course literature. You can also dive into the various process frameworks introduced in the standards. Again, our recommendation is to pick a particular method, and not try and write about "project controls" in general.

Purpose
1. Defining scope: 2. Engaging stakeholders:
  • Identification
  • Assessment of stakeholders (analysis)
  • Managing stakeholders
3. Realizing impact:
  • Outputs, outcomes and benefits
  • Benefit realization management
  • Impact (sustainability)
4. Understanding the context:
  • Identification
  • Temporal context of projects
  • Organizational context
  • Project based organisations
  • Matrix organisations
  • Project organization
5. Investing in projects:
  • Stage gate model
  • Waterfall model
  • Agile (Adaptive) model
  • Scrum
  • Concurrent models
  • Over the wall (Chinese whispers)
6. Investing in projects:
  • Business case([3])
  • Net Present Value (NPV) - Discounted cash flow
  • Internal Rate of Return (IRR)
7. Assessing project success: 8. Connecting the dots:
  • (sustainable) project management
People
1. Introduction:


2. Teaming:


4. Communicating: 5. Mediating:


6.Listening: 7. Motivating:


8. Leading: 9. Self-management: 10. Connecting the dots:
  • Rework by google “Psychological Safety”
Complexity
1. Scoping: What to do?:
  • Pooled, Sequential & Reciprocal dependence
  • Work break down structure (WBS)
2.Estimating: ? 3. Scheduling: When to do it?:


4. Resourcing: Who does what?:
5. Costing: How much?:
  • Cost build up
  • Cost planning
  • Cash flow
6. Improving: Can we do it better?:


7. Contracting: Make or Buy?: 8. Connecting the dots:
  • When – the scientific secrets of perfect timing
Uncertainty
1. Introduction:
  • The Johari window / Rumfelds
  • Types of uncertainty: Epistemic/Aleatory([43]])
  • Levels of uncertainty (i.e. risk, uncertainty, ignorance)
2. Anticipating: ? 3. Monitoring:
  • Conformance/performance
  • Milestone trend analysis
  • Risk Burn down charts
  • Earned value([55], [56], [57])
  • Project reporting
  • Project warrooms
  • ' Project dashboard


4. Adapting:
5. Learning: 6. Deciding:


7. Contracting: Interpreting: 8. Connecting the dots:
  • Resilient projects
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox