There is no piloting of the tool, no requirements
study to see which tools out there fit the organization, and no training is given.
This introduction of the new tool causes chaos. A Level 5 organization will follow
the steps above, and should the pilot prove effective, will probably deploy the tool
one or a few projects at a time, not en masse into the entire organization. A go/no
go decision will be made at each step.
Don??™t wait until Level 5 to introduce these concepts into your organization. The
difference in introducing this approach at Level 1 or 2 versus Level 5 is that here at
n n n n n n n
Understanding Maturity Level 5: Optimizing n 125
Level 5 you absolutely know your organization??™s processes and can be more proactive
about predicting the level of uncertainty that the tool (in the example used)
will create. You can plan its introduction better and pinpoint areas that will need
more attention, such as training and perhaps contracts.
Things that most organizations tend to forget about this process area:
You must pilot your improvement! Only piloting will be able to accurately
predict whether this improvement has a chance of being accepted and working
in your organization.
Pages:
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308