Use the experience of the drawing office people to give a duration for the complete production and approval of the drawing (always takes longer than expected)and break it into ten steps as in my example. It gives the planner at least a chance to progress the activity without waiting for the final drawing to be produced. Senior managers will then be able to see at least something is happening
How do you proceed ? Is your progress for each step based on a excel file for instance, that follows the progress of each drawing to be produced and validated ? And then, for each step, you do regularly the ratio between the total drawings & the actual nb realized ?
I use steps to progress activities to avoid cluttering up the gantt chart for example when producing drawings over a period of time. Step 1 Task started 10% Step 2,3,4,5 and 6 Production of drawing 11% - 60% Step 7 Internal check of drawing Step 8 Incorporate internal comments onto drawing Step 9 Client comments incorporated onto drawing Step 10 Approved document
I know some WPMs who used then for serial production. The main inconvenient I see in this practice is that, we cannot see the impact on schedule if one step is delayed.
Moreover, it is not easely possible to get some Output Milestones (deliveries) linked to the related activity.
By the way, the WPM who schedules this way must perfectly know the methodology of schedule update ; I often see to many neglects.
I would recommend this practice for stabilized serial production schedules only.
I have used it and I found it very helpful. You can use it as further layers of WBS but I used them more as note (or log in P3). The good thing is that you can write all the notes you want and also progress it and show its effect on parent activity if you wished. I started adding steps as the works progressed and started seeing some more steps. (And I did not want to add the activity).
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
Patricia
Use the experience of the drawing office people to give a duration for the complete production and approval of the drawing (always takes longer than expected)and break it into ten steps as in my example. It gives the planner at least a chance to progress the activity without waiting for the final drawing to be produced. Senior managers will then be able to see at least something is happening
Hello Roger,
How do you proceed ? Is your progress for each step based on a excel file for instance, that follows the progress of each drawing to be produced and validated ? And then, for each step, you do regularly the ratio between the total drawings & the actual nb realized ?
Kindest regards.
Patricia
I use steps to progress activities to avoid cluttering up the gantt chart for example when producing drawings over a period of time. Step 1 Task started 10% Step 2,3,4,5 and 6 Production of drawing 11% - 60% Step 7 Internal check of drawing Step 8 Incorporate internal comments onto drawing Step 9 Client comments incorporated onto drawing Step 10 Approved document
I use steps when i dont need to detail activities any more (gantt chart) but want to guit it an advance criteria.
I know some WPMs who used then for serial production. The main inconvenient I see in this practice is that, we cannot see the impact on schedule if one step is delayed.
Moreover, it is not easely possible to get some Output Milestones (deliveries) linked to the related activity.
By the way, the WPM who schedules this way must perfectly know the methodology of schedule update ; I often see to many neglects.
I would recommend this practice for stabilized serial production schedules only.
Steps are particularly usefull when doing large chunks of work where the tasks do not need to be done in sequence.
I use steps when i dont whant (or need) to detail more an activty with links, resources, codes etc.
Best regards.
I have used it and I found it very helpful. You can use it as further layers of WBS but I used them more as note (or log in P3). The good thing is that you can write all the notes you want and also progress it and show its effect on parent activity if you wished. I started adding steps as the works progressed and started seeing some more steps. (And I did not want to add the activity).