Scenario Planning Revisited
As we discussed in the earlier chapters of this book, the turbulence of the business environment, the need for compressed development cycles, the number of alternative development scenarios, and the regaining of power by business people over their IT and other expert-based projects means that detailed project schedules should not be longer than three to six months in total.
As shown in Figure 15.7, for longer projects, you should identify scenarios and the major events in each scenario for your project over the estimated project development period. However, only the schedule to achieve the next deliverable is taken to any level of detail (i.e., an execution plan).
Figure 15.7. Scenario planning revisited
Get Radical Project Management now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
