RUN-TIME DISCIPLINE-LEVEL ITERATION. Service life cycle run-time discipline-level iterations
are conducted in the same manner. Typically, the choice is made to iterate on one individual
run-time discipline at a time. However, different teams can be employed to simultaneously iterate
on multiple discipline activities. Moreover, one option is to apply multiple iterations on large
run-time discipline tasks, such as deployment, if a single iteration does not meet the required
goals. Exhibit 3.14 illustrates run-time discipline-level iteration activities, as well.
EVENT-LEVEL ITERATION. In Chapter 2 (in the section on Service Life Cycle Events), service
life cycle events were classified as staged, unpredictable, random, or conditional. Iterating on
random, unpredictable, or conditional events is an unattainable task, inasmuch as they are not
planned or predicted events. They were included in the life cycle, however, to strengthen a
proactive strategy and to provide realistic real-life scenarios. Staged events are typically good
candidates for service life cycle iterations. If the organization supports systems development life
cycle stages such as design, build, or deployment stages, stage-level iterations can be valuable.
Yet, once a stage-level iteration is applied, it becomes clear that this is not an effortless, and at
times a complex task. A stage may span multiple disciplines, include more than a single iteration
level, and even overlap the design-time and run-time seasons.
Pages:
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134