Search Posts

Category: Systems Analysis and Engineering

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 […]

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. […]

Payback Period

Here’s a nice 3 minute explanation of “payback period”. It includes some context and a useful worked example. Organizations typically have more ideas about projects they might like to do than resources to do them all. So, to decide which one(s) to actually initiate, they typically compare candidate projects in terms of business case and […]

Next Page »