1 / 15

Cross-Project Links Report Madison MPUG Chapter Meeting April 13, 2011

Cross-Project Links Report Madison MPUG Chapter Meeting April 13, 2011. Background. Project Sponsors want a clear high-level view of dependencies between projects Communicate early on how schedule changes within one project impact dependent projects. Current Process.

ealexander
Download Presentation

Cross-Project Links Report Madison MPUG Chapter Meeting April 13, 2011

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Cross-Project Links Report Madison MPUG Chapter MeetingApril 13, 2011

  2. Background • Project Sponsors want a clear high-level view of dependencies between projects • Communicate early on how schedule changes within one project impact dependent projects

  3. Current Process • Report is updated and published monthly • As new cross-project dependencies are identified, these projects are being added to the report

  4. Milestones Professional • Software recommended by a co-member of the Madison MPUG (Microsoft Project Users Group) Chapter • Produced by KIDASA Software, Austin, TX • Contains numerous templates that can be used to create custom reports with MS Project data • Provides more flexibility than Visio for this type of reporting

  5. Sample Report

  6. MS Project Server • Some setup needed in project server – • External predecessor logic: AMI-RCDM\28 • Example: AMI-MDMS schedule: • External predecessor is Task ID # 28 in the AMI-RCDM schedule • In the MDMS schedule, enter “AMI-RCDM\28” in Predecessor ID field to set up the link

  7. MS Project Server • AE uses the Text 30 field in MS Project • Populate Portfolio ID with PM initials + number scheme • Must be unique across all projects on server

  8. MS Project Server • Another option is to create a formula to populate the Portfolio ID field – ensures ID is unique:

  9. MS Project Server When viewing the schedule in project server, the predecessor task from the external project appears in gray (disabled) above the dependent task Note: We are currently viewing the AMI-MDM schedule

  10. MS Project Server Vice-versa when viewing the schedule with the predecessor milestone (successor task in external project appears in gray) Note: We are currently viewing the DMS Upgrade schedule We’ve found this functionality to be useful – makes it clear to the PM that there is an external project dependency, and which task is impacted.

  11. Milestones Professional Can set up smart symbol tags to track project milestones and timelines

  12. Milestones Professional • Refresh report with updated project schedule with the push of a button – automatically updates timeline/milestones

  13. Milestones Professional

  14. Milestones Professional - Tips • Timing: Consider how you will sync timing of report creation to when PMs update schedules (might require expectation setting with report recipients) • User Interface: This is not a Microsoft product – different user interface – there is a bit of a learning curve • Refresh Process: When refreshing, first open the project schedule in MS Project before selecting “refresh” in Milestone Professional – speeds up refresh process

  15. Questions:

More Related