[44] in I/T Delivery
Re: Delivery Process Map
daemon@ATHENA.MIT.EDU (Tim McGovern)
Tue Apr 22 10:30:34 1997
Date: Tue, 22 Apr 1997 10:30:17 -0400
To: rferrara@MIT.EDU (Robert V. Ferrara)
From: tjm@MIT.EDU (Tim McGovern)
Cc: ganderso@MIT.EDU, delivery@MIT.EDU
At 4:52 PM 4/18/1997, Robert V. Ferrara wrote:
>Please suggest any language changes. Also, I'll add an explicit build/buy
>decision in DESIGN SYSTEM.
I was not present for the Friday discussion, so I offer this in the
interest of thinking about the full set of I/T processes before we
add this to the Delivery process map.
When discovery work precedes any actual delivery work, the buy vs. build
case should already be made--delivery may need to re-affirm it. There is a
discovery subprocess which examines delivery alternatives, and recommends
release strategies, and future delivery activity. When there is no
discovery work done, and we just start with delivery, I suppose you WOULD
need to have such a work element.
Tim
