HOPEX Planning : HOPEX Planning : Describing a Master Plan
   
Describing a Master Plan
 
Master Plan Example
Defining Object Life
Viewing Application Life (Gantt Chart)
Specifying Object Life
Defining Life Cycle of an Object Type
Declaring a New Master Plan
Creating a Master Plan
Viewing and Updating Master Plan Content
Master Plan Objectives and Requirements
Master Plan Status
Using the Gantt Chart of a Master Plan
Adding Objects to a Master Plan
Indicating object life cycle status
Using Gantt Charts
Defining Milestones
Using Timelines
In the context of information system planning, a master plan defines long term evolutions of the system that will best respond to business demands. Having created a portfolio with initiatives and timespots, you can study implementation planning of your different projects by creating master plans from your portfolio or from an initiative group.
*A master plan is a low detail level definition of a long-term project. A master plan coherently groups milestones and planned elements with time periods defined by milestones.
We expect a master plan not only to show planned elements at different successive levels, but also to provide information on functional suitability of evolutions related to business function expectations, and the impact on hardware of implementation of this master plan.
This complementary information provides stakeholders (functional evolution requester business function managers, IS managers, technical architects) with decision-making criteria enabling selection, rejection, postponement, etc. of particular master plans.
Master plan description corresponds to a study phase, actual implementation of the master plan taking place at a later stage.
This presentation relates to improvement of an auto repair service in a car hire company.