Category: Plan-driven
High Level Models of Project Deliverables
Examples are the context diagram and use case diagrams. Such models are very useful strategically. They complement product visions, stories, or value propositions, customer segmentations, customer personae, etc. Also, they can be progressively elaborated into more detailed structural and/or dynamic models. Here is a fine video – 8 minutes or so – on four such […]
Context Diagrams
Context diagrams represent a project’s product boundaries or “scope”. They model the product at a high level, in its “done” context. They do this by representing only the entities that interact with the product in that context. Thus, they do not represent the parts of the product or its behavior over time. As high level […]
Power Interest Grid for Stakeholder Analysis
Good 5′ explanation and slidedeck relating to the job of understanding stakeholders for project purposes. Very important at the front end of most any project, but particularly those developing their products via a plan-driven approach.
Tornado Diagram
Here is a 4′ introduction to two key constructs in quantitative risk analysis, namely sensitivity analysis and the tornado diagram. Useful slides, basic definitions.
Managing Conflict in Projects
The theme of this useful, results-oriented advice on resolving conflict in projects is “It’s your fault!” Worth a listen (although the format is talking heads and it includes a brief cm).
Tuckman Ladder
Here is a one-minute explanation of a useful, long-standing model of project team evolution – the Tuckman Ladder. This model is useful largely as a way to inform team members about “where they are” in a project, from an internal/team perspective, that is, a way that does not rely on scope, schedule, or budget frameworks. […]
Project Progress Tracking via EVM
Solid 18′ video offering a clear explanation via a worked example.
Intro to Risk Management
Very nice 11′ orientation via defintions of key constructs, a nice visual risk register, and a worked example. As the presenter indicates, the assumption here is a small to medium size project. That said, regardless of project scale, the basic constructs here are relevant and useful.
Goals vs. KPI’s
Good short explanation of the difference.