<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=150057&amp;fmt=gif">

Creating a Project Scheduling Master Plan in Safran Project

June 14, 2016 |   | 
1 minutes read
Safran Software Solutions

Safran Software Solutions

By adhering to the project master plan, including all milestones and deliverables, the Project Master Schedule ensures successful project scheduling and that the project is completed on time.

To be effective, the Project Master Schedule should derive its information from all the detailed work schedules, and the health of the Master Project Schedule depends heavily on the quality and accuracy of the underlying component projects.

On many projects, the Master Project Schedule tends to be separate – to stand apart from the details of the component project, not reflecting the true picture of the project. Creating the Project Master Schedule is a bottom-up process that summarizes each detailed work schedule. On large undertakings like mega projects, the amount of data and information can be enormous. Unless data is organized, structured and presented at the appropriate level and in a convenient form, it is still only data. On mega projects with demanding timelines, accurate information is even more critical to the success of the project and the business.

Discover the benefits of Safran Project's unlimited scheduling features and  begin managing your projects today. Click here to start your 30-day trial. 

Bringing It Together

The one-page Project Master Schedule pulls together each underlying schedule and provides executives, leaders and stakeholders with the information required to make good decisions going forward.

To summarize the component schedules into a single page presentation of the Master Project Schedule, planners and project managers must take steps to ensure accuracy and unified aggregation across all projects.

  • All scope of work must be included
  • All projects and sub-projects must adhere to the project break down structure
  • Apply robust coding structures
  • Summary presentation and aggregation must be consistent with the WBS and aggregated from the lower level activities
  • The underlying project schedules must be updated on a regular basis to reflect the latest information available


The one-page view should also follow several guidelines:

  • The timescale across the top of the page must cover the full remaining scope and time to meet the project’s business goals
  • Aggregation of all scope consistent with the project WBS
  • Summarized levels according to project break down
  • Standardization of symbols so that management can quickly absorb key points
  • Status and front-line to show progress
  • The view should include key milestones

Meeting these criteria, you can utilize Safran Project in its optimum capacity, making it easy for your team to create transparent communication and engage all team members in an effort to meet the project goals.