Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Base Model

  • Consider five size categories for all IT projects: Extra Small, Small, Medium, Large, and Extra Large. (ed. This is one or two more categories than prior art I have discovered so far – sml)
  • "Size" means the complexity and risk as impact on the end-user community.
  • The Size Category determines the release processes that must be followed. That is the sole purpose of this tool.
  • Determine sizing score by considering a concrete set sizing criteria, or decompositions. (ed. Decomposition of Risk, PMBoK – sml)
  • Still figuring out if these should be summed, averaged, or some other math.

Phases

  • If you can break a project down into discrete phases of lesser impact, you can reduce the amount of required process and complexity.
  • A "phase" is only a phase if it can result, on its own, in a discrete improvement to the product or service.
  • You can reduce scope by eliminating non-dependent phases.

Decompositions

Human Resources

ITIL Outline discovered by Pat on Wikipedia:

...