{"id":7318,"date":"2012-01-03T07:44:47","date_gmt":"2012-01-03T14:44:47","guid":{"rendered":"https:\/\/svapm.org\/?p=7318"},"modified":"2011-09-05T08:09:01","modified_gmt":"2011-09-05T15:09:01","slug":"handling-the-delays-in-a-project-schedule-part-ii","status":"publish","type":"post","link":"https:\/\/svapm.org\/?p=7318","title":{"rendered":"Handling the delays in a project schedule (Part II)"},"content":{"rendered":"

Certified Business Coach and Corporate Exit Strategist<\/p>\n

\"\"<\/a>\u00a0This is the second part of a three part article discussing \u201chow does a project manager intelligently\u00a0 handle delays in a project?\u201d<\/p>\n

Last article we focused on acknowledging the natural flow of a project which includes periodic speed bumps and roadblocks.\u00a0 In today\u2019s article we\u2019ll focus on using recovery protocol plans to assist with project management.<\/p>\n

Agree to a\u00a0Protocol Recovery plan at the start of a project:<\/strong><\/p>\n

All projects will hit some unexpected issues.\u00a0 By discussing a “protocol recovery plan” at the start of the project, the team will understand how to proceed when time is running out.\u00a0 A “protocol recovery plan” is like a “fire escape route”.\u00a0 At the start of the project, your project sponsors and stakeholder discuss the flexibility of the following:\u00a0 Add Resources, Remove Features, Change Schedule, Reduce Quality.\u00a0 The idea is to agree up-front (before the project starts) which order you will do them.\u00a0 For example, if\/when you hit a snag does the team agree to first investigate adding more resources to the problem?\u00a0 At some point, adding resources will no long be an effective option.\u00a0 At that point, which is the next flexible item to adjust?\u00a0 Would it me to remove some features from the list or would it be acceptable to add time to the schedule?<\/p>\n

Take a look at the below figure:<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

In this company, the group discussed and created the above protocol recovery plan.\u00a0 In their last release they were hit hard with client complaints; technical journals reported on their dismal quality; and they decided as a team that they were going to put out a high-quality product this release.\u00a0 As a result, the group agreed from the start that the QUALITY is the main priority and last to be modified.\u00a0 \u00a0They also understand the order in which the other items will be attacked.\u00a0 Because the group agreed upfront that “QUALITY Standards\u201d will be the last to change, there was no lost time in deciding how to proceed when an issue arose.<\/p>\n

In this example, the team agreed to add resources (until it doesn’t make sense to add resources anymore).\u00a0 Once you have reached the point where more resources will not help, you agree that the next step will be to start removing features.\u00a0 This will only work if : at the start of the project, you understand\u00a0the minimum set of features or services that make the project worthwhile to the client.\u00a0 You will have a set of many other “nice-to-have” features or enhancements on your list as well.\u00a0 This upfront knowledge allows you the flexibility to manage issues. \u00a0 If you understand the minimum MUST HAVE feature set, you can then start removing or rescheduling the “nice-to-have” items to the next release.\u00a0 Once you have removed all the “nice-to-have” items and are only left with the MUST HAVE, then you look back at your protocol recovery chart to find out what the team has agreed to do next.<\/p>\n

If you have this outlined and approved at the start of the program, then you don’t have people complaining that you are\u00a0cutting his\/her features, etc.\u00a0 This is all understood before the project starts.
\nConclusion:<\/strong>
\nA protocol recovery plan is much like a “fire escape” plan.\u00a0 It’s not something you scramble to put in place during the fire.<\/p>\n

Once again, a good project manager doesn\u2019t try to control a project.\u00a0 A good project manager adapts and manages the natural flow of things.\u00a0 The trick isn\u2019t to stay on track.\u00a0 The skill is to seamlessly get back on track when we wax and wane.<\/p>\n

The next feature will cover the idea of a critical path analysis.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

This is the second part of a three part article discussing \u201chow does a project manager intelligently handle delays in a project?\u201d <\/p>\n

Last article we focused on acknowledging the natual flow of a project which includes periodic speed bumps and roadblocks. In today\u2019s article we\u2019ll focus on using recovery protocol plans to assist with project management.<\/p>\n","protected":false},"author":1508,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"give_campaign_id":0,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[2,846,5,20,6,9,1,854,855,856,847,848,849],"tags":[195,39,51,33,64,1370,17,38],"class_list":["post-7318","post","type-post","status-publish","format-standard","hentry","category-leadership","category-scope-2","category-time-management","category-quality","category-communications","category-risk-management","category-miscellaneous","category-pmbok-process-planning","category-pmbok-process-executing","category-pmbok-process-monitoring-and-controlling","category-self-leadership","category-1-1-leadership","category-team-leadership","tag-accountability","tag-best-practices","tag-change-management","tag-common-sense","tag-communication","tag-leadership","tag-lessons-learned","tag-project-management"],"aioseo_notices":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/svapm.org\/index.php?rest_route=\/wp\/v2\/posts\/7318","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/svapm.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/svapm.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/svapm.org\/index.php?rest_route=\/wp\/v2\/users\/1508"}],"replies":[{"embeddable":true,"href":"https:\/\/svapm.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=7318"}],"version-history":[{"count":0,"href":"https:\/\/svapm.org\/index.php?rest_route=\/wp\/v2\/posts\/7318\/revisions"}],"wp:attachment":[{"href":"https:\/\/svapm.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7318"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/svapm.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7318"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/svapm.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7318"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}