Microsoft Office Forums

Go Back   Microsoft Office Forums > >

Reply
 
Thread Tools Display Modes
  #1  
Old 07-23-2015, 02:16 PM
thedanimal thedanimal is offline Schedule with many dependencies question Windows 7 64bit Schedule with many dependencies question Office 2010 64bit
Novice
Schedule with many dependencies question
 
Join Date: Jul 2015
Posts: 1
thedanimal is on a distinguished road
Default Schedule with many dependencies question


Hi all,

Here's what I'm trying to get my head wrapped around what would be a good approach. We're commercializing ~20 new products, and before they can be released to the sales team we need to be 100% complete (or pretty darn close) on ~300 prerequisite tasks. Instead of creating 20 schedules, or 20 Sub Projects in one schedule, any ideas on how this could be represented in 1 schedule? Also, these products will be phased in several at a time so it wouldn't be 6000 rows out of the gate.

Thanks for any help!
Reply With Quote
  #2  
Old 07-24-2015, 05:51 AM
JulieS JulieS is offline Schedule with many dependencies question Windows 7 64bit Schedule with many dependencies question Office 2013
Expert
 
Join Date: Dec 2011
Location: New England
Posts: 1,693
JulieS will become famous soon enough
Default

Case FOR Separate files:
  • If the projects need to be reported individually, that does argue for separate project files that can be combined as needed in a master project.
  • The advantage of separate projects is if they have differing PMs each can be updating his/her project file while another PM is updating their file.
  • If using individual projects and master - you only need to have the master file hold the "active" projects. If a project is not yet begun or has finished, the files do not need to be in the master.

Case against separate files:
  • If you are using the same resources - you need to create a resource pool to keep track of possible resource overallocations. Resource pools need to be treated carefully and all user touching the project files attached to the pool need to have a very solid understanding of how MS Project works.
  • Care needs to be taken to make sure each individual project file is never moved or copied as this creates havoc with the master. Suggest to never save the master but to re-create as needed.

Case for putting everything in one file:
  • Easy to see everything going on.
  • All updates are contained within one file.
  • Can use a spare text field for identifiers for what product is being produced.
  • No concerns about resource pools - all the tasks and all resources are contained in one project file.

Case against:
  • 6000 lines is a bit much for the PM to keep track of.
  • Need to answer the question of what will you do with projects that are complete? Do you delete their tasks to keep the project file in control?

I hope this helps.
Reply With Quote
Reply



Similar Threads
Thread Thread Starter Forum Replies Last Post
Excel Project Sheet with Dependencies OceansBlue Excel 5 02-28-2015 12:18 PM
Cross Project Dependencies OTPM Project 6 01-18-2014 07:52 AM
Question about tasks on critical path in MS Project schedule (with a twist) SomewhereinTX Project 7 01-06-2014 03:07 PM
Schedule with many dependencies question moving tasks - retaining dependencies Andy Francis Project 5 07-25-2013 10:24 AM
Filter indirect dependencies SirPercival Project 1 07-04-2012 01:03 PM

Other Forums: Access Forums

All times are GMT -7. The time now is 06:03 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Search Engine Optimisation provided by DragonByte SEO (Lite) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
MSOfficeForums.com is not affiliated with Microsoft