You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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

Take the quality that invokes the highest score.

Score

Man Years

Project Members

Skills Gap/Consulting

1

<= 0.25

1

None

2

0.25 - 0.5

2

< 10% Consulting or Attrition Risk*

3

0.5 - 1

3 - 5

10-25% Consulting or Attrition Risk

4

1-2

6-10

25-75% Consulting or Attrition Risk

5

> 2

> 10

Approaching 100% Outsourced

*Attrition Risk is risk of individual flight, pending budget reduction/downsize, or single points of failure. 

Release Complexity

A release can contain more than one of these. Consider only parts of the service subject to change. Take the quality that grants the highest score.

Score

Software Application

Data

Integration

1

minor patch or security release, no end-user function affected

single schema

self-contained, single end-user transaction

2

major patch, "dot release" that effects end-user behavior

single database, multiple schemas

system of record, affects data feeds to warehouse

3

full application upgrade, new user functionality

external link or feed relationship to other system of record

service allows for real-time update of share enterprise data

4

operating-system upgrade as distributed release or affecting many underlying services

multiple external links or feed relationships

real time integration service, loss of service ends business productivity

5

packaged release of operating system, multicomponent or multi-transactional system

multiple production database servers changed

real-time integration service, requires client applications to refactor

End Notes

(ed. to become properly formatted end notes later. sml)

  • No labels