{"id":35961,"date":"2016-08-22t10:21:12","date_gmt":"2016-08-22t14:21:12","guid":{"rendered":"\/\/www.deco-dalles.com\/?p=35961"},"modified":"2019-10-18t11:14:58","modified_gmt":"2019-10-18t15:14:58","slug":"ghost-schedules","status":"publish","type":"post","link":"\/\/www.deco-dalles.com\/ghost-schedules\/","title":{"rendered":"ghost schedules: an overview for project controllers"},"content":{"rendered":"
any\u00a0project controls professional knows that during the course of a project multiple versions of a\u00a0project schedule will be created. schedules are often created at different levels.\u00a0it usually takes a few iterations to get to an agree-upon baseline. then there are progress schedules, scenario schedules<\/a>, mitigation schedules, and perhaps even a recovery\u00a0schedule. but what about ghost schedules? there might even be a ghost schedule.<\/p>\n ghost schedules are essentially versions of a schedule that are not shared with the entire team. you could say they are kept in secret.<\/p>\n in a 2015 report by navigant consulting<\/a>, the authors reveal that\u00a0ghost schedules are most often produced in order to view the timeline of a project in terms of an earlier\u00a0target finish date. then the ghost schedule can be used to influence the project participants to back the new timeline or to influence other key project decisions.\u00a0it can often be the case that a scenario schedule, a schedule built to explore a hypothesis or to demonstrate other possible timelines, becomes a ghost\u00a0schedule when it continues to be maintained and progressed concurrently with the progress schedule.<\/p>\n you might have heard ghost schedules by some of their\u00a0other names: concurrent schedule, shadow schedule or alternate schedule.<\/p>\n since ghost\u00a0schedules are used in the background, they can be controversial. a ghost schedule is clearly not the contract schedule. it can be maintained by the owner, or by the contractor or even by a subcontractor. although a ghost schedule can used for analysis and decision-making, it’s not a document that is shared with the entire project team, making it’s use a bit of a slippery slope.\u00a0however, it seems generally accepted that ghost schedules\u00a0exist\u00a0on\u00a0a large majority of projects.<\/p>\n referring back to navigant’s report, there are many situations that lead to the spawning of a ghost schedule. here’s a synopsis of some of the more common reasons broken down by the user of the ghost schedule. these are high-level summaries and for more on each situation, i would refer you back to navigant’s report<\/a> which has more detail.<\/p>\n <edit sept 2, 16> maintaining both a ghost schedule\u00a0and the original schedule\u00a0has some major implications. first, it’s not easy. just maintaining the current schedule is usually a significant effort on its own, depending on the size of the project. so maintaining a 2nd copy is going to be a challenge, one that may lead to lots of frustration and extra effort, but a what cost? there is strong likelihood that the two schedules will eventually deviate to a significant degree, rendering the ghost schedule unusable.<\/p>\n then there’s the confusion factor. project controllers are already awash in data and scenario projects, and adding more may not lead to the clarity that decision-makers expect. personally, i’m not a fan of maintaining a ghost schedule.<\/p>\n on the other hand, we know that ghost schedules are out there, and that there are many situations in which an alternate schedule\u00a0is created and maintained independently during a project. a schedule is really a collection of data, or a dataset\u00a0in it terms.\u00a0in today’s big data world<\/a>, using a\u00a0dataset to evaluate or forecast scenarios or other outcomes empowers the user. it becomes a tool for decision-making. it’s easy to copy data and we do it all the time. but what we have to keep in mind is that the originating dataset is bound by a legal contract and an understanding by the team.<\/p>\n if used at all, ghost schedules\u00a0should be used as a tool to help facilitate a mutually beneficial outcome for the project, not as a tool that promotes secrecy and obstructs open communication between owners, contractors, subcontractors and other stakeholders.<\/p>\n what are your thoughts on the use of ghost schedules?\u00a0<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":" any\u00a0project controls professional knows that during the course of a project multiple versions of a\u00a0project schedule will be created. schedules…<\/p>\n","protected":false},"author":5,"featured_media":35964,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[217,193],"tags":[],"content-topics":[],"class_list":["post-35961","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-construction","category-project-controls-tips-tutorials"],"acf":[],"yoast_head":"\nwhat is a ghost schedule?<\/h2>\n
what are some common situations that lead to the creation of a ghost schedule?<\/h3>\n
contractor ghost schedules<\/h3>\n
\n
owner ghost schedules<\/h3>\n
\n
what are the pros and cons of ghost schedules?<\/h3>\n