/w EPDw UKMTE4 ed 16774169 Week 3: Planning and Scheduling - Discussion Adjusting the Project Schedule (graded) A customer has asked you to crash the project and told you to crash an activity that is not on the critical path. What do you, as the project manager, suggest to your customer? Responses Response Author 297910035,29900 295711023 Starting with Crashing the Project Schedule Date/Time 0 3/11/2012 4:34:01 AM Professor Firestone Team, this discussion has two important components: crashing project schedules as well as handling customers. Often crashing is requested by the customer or project sponsor in order to meet some deadline that may or may not be known to you, the project manager. As the project manager, you should have the best knowledge of the schedule and the budget to support meeting the scope of the project. But there are consequences of crashing and you are still the one where the 'buck stops'. So, what are you going to do? 299005627 297910035 RE: Starting with Crashing the Project Schedule 295711023 Summers Love-Morrison 3/15/2012 12:37:44 PM I think that it is important to ensure that the customers are satisfied and ensure that we understand exactly what they want. ON the otehr hand, when considering a project crash we must take into consideration if we can complete the project much earlier and the cost, considering that it may take more man hours in a day in order to get the project compelted early.In order to reduce the cost and time, we need to shorten the critical path. 299005627 297910035 RE: Starting with Crashing the Project Schedule Nazish Raja 3/17/2012 7:58:24 PM Nice Post Summer. It’s important to have a service level where there is call centers, service desks and support. I also think a customer retention is also important because having utilization for a customer can definitely dedicate your service and I would also add response time to this list because customer feed back for sure helps with the service improvement because of the given comments, a lot of comments can be implemented into the changes and help create new competitive strategies and goals. 297699956,29848 297643309 RE: Starting with Crashing the 295711023 Albert Wells 3/14/2012 8:33:12 PM Project Schedule I think its important to avoid crashing the critical path. Keep in mind I have very little real world experience and would love feed back on this. So the critical path in my mind is the sacred portion of the project if we extended we extend the project or have to spend a great deal of effort and usually resource to take and keep the project on track. However, if we crash it we create "dead" space in the project because we can't push everything back. In my opinion based off of my understanding as a PM I would be willing to crash no critical task as long as the project sponsor and customer both understood and accepted the increase in budget. 298483475,29908 297699956 297643309 RE: Starting with Crashing the Project Schedule Shadina Pennybaker 3/14/2012 9:55:25 PM Albert, I as well don't have any real experience when it comes to managing projects, but to my understanding the critical path of the project is considered critical because if it changes everything else can change. If you fall behind on a task on the critical path it will have a domino affect on other task that are depending on that task to be completed before it can start. I believe if you crash the critical path it will cause other task ( that are not on the critical path) to fall behind schedule. I could be wrong, but this is my understanding. 299085796 298483475 297699956 RE: Starting with Crashing the Project Schedule Sindy Guerra 3/16/2012 3:33:09 PM Shadina, this is a great explanation of the critical path. The big word here is "dependency". You cannot start one task if you haven't completed the other task that this one depended on. An example from the project I chose for this course is I'm trying to buy a new temple. I cannot start negotiating the lease if I haven't raised enough funds. However, there are other tasks that can be done that are not on thhe critical path. These tasks are more flexible and do not have a domino effect. If one delays on the tasks that are in the critical path, then the whole project will be behind. 299085796 298483475 RE: Starting with Crashing the Project Schedule Albert Wells 3/17/2012 10:14:59 PM Thanks both for the response. I understand we have dependencies along the critical path. Does this mean if i finish a task on the critical path the project get ahead of schedule? 297661369 RE: Starting with Crashing the Project Schedule 295711023 Leigh-Ann Joseph 3/14/2012 8:58:42 PM When you consider crashing a project schedule you need to consider if it is even possible to get the project done quicker and how much it will cost. Some projects will take a certain amount of time and there is little room to condense the project. If it is possible to add more resources and get the project done quicker than the amount of money it will cost will have to be considered. This should be clearly defined and the client should receive this and approve it before any work is done. I would meet with the client and give the pros and cons of crashing the schedule and quote the extra cost that will be required to make this change. If the client agrees and has considered the pros and cons then I would move ahead with the change in the schedule. 297554735 RE: Starting with Crashing the Project Schedule 295711023 Kevin Shaw 3/14/2012 6:15:22 PM In the end I do work for the customer. I would make them fully aware of the consequences of crashing the project and the cost associated with this. The decision would be up to them. I would request that if they do wish to crash the project i would need an acknowledgement from the customer showing they approved the crash. 297114331 RE: Starting with Crashing the Project Schedule 295711023 Mercedes Santana 3/13/2012 6:51:04 PM Well depending on wha the cost is going to be after the ideas is presented then a decision can be made. There has to be an analysis of where this new item can fit into the current project plan. If it's even feasible to fit into it without going over the budget or time constraints. Unless the stakeholder really wants to include it in the project and is aware of the cost and time constraints and is willing to increase the budget and time then a decision can be made based on all the information. 296552238 RE: Starting with Crashing the Project Schedule 295711023 Brandi Williams 3/12/2012 6:28:44 PM For every action, there is a consequence. Sometimes it is good and sometimes it is bad. The question comes down to "how much is this going to cost?" As suggested in our text, as the PM, I would calculate the crashing cost and time of each activity that the client has suggested to be "crashed". Only activities on the critical path should be considered to crash when using CPM (activity-type network) as opposed to PERT. PERT is event oriented, whereas CPM is activity oriented. Depending upon the driving force of the project, I would most likely "reject" the suggestion of crashing an activity that is not on the critical path if the project is mainly activity driven, such as construction or furniture restoration. If the project is event driven and funds are being provided as-events-occur or in incremental phases such as "event planning" (wedding, graduation, etc.), then I would consider crashing an activity. 297278651 RE: Starting with Crashing the Project Schedule 295711023 Aaron Downing 3/13/2012 11:22:07 PM Is the biggest problem regarding crashing a project the aftermath of the increased costs? We recently experienced this at work, not a perfectly classical sense of a project but a project none the less; we were behind because we lost people so they crashed the project by bringing in outside resources and allowing all the overtime needed to get caught up. The aftermath was a pullback in manpower and overtime and micromanagement to keep the costs under control. 297279299 RE: Starting with Crashing 295711023 Herbert Anderson 3/13/2012 11:24:03 PM the Project Schedule First weighing all my option and communicating with the customer or sponsor, they must understand that crashing projects can become hard to do with the trying to budget with the scope and shorten the schedule process. They must also understand that certain tasks cannot be push faster with or without the resources, things must stay its course. I wouldn't recommended it but the customer has a strong reason for the sudden add or change then, I must try to meet the client needs. However, As teh PM for a project my main goals are making sure every task is at a smooth flow and if some sub task finish eary then maybe room could be made to crash a project. According to Chris Foya of http://pmstudent.com/crashing-a-project/, states "Crashing is a process of expediting project schedule by compressing the total project duration. It is helpful when managers want to avoid incoming bad weather season. However, the downside is that more resources are needed to speed-up a part of a project, even if resources may be withdrawn from one facet of the project and used to speed-up the section that is lagging behind. Moreover, that may also depend on what slack is available in a non-critical activity, thus resources can be reassigned to critical project activity. Hence, utmost care should be taken to make sure that appropriate activities are being crashed and that diverted resources are not causing needless risk and project scope integrity." 296919814 295885363 RE: Starting with Crashing the Project Schedule 295711023 Vanansio Samson 3/11/2012 3:07:34 PM The only way to reduce a project's expected duration, or the time remaining to completion, is to shorten the critical path. Shortening the time for performing tasks on non-critical paths will not have any effect on the project duration. Applying additional resources to activities that are not on the critical path may allow those activities to be completed early, and will not effect the overall project end-date. My chance to make an impact on the estimated end date relies on my ability to identify and shorten then critical path. 296919814 295885363 RE: Starting with Crashing the Project Schedule Sharon Jno-Baptiste Griffin 3/13/2012 11:00:55 AM Vanansio, I totally agree with you. Project managers should evaluate their project on a weekly basis to ensure that they remain on track. Once they realize that the project goes a bit off-tract, adding resources to critical paths, events which need to occur first to complete the whole project when the project has interdependent activities. 296017639,29628 295927007 RE: Starting with Crashing the Project Schedule 295711023 Melissa Burr 3/11/2012 4:34:13 PM It is important to be able to handle a customer and I think in this situation I would hear what the customer had to say, the reasons they needed this changed and provide my information as to why I agree or disagree and the affects it would have on the outcome. If the customer accepts that outcome then there isn't any reason to not do what they ask of the PM. 296284411,29656 296017639 295927007 RE: Starting with Crashing the Project Schedule Echo Woolf 3/11/2012 7:04:57 PM Melissa, listening to what the customer has to say is imperative. The project team is working for them. So if the customer wants to crash an activity I would first want to know the reasoning behind the decision. If it was something that wouldn’t interfere with the completion of the project, or like my classmates said, there was an alternative solution, I would make that suggestion. If the project could realistically not increase the risks of the project I would do what the customer asks, but let them know of any potential consequences that could come from the decision. Otherwise, as a PM I would revisit that activity and see if there was a cheaper way to handle it if it was a cost concern or a faster way of completing it if it was a time concern. Regardless, the customer has a right to ask for these types of changes to be made. 296565972,29662 296284411 296017639 RE: Starting with Crashing the Project Schedule 3/12/2012 8:33:29 AM Frederick Rock I agree, listening to the customer and or sponsor is important for all the reasons given. However the fine line here is the integrity of the project. Yes a meeting should be set up to discuss all the concerns and reason for the crash. But communicating the fact of life as a result of the crash is just as imperative. Discussing the cost of the crash could change a point of view or not. 296621878,29728 296565972 296284411 RE: Starting with Crashing the Project Schedule 3/12/2012 6:47:08 PM David Page While I agree with everyone so far I most agree with Fredrick. There is a fine line there because as he said the integrity of the project is at stake. Additionally, there is the reputation of the company. First what are the customer’s intentions? There should be budget in place and through crashing maybe it would save in the beginning but would have a significant impact on the project later. The PM is going to have the best overall picture with regards to the end result. If crashing some portion later causes an impact as the professor said in the initial post the “buck stops with you.” So while the customer has the right to make the request it is the PM’s job to seek alternatives or know the impacts. If the customer wants a crash and that impacts the scope and the customer is okay with the loss if there is one then I suppose everyone is right in that when it is all said and done it is going to be their product. 296621878 296565972 RE: Starting with Crashing the Project Schedule Miriam Hassan 3/12/2012 7:53:11 PM Modified:3/12/2012 7:53 PM The crashing of any part of the project does not necessarily equate to cost savings as additional resources and money are required to speed up the process. And the project manager must carefully evaluate the situation before embarking on such a task, determining whether there is slack in other areas of the project to help compensate for the crashing without affecting the cost and time restraints. The best practice to crashing is to enforce it during the early stages of the project, this provides flexibility in the event crashing may be required at a later stage of the project. 297281334 296565972 RE: Starting with Crashing the Project Schedule Aaron Downing 3/13/2012 11:30:42 PM There you have it. Is cost or schedule more important? You have to obviously balance the two and while keeping on schedule will keep the customer pleased, sometimes you have to let things slide because costs get out of control. The main thing to remember is that the longer the project lasts, the more it costs, no matter what. 297117981 296017639 RE: Starting with Crashing the Project Schedule Mercedes Santana 3/13/2012 6:56:50 PM Melissa and Echo, I agree that listening the customer is imperative since we are working for them. There may be a challenge in handling the new item they want to add to the Project. It's important to lay out the consequences of this new task in cost and time so that they can see what it will take in order to accomplish this new task along with what has been laid out. Once they see cost and time then it can be easier to make a decision whether it's feasible or not. 296509831 296065032 295927007 RE: Starting with Crashing the Project Schedule David Froning 3/11/2012 8:06:11 PM I think you are on the right track. Before I would crash a task I would make sure that I understood what the customer was trying to accomplish by doing so. It may be that I have the ability to do something different with the schedule or the resources that would allow me to make better decisions based on what the customer was trying to accomplish. 296509831 296065032 RE: Starting with Crashing the Project Schedule Sheila Williams 3/12/2012 5:22:16 PM I agree, David. Before "crashing" an activity, it is important to understand what the customer is trying to accomplish, not to mention that the customer needs to understand what will happen with "crashing." I would explain to the customer that "crashing" means to add resources to the critical path, or rather, spending more money to get something done in a shorter period of time, without necessarily getting the highest level of efficiency. I would also add that new resources won't be familiar with the tasks, therefore, they may be less productive in the long run. Furthermore, there is the possibility that as an activity is crashed a new critical path will develop, where this new path may or may not include the elements that were bypassed because they were not on the original critical path. Accordingly, "crashing" would result in increased costs (Kerzner, 2009). Source Kerzner (2009). Project Management (10th ed.). John Wiley & Sons 296015885 RE: Starting with Crashing the Project Schedule 295711023 Joseph Allen 3/11/2012 7:02:24 PM Crashing a project will require additional resources. These additional resources will require additional funds. Should it be possible to crash the project and shorten the duration of the project it is important the the project sponsor understand the consequences and the costs that may be incurred to accomplish this. The project sponsor can then be aware and make their decision on if the additional costs are justified to meet the needed deadline. The project manager should present these changes and cost estimates to the project sponsor in writing so that there is a record of acceptance. In the case where the PM is dealing with an outside customer, the changes to the project must also be presented to the customer in writing. This may take the form of a change request. The additional costs to the customer should be outlined and the estimated schedule reduction. Typically a change requiring additional costs to an outside customer are beyond the original budget. It would be important to communicate these cost additions to the customer so the costs are captured and not absorbed by the organization. Establishing a relationship with a customer early in the project is important. Honest and regular communication should be established so that when changes are requested the customer fully understands the consequences of the changes. 296327469 296088361 RE: Starting with Crashing the Project Schedule 295711023 Marquita Blair 3/11/2012 8:33:38 PM From my own personal experience if we were asked to crash a project it was for a good reason, like an inclimate weather season was fast approaching. But the problem is, more resources are needed in order to speed up that portion of the project, so resources are being pulled from one task and placed on the other, and slack becomes an issue for the non-critical activities. As the PM I would only crash a project schedule if I knew it was an appropriate activity and if the reassigned resources were not causing a needless risk to their original tasks. Crashing activities are best when performed in the beginning of a project it opens up leeway to later tasks within the project. 296327469 296088361 RE: Starting with Crashing the Project Schedule Sanah Fatima 3/12/2012 10:32:14 AM on of the common idea is to Increasing Your Resources There are a number of standard and typical approaches to attempting to crash a project schedule. One of the most commonly utilized methods involves increasing the assignment of resources on schedule activities. This essentially means decreasing the time it takes to perform individual activities by increasing the number of people working on those activities. Pros: This makes sense, at first glance. For example, if it takes Bob 4 hours to complete an activity, it would logically take Bob and Sue 2 hours to complete the same activity. Something to keep in mind in my opinion: It is really depends on the deadline essentially. If you have tight deadline it would be worth adding resources, If your dealine is not tight then adding resouces would be just more expense to the project. 296256207 RE: Starting with Crashing the Project Schedule 295711023 John Sebastien 3/12/2012 6:26:36 AM As the project manager, if it is very critical that the project’s schedule be crashed so that the customer’s/ sponsor’s deadline are met, then I would follow through with it. However, if by following the current schedule will still ensure the project’s completion date set by the customer, then I would certainly stick to the current schedule. As the project manager you are responsible for completing the project on time, while satisfying the customers’ needs. Also, as part your responsibility will be to manage the budget most effectively, so that the project is fully complete and there’s no cost overrun. Although crashing compresses the schedule to reduce execution time, it can result in an increase of risk and overall cost. Therefore, the budget must be able to support such undertakings before making such decision as the project manager. 296530391,29777 296322933 RE: Starting with Crashing the Project Schedule 295711023 Syleisha Smythe 3/12/2012 10:21:00 AM I just wanted to start the week off by sharing a DeVry Student HUB video resource pertaining to Critical Path, Slack and Lag/Lead time. This video utilizes MS Project in the explanation which is helpful for our course project this week: http://hub2.devry.edu/node/1223 296530391 296322933 RE: Starting with Crashing the Project Schedule Marquita Blair 3/12/2012 5:55:42 PM Thank you so much for posting this video! I needed a quick refresher course in Project. I have not used it since the beginning of last year. 297967527,29868 297771693 296322933 RE: Starting with Crashing the Project Schedule Kathryn Martinez 3/15/2012 1:32:40 AM Yes Syleihsa, Thank you for posting this video it was a great help to understanding the Critical Path, Slack and Lag/Lead time. I found it very helpful. 298680403 297967527 297771693 RE: Starting with Crashing the Project Schedule Syleisha Smythe 3/15/2012 3:04:16 PM You're very welcome :) Glad you both found them useful. I have not used Project in forvever either! There are also MS Project tutorials posted at the bottom of this weeks lecture page to help with a brush up before trying to complete the course project. Good Luck to you both! 298680403 297967527 RE: Starting with Crashing the Project Schedule Kathryn Martinez 3/16/2012 11:37:46 PM Thanks for letting me know Syleisha, I've gotten a bit rusty in my project management skills. I know project management but there are some things I just can't seem to wrap my mind around. 296538359,29755 296346910 RE: Starting with Crashing the Project Schedule 295711023 Syleisha Smythe 3/12/2012 11:20:57 AM I think the first steps I would take with this customer is to find out what their desired result is in crashing the project. If it is a shortened project duration then I would explain to them that crashing a project schedule is only effective when applied to tasks along the critical path of the project as shown below in MS Project: Source: http://www.rationalplan.com/terms/termsImages/CriticalPath.gif If a task is not part of the critical path, "crashing" it will have no effect on the overall project schedule. The HUB has a great video which explains how to create a Critical Path Method diagram for project planning purposes. You can view it here: http://hub2.devry.edu/node/3068 297555091,29836 296538359 296346910 RE: Starting with Crashing the Project Schedule Marquita Blair 3/12/2012 6:08:21 PM Really good post. And yes you are right "crashing" has no effect on minor tasks because they do not determine time duration. I also agree with your statement that you'd want to know what was the customer's purpose for wanting to crash the schedule. I've only seen this happen a couple of times and the reasons were so extreme my boss had not other choice but to follow through with the request. It wasn't just because the customer asked him to, it was more like project emergencies. 298366908,29838 297555091 296538359 RE: Starting with Crashing the Project Schedule Sanah Fatima 3/14/2012 6:16:05 PM You are right! this could be due the deadline. When project have intense deadline and when the focus is to get it done successfully, You would want to hire more resources. 298389536 298366908 297555091 RE: Starting with Crashing the Project Schedule 3/16/2012 10:08:08 AM Syleisha Smythe Yes, I would also agree with Sanah and Marquita that if the client is requesting to crash the project, but suggesting to crash non-critical tasks in hopes of moving the project along faster, wee would need to make the suggestion of adding more resources (and by consequence cost) to the project utilizing the appropriate change management and scope change request processes. Otherwise we would need to make suggestions of tasks along the critical path that could be crashed with the least consequences to quality. 298389536 298366908 RE: Starting with Crashing the Project Schedule 3/16/2012 11:11:29 AM Miriam Hassan And then there comes a time when the PM has to say "no" to the client due to the simple reason that the requests may jeopordize the integrity of the project and throw the budget way out of balance. As the Project Manager, you need to be tackful, investigate other non-critical areas where crashing certain tasks will not harm the project. In any case, you should schedule a project team meeting to come up with alternative solutions and meet with the owners to discuss the consequences. If all else fails and the owner is still insisting on crashing the items, the Project Manager has to use his/her better sense of judgement as to whether to walk away from the project or fulfill the owner's request - but not before putting it into writing along with the owner's signature as consent. (In other words, the PM should always cover his/her a - ! in the event of a dispute) 297557958 295808161 Adjusting the Project Schedule David Page 0 3/11/2012 12:11:44 PM Just because some portion of the project is not critical does not mean that will not have an impact on the project as a whole. As the PM you have to keep the customer happy but you also have to consider the success of the project. I would want to have a risk analysis done and work with the customer to find out what real purpose of the crash is for as well as inform the customer of the impacts to the schedule. I would also work the figures and check the schedule to ensure that the project could support the crash. There be another way and I would want to discuss all avenues that are possible to see what would be best for the project as well as the customer. 297557958 295808161 RE: Adjusting the Project Schedule Sanah Fatima 3/14/2012 6:21:35 PM I agree with your statement Dave, I would do risk analysis and as soon as WBS is created find Pert time to avoid any issue in future in the project. This way PM can have clear picture of what to expect. 295833864 Suggestion to customer. 0 3/11/2012 1:13:42 PM Robyn Little I would suggest an alternative or explain to them why we do not really need to include this area into the project. Eliminating will also save time and money for the company. As long as the customer understands that this area of the project is not necessary and will save on the bottom line, money and time, they will hopefully understand and agree. I would explain that this may be something better handled by them after project completion or what ever I could come up with pertaining to the project and the budget and their company. 297005031,29757 296679435 Responding to Customers when Crashing the Project Schedule 0 3/12/2012 8:56:08 PM Professor Firestone Folks, it is time to deal with the "Ah ha" moment! There have been many examples from you about reacting to customer requests to shorten the project schedule and duration. Now for the 'meat' of this request! ;-) How do you respond to customer requests that may not be in keeping with the thought of only critical tasks! Looking at the consideration of managing the customer aspect, why do you think the customer would tell the project manager to crash any project task that is not on the critical path? 297571255,29789 297005031 296679435 RE: Responding to Customers when Crashing the Project Schedule David Froning 3/13/2012 2:47:55 PM One reason I can come up with for a customer to request crashing a non critical task, would be the need to get a certain resource or group of resources off the project and utilize them else where on a different project or to get them on a critical task to help the bottom line. A PM needs to look at this closely to make sure that they keep the customer satisfied not only with the product, but with the entire project. 297895637 297571255 297005031 RE: Responding to Customers when Crashing the Project Schedule Miriam Hassan 3/14/2012 6:45:02 PM Other reasons could be the availability of limited resources, an expected increase in price, unfavorable weather conditions or the threat of strike within the subcontracted trades and vendors. When customers ask the PM to crash a project it is more than likely to be a request made in their own interest without acknowledging the consequences (if any) of making this demand. As project manager careful consideration must be given to ensure the project's schedule is not impacted must be given prior to engaging in the customers request. Once again, the decision made by the PM is in the best interest of the client. 297895637 297571255 RE: Responding to Customers when Crashing the Project Schedule David Froning 3/15/2012 12:00:33 PM I never thought about it in regards to weather. I should have. We had a project that involved Lineman contractors working on our distribution system. We had about 20 crews from a contractor that we had work for about 2 months bringing a new feeder or pole line about 2 miles. When Katrina hit the contractors wanted to bring these crews down south for the storm work, which was much more lucrative to the contractor. They wanted to work around the clock on their portion of work to complete it in less than 3 weeks. It was great for me, but it cost the contractor the OT to pay his crews, it did not get charged to my project, and I actually got done much faster than planned, and the contractor was able to pull his crews out early to go to the storm damaged area to work. In the long run they lost on my project, but the company gained by getting the crews to the storm area quicker. 298880032 297005031 RE: Responding to Customers when Crashing the Project Schedule Aaron Downing 3/17/2012 3:04:00 PM I think this is a very valid point David. If the project doesn't have dedicated resources, the customer may want to free up those resources as soon as possible, thus they want you to finish as fast as possible. As long as it doesn't effect the quality of work or product, you may have to appease them. 297027001 RE: Responding to Customers when Crashing the Project Schedule 296679435 Vanansio Samson 3/13/2012 3:46:05 PM If it would benefit the project, then I will probably evaluate the situation, and if not, then I will say NO to the request. As a project manager, I will keep my priorities lean, there will always be many good ideas that did not make the crash. I will express it as a relative decision; the idea in question might be good, but not good enough relative to the other work and the project priorities. If the item is on a priority two (2) list such as a non-critical path, I will convey that it is possible and will be done, but that no one should bet assuming it will happen. 297165138,29909 296836654 RE: Responding to Customers when Crashing the Project Schedule 296679435 John Sebastien 3/13/2012 5:59:11 AM Most times customers request that project managers crash project tasks, is in situation of desperate need for shortening the project time frame. Sometimes the general operations of the business is dependent on the project being completed urgently, therefore customers would not find any difficulty in throwing additional resources for fast-tracking the project. Also, customers seek to have certain tasks compressed in order to reduce incremental cost. 299097367 297165138 296836654 RE: Responding to Customers when Crashing the Project Schedule Sheila Williams 3/13/2012 8:05:00 PM I agree with John; Crashing is, by definition, a method which can be utilized to attempt to get the most value out of a project assignment. Essentially, it boils down to an attempt to get the most productivity out of the least time and expense. Hence, customers may request the project manager to crash project tasks (not on the critical path) in a attempt of shorten the project duration and/or to reduce incremental costs. In essence, the project manager has to consider that there is a possibility of a new critical path being developed. 299097367 297165138 RE: Responding to Customers when Crashing the Project Schedule Mercedes Santana 3/17/2012 10:38:16 PM I couldn't come up with a reply to the customers that would want to crash project tasks. But I think it's a great learning lesson to consider that the stakeholder/customer maybe requesting for the purpose of cutting cost and completing the task faster. I can see how reducing the time can also reduce the cost but I don't see how it can always be the best way to handle tasks. 296904376 296840511 296679435 RE: Responding to Customers when Crashing the Project Schedule Tyrone Labad 3/13/2012 6:30:29 AM Given that people are working on various activities on the project, it may sometimes be necessary that specific perople are required for other projects or they may be going on vacation or may be unavailable. Due to these reasons, there may be a request either from a customer or from the functional managers that a task which has that resource assigned to them be crashed (even if the task is not on the citical path) so that they can get allocated to other tasks or be released form the project. Another scenario I can think of is when an activtity that is not on the cirtical path needs to be crashed is when teh task is a resource and cost intensive task, and there is a request for crashing it so that money can be saved by doing the activity faster. For instance, if there is a consutant engaged at rate of $1000 per day or if there needs to have time for tetsing on a costly mainframe computer, there may be requests for crashing these activities so that the cost expended on these activities are minimized. 296904376 296840511 RE: Responding to Customers when Crashing the Project Schedule Echo Woolf 3/13/2012 10:18:28 AM For the most part, customers do this because they want to save money, resources or reduce costs. Therefore, if a task that isn’t on the critical path can be eliminated they may weigh the benefits and realize this is the best choice. An example could be if there are 3 engineers on a non-critical path task, and on a critical path task they need more engineers but do not want to increase their overhead, they may crash the non-critical path task. Therefore, they can move those resources (people) to a task that has more of an influence on the project success which will help keep the project stay on track and save labor costs. 297207563 RE: Responding to Customers when 296679435 Robyn Little 3/13/2012 9:04:52 PM Crashing the Project Schedule Maybe they don't want to deal wih the project manager anymore because they don't like their ideas or they think they can use their employee resources to come up with better results in those areas of expertise, or it is just too expensive and time lengthy in their opinion. 297260283 296679435 RE: Responding to Customers when Crashing the Project Schedule Nazish Raja 3/13/2012 10:33:39 PM Crashing a project is only crashed when it’s on a critical path otherwise there is no need to affect the schedule. Crashing a project is not a good thing but it happens when the project is behind schedule and the activities that are already gather for the project will be compressed down. Also, you also lose money because the time and money spend is wasted and money may be spend more to finish off the crashed project. Text Book chapter 5 297441943 297131692 296679435 RE: Responding to Customers when Crashing the Project Schedule Marquita Blair 3/13/2012 7:17:53 PM There are is only one reason I can think of for crashing a task that is not on the critical path, the customer trying to gain more slack time for something else or decrease time for something else. Because crashing only works on tasks in the critical path. Reducing time on a non-critical tasks has no affect the project delivery time. It's a waste of time crashing non-critical path tasks for the sake of reducing time, so my only guess is the task the customer wants crashed, has noting to do with project time, their reasoning must be based on the effect it will have on another task. 297441943 297131692 RE: Responding to Customers when Crashing the Project Schedule David Froning 3/14/2012 1:18:50 PM The customer may even want those resources on an entirely different project that is in need of the same resources being used on the no critical task that they want crashed. 297772225 RE: Responding to Customers when Crashing the Project Schedule 296679435 Kathryn Martinez 3/15/2012 1:40:07 AM From review a client would want a crash done if necessary to avoid certain things if possible for example if I were to be in construction and we had to build a roof the weather would have a lot of influence on my work schedule. A contractor would crash the project in order to save the roof from bad weather if there were a possible rain storm coming soon. For a client to want us to crash a project not on a critical path would probably for personal reasons such as financial or resources are limited. 296916761 RE: Responding to Customers when Crashing the Project Schedule 296679435 Joseph Allen 3/13/2012 10:52:50 AM From my experience customers ask that project tasks be crashed outside of the critical path for a couple of reasons. One, for some reason they feel that portion of the project needs to be completed, or they want it completed. This is sometimes to appease their immediate boss. It could be a series of tasks that may show project progress, maybe visual progress. Or they want that portion of the project done to see and accept that particular deliverable on a certain date. The other reason they ask for tasks outside of the critical path to be crashed is that they do not understand the project schedule and begin to try to manage the project themselves. They feel that if certain project tasks are crashed the duration of the project can be shortened. In either case it is important to help the customer understand the project schedule and the reason tasks are done in the order they have been planned. Managing your customer is as important as managing the project. 298021024 RE: Responding to Customers when Crashing the Project Schedule 296679435 Melissa Burr 3/15/2012 5:13:47 PM A reason a PM could be asked to crash a particular task by the customer could include financial problems that need to be resolved and by cutting certain tasks could resolve them. 298032891 RE: Responding to Customers when Crashing the Project Schedule 296679435 Brandi Williams 3/15/2012 5:37:58 PM The customer would more than likely tell the PM to crash a project due to time constraints or financial constraints. Something would be at "stake" and clients are stakeholders, therefore they have something to gain or lose and they'd much rather "gain". So there perspective is not the same and they do not approach "crashing" fromt the same point of view as the PM and team. 298227239 RE: Responding to Customers when Crashing the Project Schedule 296679435 Herbert Anderson 3/15/2012 10:20:39 PM Good question Professor, I'm not all the sure but it all could lead to scheduling; The client might have external issue that result in a speed up of a project or bring on another project to gain a certain purpose. Theirs serval reason why a client make these split decision, however its up to the PM to meet the customer exception and maintain the original project. crashing a project on a critical path is risky and should be thought through before final decision are made. Now I wounder if this crash the project on a CP has something to do with the PM performance? Is it that the PM is behind on schedule, and this is the reason for crashing? Im starting to think that the PM is mostly the reason for the crashing of any project, because why would a client want to risk any project the threat is high. 299569480 RE: Responding to Customers when Crashing the Project Schedule 296679435 3/18/2012 9:48:55 PM Kevin Shaw I still think that it falls along the same lines as the other. You have to keep the customer informed and make sure that everything is documented. 298881289,29823 297200522 Responsibility and Accountability 0 3/13/2012 8:54:34 PM Professor Firestone We are off to an incredible journey with so many quality responses so far! Here is a consideration. Once the customer and the project manager agree on a project schedule, who is responsible for getting the work performed? Who is accountable for getting the work performed? Is there a difference, and why? How could this impact the project schedule? (You might keep in mind some of the discussion and material from previous weeks.) How about an example that is 'different' enough that it would not fit your original thoughts and response. 298881289 RE: Responsibility and Accountability 297200522 Aaron Downing 3/17/2012 3:07:33 PM The PM doesn't perform the work per say but he/she is definitley responsible for coordinating the efforts to get it done. The line managers are responsible for managing their resources to get specific tasks complete. The biggest issue I see here is that the line manager may not dedicate all the necessary resources to the projects needs, thus changing the project schedule. 299219685 298237438 RE: Responsibility and Accountability 297200522 Herbert Anderson 3/15/2012 10:39:14 PM The project manager is held accountable for getting the work performed, yet the functional manager must share the resource and the project team must meet the deadline the PM sets from the start. The FM must work with PM to meet deadlines and according to the past studies PM's and FM's are like cats and dogs, its hard the link them up if communication & understanding is lost. Nevertheless, the PM should be a expert at building a team and keeping schedule. In a perfect world if the FM is helpful toward the PM and the project team is on top of their objectives, then the impact of the schedule should be low. But in most cases this never happens because people are people and mistakes are made. Therefore different plans are draw out for the what-ifs 299219685 298237438 RE: Responsibility and Accountability Donte Whiting 3/18/2012 10:49:34 AM Great posts Herbert and I agree. Id like to add that the only thing I see wrong with this, is if the PM and the FM are not on the same page, this can become an issue. Like you stated that if the FM and the PM are on top of their objectives everything should go as plan. But if that communication slips and neither are on the same page this can cause for an extend project which could be thrown off schedule. 297897620 RE: Responsibility and Accountability 297200522 David Froning 3/15/2012 12:05:54 PM This is where the Functional manager versus Project Manager falls into play. The PM is accountable for making sure that the work is getting done and the projects stays on task. But the functional manager is responsible for giving his resources and skills to actually getting the work done. This is why it is so hard if the team is not all on the same page. The functional manager must understand the Projects deadlines and needs. 299619041 RE: Responsibility and Accountability 297200522 Albert Wells 3/18/2012 11:18:18 PM I may be wrong here but I believe that the job of the PM is to manage the project and one aspect of that is to ensure that the work is done in a timely manner. This is an indirect responsibility of the PM. The PM is managing the project making sure things are on schedule and that every one is communicating effectively and that clear paths for resolution are available for both risk and conflict. This combined with managing the budget and the time line give a PM an incredible amount of control over the work that is or is not completed on the project. I think we also need to recognize the importance of having realistic expectations set for and by the customer. 297486959 RE: Responsibility and Accountability 297200522 Vanansio Samson 3/14/2012 3:29:37 PM Of course the project manager. Project managers are considered to be resourceful and innovative, and they must adapt to ever changing circumstances faced in the projects they managed. This includes dealing with deviations from the project plan, changes to the project scope, sudden unavailability of expected resources, late shipment of purchased equipment from supplier, and unexpected events, as well as other issues related to the project (s). An effective project manager involves managing a complex and expansive set of interfaces between not only complex technical elements, but also a wide range of individuals. 297488873 RE: Responsibility and Accountability 297200522 Sharon Jno-Baptiste Griffin 3/14/2012 3:35:04 PM Once the project schedule is agreed on, the Project team is responsible a for getting the work done, however, the project manager will be held accountable for work not getting done or schedule not being met. The project manager is responsible for his project team and therefore will be held accountable for their actions. 297282072 RE: Responsibility and Accountability 297200522 Daniel Worcester 3/13/2012 11:33:16 PM My traditional train of thought is that the PM should be held responsible for all aspects of the project. However a project manager should have supervisors that are responsible for getting the work done where as the project manager is accountable for the work being performed. An example of this would be a product being built after design the supervisors are responsible that the work gets done however at the end of the day the PM is not only responsible for the work getting done they are also accountable for the time in which it gets done, the quality in the work, and the efficiency of both the quality and the time it takes to produce. 297359915 RE: Responsibility and Accountability 297200522 Brandi Williams 3/14/2012 9:19:00 AM The PM is responsible for getting the work performed by delegating task assignments and monitoring the process of completion of those assigned tasks. The individual team members and the PM are accountable for getting the work performed. It is a "shared" accountability with different "weights". There is a difference in the level of accountability because ultimately, the PM is managing the project, although not personally performing the tasks, he/she has assigned these tasks. The PM's stake or "weight" is heaviest because the PM must answer personally to the client(s) who have entrusted him with their product/service and finances. That makes the PM accountable from a management and stakeholder standpoint. Managers cannot totally shift the blame on the person assigned because it is the manager's responsibility to delegate "responsibility" and to monitor the project's progression. At the same time, the team member is accountable for completing the tasks assigned to him/her. If you're on a team you serve as an "active" member and you must perform or else there is no purpose for you to be on the team. So if the team member "fails" to meet requirements, then that team member has failed the team as a whole, the PM, and the client. Team members serve each other and are accountable to one another as most team projects have dependencies. For example, if I fail to complete my duties as an engineering tech, this will negatively impact the engineers I support because they depend on me to provide output or analysis of the progression of their wells. All team members are valuable because they provide a skill/service/need that is important. The project schedule will always be negatively impacted (usually time or money) if some fails to do their part and perform their duties as needed. It wastes valuable time and it costs more to have someone else do the work that should have been done by that team me mber. 297383323 RE: Responsibility and Accountability 297200522 Joseph Allen 3/14/2012 10:30:07 AM In creating the schedule the PM should have involved the functional mangers and received their "buy in" for the schedule and to provide the proper resources. In that respect the functional managers are responsible for getting the work performed. The PM is accountable to ensure this work is performed to project schedule. Should the functional managers not be able to get the work performed they are accountabl e to the PM for the reasons that the work is not performed and how they intend to keep the project on track. The PM and functional managers must work together to ensure the project stays on track. Ultimately the PM is accountable to the customer on the project and the project schedule. Team members and functional managers must be accountable to the PM to ensure they have the proper information to relay to the customer. 297428642 RE: Responsibility and Accountability 297200522 Sheila Williams 3/14/2012 12:40:45 PM The project manager has the overall responsibility for the successful initiation, planning, designing, executing, monitoring, controlling and closing of a project. Notably the project manager has the responsibility of coordinating and integrating activities across various functional lines. At the same time, it is the functional managers who will decide how and where the task will be done, and who will get the job done; they have the responsibility for the deliverable. In other words, the functional managers are responsible for the technical, once the project manager identifies the requirements (Kerzner, 2009). This is why it is so important that the project manager good communication and relationship skills because s/he has to ensure that the project is completed as planned. Source Kerzner (2009). Project Management (10e). John Wiley & Sons 297491198,29753 297434473 RE: Responsibility and Accountability 297200522 Syleisha Smythe 3/14/2012 12:57:33 PM I do believe there is a difference between accountability adn responbilility. I would think that the project manager is "accountable" for making sure the project work gets done and the functional managers are the one ones actually "responsible" for the work/task completion. For instance, on a system implementation project I participated it, the organization assigned an internal employee as the project manager and had an outside consulting firm assist with the implementation who assigned their own project manager for their purposes. The two ended up working alongside one another, but the internal project manager was "responsible" for ensuring the functional managers and employees work was completed, but the external PM was ultimately "accountable" for the success of the project and ensuring all deliverable deadlines were met. 297538582,29797 297491198 297434473 RE: Responsibility and Accountability Sharon Jno-Baptiste Griffin 3/14/2012 3:41:34 PM Syleisha, you make a great point in differentiating the difference between accountability and responsibility of the project manager. I just think that the functional managers are not responsible for the work done. That would be the project team who usually is put together by the project manager. The project manager knows his project, the skillset, knowledge and competencies required and he staffs the projects. In that case, the team members should be held responsible for thier assigned activities, however, the project manager should be help accountable for the overall project success or failure. It is now the responsibility of the project manager to ensure that his team is being production and to monitor the project to ensure that it is on track to finish on time, project deliverables are what's needed and the project is completed within budget. 297971066,29884 297538582 297491198 RE: Responsibility and Accountability David Page 3/14/2012 5:41:47 PM Obviously, different environments are going to create different dynamics within a project. However, in the end I still believe that the PM is overall responsible and accountable for the project. That said though delegation of authority and responsibility can be handed down through the levels as the PM can’t be everywhere monitoring everything at once. Again though the PM has the overall picture of the project and knows where the shortfalls are and needs to address those things. While the PM does not have control over the functional managers the PM does have to maintain some control of the project and will have to resolve the shortfalls and find ways to gain more support from whoever is impacting it. For the work to get done at the lower levels the PM needs to make sure that their managers have what they need to help them get their job done. The PM in my eyes thus far through school is to ensure the budget, schedule and quality is upheld as well to ensure that the stakeholders are informed, empowered and the tools to do their jobs, as well as act as the buffer between the functional managers and top management so that those that are performing the work can do their job effectively and efficiently. 297971066 297538582 RE: Responsibility and Accountability Syleisha Smythe 3/15/2012 3:13:31 PM Thanks for your comments, Sharon :) I think David hits the nail right on the head! Whether it is the functional managers or the project team would depend of the organizational environment. I have a tendancy to speak from my previous experience where normally the project team was made up of functional managers who provided resources to the project manager in a more traditional/non-project driven organizational structure. 298842151 297538582 RE: Responsibility and Accountability 3/17/2012 1:22:00 PM Leigh-Ann Joseph I agree with you David, but it also depends on how the companies hierarchy is set up and where responsibility and accountability should lie. In my case for example, my organization recently hired a PMO (Project Management Office). Prior to this, we didn't officially have PM's and my Director of IT was in the functioning role as PM. The projects I coordinated and implemented had me functioning as PM assistant and it was my responsibility to completely organize and coordinate all aspects of the project life cycle with the guidance of my Director. Now, with our organizations newly added PMO the hierarchy is slightly different, with some similar roles. We now have the Senior Project Manager, One Project Manager, Director of IT, Project Team Members where there are 5 of us. The initial organziation is done at the top, with tasks filtered down to each of the Project Team Members. Each role has certain responsibilities and are accountable usually to the person above us directly. As a whole team part of the Office we are accountable to the organziation for the success of the project. I hope this is clear. 297495872 crash the project 0 3/14/2012 3:55:04 PM Donte Whiting In crashing, the time is reduced by increasing resources. But the sequence is not disturbed. For example, a project involves raising a boundary wall in 16 days and moving machinery crates in 8 days, the total duration being 24 days. By engaging more workers and excavators, the boundary wall can be made in 12 days and machinery shifted in 4 days, reducing total time to 16 days. please take a look at this site, it provides a great scenario of a crash project...http://hafeezrm.hubpages.com/hub/REDUCING-PROJECT-DURATION 297621869 Crashing a project 0 3/14/2012 8:03:26 PM Derek Cavanaugh Any time changes are made to a project schedule, whether crashing the project or extending a deadline, it is imperative that you have a meeting with the customer to determine their reason for the request. As a project manager, you can go over their request and provide a risk analysis that will allow you to address the feasibility of it. Sometimes activities that are not on the critical path may still be necessary for the project's completion and that information needs to be addressed. Also, there are also activities that are not necessarily "must have" activities and wouldn't be on the critical path, but they would be "nice to have" activities that the customer has a special interest in and would like to see completed because they may have another interest that the would like to explore if that extra activity turns out in a certain way. 297690283 Crashing the Project Kimberly Brewer 0 3/14/2012 9:40:33 PM I would have to do an analysis to see if the process/component of the project can be crashed. The thing is, I may have put the steps in the process the way that they belong for a reason. As Professor Firestone mentioned, there are going to be consequences and we must make sure that we will not suffer as a result. If there are negative consequences that are found during the analysis, this must immediately be shared with the customer so that they understand why I cannot honor their wishes. 298194563,29797 297700074 What to do about crashing the project schedule 0 3/14/2012 9:55:38 PM Professor Firestone A few nutshell considerations to keep in mind about crashing the schedule in project management, Everyone, and as you are already seeing from your colleagues in the course. Rarely will a project's quality be sacrificed. Hence, quite likely you need to keep this as a constant. To crash a schedule normally (in every circumstance I have encountered) means to reduce the time for the project by using additional resources. This normally equates to adding costs. You will be required to minimize additional costs. Some project sponsors will require you to make other tradeoffs with the project time and project cost. Now, what are you to do, knowing this when you crash a schedule? 298194563 RE: What to do about crashing the project schedule 297700074 Robyn Little 3/15/2012 9:30:25 PM "One of the most commonly utilized methods of crashing a project schedule involves minimizing the schedule activity durations while, at the same time, increasing the assignment of resources on schedule activities. Crashing is something which can be utilized to attempt to get the most value out of a project assignment. Essentially, it boils down to an attempt to get the most productivity out of the least time and expense."http://project-management-knowledge.com/definitions/c/crashing/ Crashing the project kind of like keeping up with production where production calculations are important. Get as much as possible out of one area while at the same time not needing more people to get the same results. That's what I get out of the definition. I have not ever even heard the term in any of my classes until now and I'm almost ready to graduate. 298626808,29902 297975579 RE: What to do about crashing the project schedule 297700074 Syleisha Smythe 3/15/2012 3:25:03 PM From the considerations listed I would say that it is important for the PM to keep all of those things in mind when trying to figure out a "crash course". Assuming the considerations, I would attempt to find the best way to shorten the project schedule without sacrifices to quality and cost, and hoepfully evenly distribute the trade-offs of time and scope. But if we are also to assume the triple Constraint theory then we need to realize that no matter what we can not trade off one without afecting the other 2 (time, cost, scope). And any organization employing PMI standard methodology would realize this as well. 298626808 297975579 RE: What to do about crashing the project schedule Echo Woolf 3/16/2012 9:22:25 PM Nicely said! I think it very important to consider how the decision to change the scope will affect the costs, or changing the time frame will affect the costs and so forth. As a project manager you have to look at the bigger picture and how one decision can affect a lot of other decisions moving forward. A PM should review the tradeoffs and discuss them will the customer. If they are well-informed and understand the effects that can come from changing the time, scope or cost, then they can give this information to the customer, which may affect their decision. Mainly because the customer may have tunnel vision if the project is time constrained, and not look at the other factors it could alter. 299023413 297975579 RE: What to do about crashing the project schedule Derek Cavanaugh 3/17/2012 8:29:12 PM I think that you made some really valid points. It seems that whenever a project is being crashed, the costs can really go up considerably because quality cannot be sacrificed. Therefore, the budgetary constraint will really come into play. I think it would depend on your industry because in some companies, if a project needs to be crashed for reasons of meeting metrics or beating the competition (such as in the pharmaceutical industry), a more advanced project can be crashed and receive supplemental budget from projects with lower importance in order to cover the increased cost that the crash incurs. 298797232 297975579 RE: What to do about crashing the project schedule Donte Whiting 3/17/2012 11:19:07 AM Great post, the PM would want to make sure that the utmost care should be taken to make sure that appropriate activities are being crashed and that diverted resources are not causing needless risk and project scope integrity. 298539297,29817 298006257 RE: What to do about crashing the project schedule 297700074 Sharon Jno-Baptiste Griffin 3/15/2012 4:40:17 PM I don't think that a PM should compromise the deliverables of the project by making tradeoffs. If there are ways that cost and time can be saved then the PM should take advantage of that, however, whenever, there is crashing, there is increased cost and usually shorter project duration. The PM can explain in detail to the customer the impact of making tradeoffs. 298539297 298006257 RE: What to do about crashing the project schedule Summers Love-Morrison 3/16/2012 6:14:23 PM Sharon, Good post! I think that the PM should always look at wasy to lessen the time and the cost. If a PM can get the project completed early and under budget than it shows the higher ups that he/she is good at what they do. Crashing a project causes so much undue stress, with the rising cost, it will also shortent he length of the project. I personally think that if we can keep the project on track and under budget than, by all means, lets make it happen. 298253593,29835 298174183 298006257 RE: What to do about crashing the project schedule Professor Firestone 3/15/2012 9:02:41 PM Bingo and it is such a thrill to hear how you are grasping the information and approaches! Now, Folks, how might you approach telling the project customer your findings, especially if this is not what the customer wants to hear? Remember: the buck stops with you, the project manager. [Those of you who are history buffs may recall that President Truman had a sign on his desk in the White House that said "The Buck Stops Here." And a buck was a significant amount of money in the 1940's.) 298253593 298174183 RE: What to do about crashing the project schedule Herbert Anderson 3/15/2012 11:13:48 PM The customer must understand the basic constraints (scope, time, budget) first, this way we have something to refer to with the client. The fact is when crashing a project its for the time to be reduce with whatever means of resource. To consider a tradeoff would only hurt the project and shouldn't be consider. because it effect the constraints. If you rush a project based on time, then your cost would be high and the output of the project performance might not be as affective, if you just let the scope of the project take its normal course. Here's another visision site I found that might help the client realize the risk invole here. In this section, we shall consider the impacts of time, cost and quality tradeoffs in activity durations. In this process, we shall discuss the procedure of project crashing as described below. A simple representation of the possible relationship between the duration of an activity and its direct costs appears in Figure 11-3. Considering only this activity in isolation and without reference to the project completion deadline, a manager would undoubtedly choose a duration which implies minimum direct cost, represented by Dij and Cij in the figure. Unfortunately, if each activity was scheduled for the duration that resulted in the minimum direct cost in this way, the time to complete the entire project might be too long and substantial penalties associated with the late project start-up might be incurred. This is a small example of sub-optimization, in which a small component of a project is optimized or improved to the detriment of the entire project performance. Avoiding this problem of sub-optimization is a fundamental concern of project managers. Figure 11-3 Illustration of a Linear Time/Cost Tradeoff for an Activity At the other extreme, a manager might choose to complete the activity in the minimum possible time, D cij, but at a higher cost Ccij. This minimum completion time is commonly called the activity crash time. The linear relationship shown in the figure between these two points implies that any intermediate duration could also be chosen. It is possible that some intermediate point may represent the ideal or optimal trade-off between time and cost for this activity. What is the reason for an increase in direct cost as the activity duration is reduced? A simple case arises in the use of overtime work. By scheduling weekend or evening work, the completion time for an activity as measured in calendar days will be reduced. However, premium wages must be paid for such overtime work, so the cost will increase. Also, overtime work is more prone to accidents and quality problems that must be corrected, so indirect costs may also increase. More generally, we might not expect a linear relationship between duration and direct cost, but some convex function such as the nonlinear curve or the step function shown in Figure 11-4. A linear function may be a good approximation to the actual curve, however, and results in considerable analytical simplicity http://pmbook.ce.cmu.edu/11_Advanced_Scheduling_Techniques.html 299620093,29848 298351046 298174183 RE: What to do about crashing the project schedule 3/16/2012 9:23:49 AM Daniel Worcester I find that the more information that you can give the clients the better off you are when telling them something they dont want to hear. I have found that when giving them information it is best to show them two scenarios one with the effects of what they want implemented, and the other as a comparison to what the original plan was and how the effects will change the project. 299620093 298351046 RE: What to do about crashing the project schedule 3/18/2012 11:20:53 PM Albert Wells In my work experience its always better to come with a solution when you have a problem. I think I will carry this over to my work as a PM. If I need to convey "bad" news to a customer I need to have supporting information on what lead to the situation and available options and how they will impact the customer and project. This is of course tempered with my and my teams professional opinion based on our collective experience and the unique situation on how to proceed. I think most customers do not want excuses but respect facts. 299522091 298480327 298351046 RE: What to do about crashing the project schedule 3/16/2012 3:24:08 PM Sheila Williams This would be my approach, as well. I would have no problem approaching the customer to explain the additional costs that would result from crashing (I believe that the customer would appreciate honesty, in the long run). I would explain the added costs and present it in written form, so that a comparison could be made. Then, I would present the same information from the original plan. With this information in hand, the customer would be able to make a better informed decision. 299522091 298480327 RE: What to do about crashing the project schedule Herbert Anderson 3/18/2012 8:47:25 PM Daniel and Sheila, you guys are on a great track, if I could add, I would approach this manner carefully. The client has a vision for the project, but they they don't truly understand the implementation process needed to achieve their goals. As a PM we must share all details of the project, but we must also keep the client focus on the big picture and the budget/time frame behind. This being said the client must understand their limited with cost and time. If the project is large its hard to crash a project and plan for a successful outcome. Therefore, it's important how you share the information to the customer. In other words don't lead them on to think that we could make sudden changes or add on's, if the project can't produce the outcome. 299510781 298852746 298174183 RE: What to do about crashing the project schedule 3/17/2012 1:50:07 PM Kimberly Brewer In my opinion, honesty is the best method for getting the customer to understand. Yes the delivery must be tactful and intelligent, but overall, they must understand what sacrifices the project would take in the event of crashing if there isn't simply some waste that needs to be cleaned up. Like for instance, maybe something was overlooked during planning and a timing can be pulled in a bit. I think that explaining all of the detail to the customer so that they understand clearly is the best way to help them to understand the direction you as the project manager must go to make the project a success. 299510781 298852746 RE: What to do about crashing the project schedule 3/18/2012 8:33:26 PM Derek Cavanaugh I agree that honesty may work best. Whether or not the client will be happy with what you are saying is another story, but if you lay it all out and show them all the details they may get a better understanding of your needs for planning purposes and why you are for or against one of their requests. While you should do what you need to do to make the customer happy, they need to know that you have all the tools and strategies straight for proper planning and execution. 298882551 RE: What to do about crashing the project schedule 297700074 Aaron Downing 3/17/2012 3:10:55 PM Well this is really a double edged sword because you have given certain time estimates up front which equate to a certain amount of hourly labor rates in most cases. By adding additional resources to shorten the schedule, you do incur some additional nominal costs but you may make up for that by shortening the overall timeline. If you crash a certain task, I suppose you better make sure to minimize any other factors that will lengthen the project duration. 297970806,29840 297885298 RE: What to do about crashing the project schedule 297700074 Joseph Allen 3/15/2012 11:33:48 AM It is important to understand from the project sponsor or the customer the objective they are trying to achieve by crashing the project, and the trade-offs they are willing to accept. It must be made clear to the customer, whether internal or external,what those trade-offs will be. For instance if the crashing process is in fact going to add additional cost to the project the customer should be made aware of exactly what those costs will be. If the customer elects to reduce the workscope, the deleted items from the project should be explained to the customer. These changes should be captured in the change order process and fully documented in writing. 298404962 297970806 297885298 RE: What to do about crashing the project Shadina Pennybaker 3/15/2012 3:12:49 PM schedule I agree Joseph, as long as the customer agrees and everything is in writing there shouldn't be a problem. I personally would never trade off quality, because your name is everything and if it falls apart down the line, or someone gets killed it falls on you and your company. Like I said last week, you can't change one of the constraints without affecting the others. You can't change quality, so time and/ or cost will change. 298404962 297970806 RE: What to do about crashing the project schedule Frederick Rock 3/16/2012 11:53:01 AM I agree here, it is incumbent to ensure that the customer understands what the trade off are going to be. Sometime this mean more cost other may mean compromising the scale or scope of the project. But the customer has to be in on the discussion, other wise your in for a very unhappy client if they assume that this would be included. 297940669,29859 297766653 RE: What to do about crashing the project schedule 297700074 3/15/2012 12:47:10 AM Tyrone Labad When we have to crash a project's schedule in order to reduce duration or bring forward the project completion date, we should always ensure that we are trying to crash those activities that are on the project critical path. This would ensure that crashing results in schedule reduction. However, while we do this, we must consider and evaluate the below aspects 1) Do we have additional resources who can perform the activities at the same quality 2) What are the additional cost implcations and do we go over the budget 3) Would subsequent activities be able to adjust and come forward as well, or are there activities that have fixed dates 4) Does the project risk increase due to this All this will help us evaluate and make the right and calculated decision 298590191 297940669 297766653 RE: What to do about crashing the project schedule Sheila Williams 3/15/2012 1:55:52 PM Also, it is important to understand the reason the objective for "crashing." Most projects and tasks will have a trade off relationship between the time taken to complete a task and the cost;taking too long will increase the cost as wages and other costs will increase; reducing the time requirement sharply is likely to increase costs as more direct materials, overtime and other resources must be directed towards the task. Therefore, the trade-off will be in either time, cost, or both. 298590191 297940669 RE: What to do about crashing the project schedule Nazish Raja 3/16/2012 8:08:23 PM I agree Sometimes a project being crashed isn't necessary the clients fault or even the project managers fault. For example; at the company I work for, we deal with drilling waste and when a technician is on a project but the weather is not cooperating then delays will happen to the point where the project may be crashed. We had a sump project that needed to be completed within 3 weeks due to the pressure from the client that owns the area. But the weather was terrible and it wouldn't stop raining where it cause major delays and all the solids and fluids where tanked first to see if the weather gets better but it didn't so it cost a lot of money and had all the waste hauled to facility for disposal. 298582969 297957116 RE: What to do about crashing the project schedule 297700074 John Sebastien 3/15/2012 2:37:35 PM The key to project crashing is attaining maximum reduction in schedule time with minimum cost. Quite simply, the time to stop crashing is when it no longer becomes cost effective. A simple guideline is: Crash only activities that are critical. Crash from the least expensive to most expensive. Crash an activity only until: o It reaches its maximum time reduction. o It causes another path to also become critical. o It becomes more expensive to crash than not to crash. The rules of thumb for crashing a schedule are always crash or shorten tasks on the critical path and choose to crash tasks that will have the least impact on the project's budget. http://www.brighthub.com/office/project-management/articles/5055.aspx 298582969 297957116 RE: What to do about crashing the project schedule Tyrone Labad 3/16/2012 7:53:56 PM Many thanks John for these consideration while crashing, I think you have captured them and makes me understand it very well. I would just like to add that a project manager should not always be ready to crash the project and do so at every given opportunity or request. This is because every time a project is crashed, there needs to be a lot of communication that has to be made, works rearranged, people working on tasks rearranged and essentially changing the initial project plan. This could lead to disruption in the project which must be effectively managed with a change management approach and proactive communication approach - but as a rule one should crash only when it is absolutely necessary or it is very high business priority. 297770865 Adjusting the Project Schedule Kathryn Martinez 0 3/15/2012 1:21:52 AM As the project manager if a customer asked to crash an activity that was not on the critical path in my opinion it would be okay to crash the activity. Crashing is trying to push through a project or activity faster. So it all depends on activity or project. So as the project manager, I would have to have discernment and good judgement when it came to which activities should and should not be crashed. For more information on Crashing Projects I found this tit bit of information on the web http://pmstudent.com/crashing-a-project/ This site gave me an idea of how to make the judgement when it came down to crashing a project. 298719904,29918 298625677 You are now responsible for a key project in progress AND in trouble 0 3/16/2012 9:20:04 PM Professor Firestone Folks, here is a 'not uncommon' situation that we can use to develop more skills as project managers. Let's hear your thoughts and D.A. (Devil's Advocate) questions. The Director of Project Management calls you into his office and informs you that one of your fellow project managers has had a severe heart attack midway through a project. You will be taking over his project, which is well behind schedule and overrunning costs. The Director of Project Management then assigns you to the project and to complete within the current time and cost. How do you propose to do it? Where do you start? Should you shut down the project to re-plan it? What else? [Your rationale is very important.] 299182767,29905 298719904 298625677 RE: You are now responsible for a key project in progress AND in trouble Melissa Burr 3/17/2012 6:54:27 AM I don't think I would necessarily shut down the project but I would pause most areas during a reevaluation to see where budgets and time started going off-track and actions I could take to help curb this. I would do the evaluation as quickly as possible because if it isn't feasible to finish as requested by my boss, they need to know that along with suggestions of how I will come as close as possible (or what severe actions may need to be taken to do so). 299182767 298719904 RE: You are now responsible for a key project in progress AND in trouble Summers Love-Morrison 3/18/2012 8:51:28 AM Melissa, Good post, Not shutting the project down is the correct answer. I feel that a re-evaluation can be done in the midst of the project. I think that if all hands are on deck in the re-evaluation than it will speed up the process. I understand that budgets and times may be off, but ensuring that we at least meet the minimum requirement in a time where there is much confusion is better than being complete off shcedule and over budget. 299620252,29963 299056167 298719904 RE: You are now responsible for a key project in progress AND in trouble Professor Firestone 3/17/2012 9:23:31 PM It is good that you point out how to keep going but also being reasonable in your approaches, Melissa. Almost all approaches are valid. The biggest challenge - after agreeing to meet at least two of the Triple Constraints - is how you would approach gaining 'allowance' for the third. For example, if you are going to meet the schedule, quite likely you will need more budget and/or scope/quality 'extras'. Of course if one of the other constraints has higher precedence with your project sponsor/customer, how will you handle that with him/her? Also, be sure to provide your approach and rationale. 299630384 299620252 299056167 RE: You are now responsible for a key project in progress AND in trouble Shadina Pennybaker 3/18/2012 11:21:17 PM If the budget took precedence over the other two constrains then I would see where changes could be made to save money. I would also identify the slack time in the critical path to make up for most of the time and money lost. 299630384 299620252 RE: You are now responsible for a key project in progress AND in trouble Daniel Worcester 3/18/2012 11:47:08 PM Shadina to add to your comment I think that a crash could be warranted if an opportunity in material made its self present. For example if a project has a material requirement that is on a special price but must be taken advantage in a limited time it may be worth the effort to crash the schedule to take advantage of this opportunity. I think the same can be said for say a weather break in a area that is known for bad weather. One must weigh the opportunities against the potential losses to determine if the overall effect is worth the risk. 299515362 RE: You are now responsible for a key project in progress AND in trouble 298625677 Kathryn Martinez 3/18/2012 8:39:08 PM Modified:3/18/2012 8:41 PM As a young project manager this could be a great opportunity to prove your skills and add more to your resume. If the Director assigns a failing project start with the details to see why it is a failing project and then compare it to a passing project to fill in the objects that are making it a failing project. Look over the project before shutting it down. If there is an opportunity to fix it do the fixes on the project to make it a passing project. Usually project managers take the initiative when doing any project and fill in the spots that need work to rework them. Even if they are stuck with the current cost and time constraints they mold the project to their structure to make it work out. For example out of my own personal experience as a tutor. I wasn't given all the material I need to teach my children but purchased the items I needed to help my children have the experience I wanted them to have when I tutored them. 299602263 298625677 RE: You are now responsible for a key project in progress AND in trouble Leigh-Ann Joseph 3/18/2012 10:42:59 PM In a situation like this I would first do a complete assessment of the status of project. After that report is complete and analysed I would develop a plan to move forward. The plan would depend on the status of the project and if it was on track or not. I would get the plan approved by the Director of PM and then discuss the details with the project team. After these things are done and in place I would continue on with the project. 299627152 299243678 298625677 RE: You are now responsible for a key project in progress AND in trouble Sanah Fatima 3/18/2012 11:57:49 AM First thing I will do is do analysis of what is left to do and how much time we have in our hands. If cost could be little bit of expandable to meet deadline, I would check with my team to see if within a team if anyone is capable of if not, either I would do the job needs to be done or hire or hire new resources. The reason I say hiring new resources at last minutes is this could be more costly. Shutting down project after half-way in the project is not optional for me. Unless it hits the dead end wall, now this could be due to customer withdrawing the project or canceling project. 299627152 299243678 RE: You are now responsible for a key project in progress AND in trouble Michael Boston 3/18/2012 11:38:49 PM I have never been in a contract that would allow me to shut down a project at any point in the project. If losses are going to occur then that is up to me and my company to minimize those losses or to make a profit. I guess it would make sense for a company that was going to loss more money than it would cost them to hire another company to finish the project for them, that may be a reason to quite but I guess the project would then still continue. 299442856 298625677 RE: You are now responsible for a key project in progress AND in trouble Mercedes Santana 3/18/2012 7:03:14 PM Take some time to reevaluate the resources still available and probably reassign tasks to fit the new situation. The goal is to complete the project so people have to be reassigned to different task and possible take on more responsibility. _u=7295436;_dt= C6-FE-37-EE-89-C
© Copyright 2026 Paperzz