UPI Study › Courses › Project Management › Free lessons › Lesson 8.5 Free with a free account
Handling Incomplete Tasks: Consequences and Recovery
Project Management · Chapter 8: Driving Project ExecutionSection 8.5 · lesson 48 of 7315 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Project Management.
Lesson complete
Earn the 3 college credits for Project Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Quality Management Processes and Performance Metrics →← Defining and Tracking Milestones in Active ProjectsNext lesson: Quality Management Processes and Performance Metrics →
In this lesson
Diagnosing why tasks stall and choosing a recovery that fits the cause.
- Identify the four common causes of incomplete tasks
- Judge a delay's effect on the finish date using the critical path and float
- Compare re-planning, adding capacity, descoping, compression and escalation along with their costs
- Prevent stalled tasks with right-sized work and a written definition of done
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (2,143 words). Read along, or search it.
Opening Case
Ninety Percent Complete for Two Weeks
For two weeks, one task has read ninety percent complete. Is it nearly done? Priya, a project manager at Willowbrook Community Clinics, a made-up clinic network, is opening a new clinic. Doors open at the start of working day thirty-one. The exam-room fit-out was due to finish on day ten. It's now day twenty, and the fit-out still reads ninety percent. Until it's done, the commissioning work can't begin: a practice clinic day, stocking, and a final readiness check, nine working days in all. Sam, the fit-out lead, says it's almost there. What should Priya do? By the end of this lesson, you'll know what she found, and what she chose.
Definition
Three Kinds of Unfinished Work
First, be exact about what counts as unfinished. A task has a planned start, a planned finish, and an agreed finished state. An incomplete task hasn't reached its agreed finished state when the plan said it would. That covers three situations. Work past its planned finish, openly still running. Everyone can see it, and the only question is how much longer it'll really take. Work reported as nearly done, but not verifiably done, like a task sitting at ninety percent. The last tenth often holds the least visible steps: testing, correcting, and getting approval. And work left half-finished when priorities shift. It may not look late at all, until some other task needs its output. The second and third are the dangerous ones, because they don't announce themselves.
Root Causes
Four Causes Behind Incomplete Tasks
Unfinished work looks the same on a status report, whatever caused it. But the right response depends on the cause, and four cover most cases. Estimate error: the plan assumed less work than the task needs. Repainting sixty waiting-room benches was planned at three days, counting only painting. With scraping, sanding and drying, it needs seven. A resource gap: the people, skills or equipment aren't there when needed. Moving records needs an analyst two days a week, but she's shared with billing, and free for only one. A dependency delay: work can't proceed because an input from someone else hasn't arrived. The wiring crew is ready, but the landlord returned the approved floor plan five days late. And rework: finished work must be redone. Forty direction signs were printed and marked complete, then two room numbers turned out wrong. Rework is especially damaging, because it makes a task that was counted as finished unfinished again.
Diagnosis
Plain Questions That Separate the Causes
Plain questions tell them apart. Is the remaining work bigger than the plan assumed? Estimate error. Is the work the right size, but nobody qualified is free? A resource gap. Is the team ready, but waiting for something? A dependency delay. Is finished work being done again? Rework. Real situations mix causes, so find the dominant one. A recovery chosen for the wrong cause wastes money and time. Adding people to a task that's waiting on a missing floor plan only adds people who wait.
Quick Check
Dense Pages Double the Translation Time
Quick check. A translation team estimated twelve days from the page count. But the pages are dense with technical tables, and each one takes twice as long as planned. The translators are available, and nothing is missing. Which cause is it? Pause, and decide. Estimate error. The people are there and the inputs are there, but the work is bigger than the plan assumed. So the remedy has to change the estimate. Pushing the translators harder can't fit twenty-four days of work into twelve.
Schedule Impact
Critical Path, Float and Late Tasks
What a late task does to the finish date depends on where it sits. The critical path is the longest chain of dependent activities, and it fixes the earliest possible finish. Float is how long an activity can slip without moving that finish. Take a made-up project finishing on working day sixty. A three-day delay to critical activity A, with no float, moves the finish to day sixty-three. The same three days on activity B, with five days of float, leaves the finish at sixty. But B has now used three of its five days. A seven-day delay on B would move the finish to day sixty-two. So a non-critical delay isn't harmless. Several small delays can eat a path's float until it becomes critical. Judge each delay against the float that remains.
Hidden Costs
Effects on Cost, Quality, Morale and Credibility
Incomplete work hits more than the calendar. On cost, people stay on the payroll longer, and anything that costs by the day, like equipment hire, keeps running. On quality, the big temptation is to cut quality to appear finished: skip the last test, or the approval step, so the report shows done. The defects haven't gone away. They've moved forward in time, and usually grow more expensive, as rework or a customer complaint. A visible delay has become a hidden defect. On morale, repeated late work brings overtime, blame, and reluctance to report bad news. People punished for saying a task is behind will report it as nearly done. And on credibility, once the schedule isn't believed, people keep private buffers and discount every report. It's rebuilt by reporting honestly and early, and making recovered dates come true.
Option One
Re-Planning From the Actual Rate
Now the recovery options. The first is re-planning: rewriting the plan for the remaining work, using how the work has actually been going. It's cheap and honest, and every other option needs its realistic estimate. Take some made-up numbers: Elena's team must pack two hundred welcome kits for the opening. The plan allowed four days: fifty kits a day. After five days, a hundred and twenty are packed, so the task is already a day past its planned finish. The actual rate is a hundred and twenty over five: twenty-four kits a day. Eighty kits remain. The old plan implied eighty over fifty: one point six days. The realistic need is eighty over twenty-four: three point three three days, about one point seven three days later. The actual rate is less than half the plan, so the estimate itself was at fault. A re-plan doesn't approve a new official date, and it recovers no time.
Option Two
Adding a Second Packer
Option two is reassigning work, or adding capacity: extra people, hours, or equipment. Both address a resource gap directly. Their cost isn't just wages. A newcomer must be briefed, the original worker answers questions, and more people need more coordination. Say a second packer joins, after half a day of briefing. During that half day, the first packer does twelve kits, leaving sixty-eight. Together they pack forty-eight a day, so sixty-eight take about one point four two days. The remaining time falls from three point three three days to one point nine two. At two hundred dollars per person-day, labor rises from about six hundred sixty-seven dollars to seven hundred sixty-seven. A hundred dollars buys about one point four days. Adding people works when the work divides cleanly and the newcomers are already skilled. It helps little when the work is sequential, or depends on one person's knowledge.
Option Three
Descoping the Neighborhood Map
Option three is descoping: reducing what's delivered, by removing, simplifying or deferring part of it, so the rest fits the time and money left. Suppose the printed neighborhood map in each kit takes a quarter of the packing time. Without it, the rate rises to thirty-two kits a day. Eighty kits then take two and a half days, saving about point eight three days, at no extra spend. The trade-off: patients get less than was promised. So the decision belongs to whoever owns the scope, usually the sponsor or customer, not the people doing the work. And descoping isn't a quality cut. Descoping openly decides to deliver less, and tells the people affected. A quality cut delivers the full list on paper, with the checking quietly removed.
Option Four
Crashing and Fast Tracking
Option four is compression: shortening the remaining schedule without changing scope. It's only useful on the critical path, and it's applied to the activities after the stalled one. Crashing buys time with money, priced per day saved. Say installing the check-in system normally takes five days for two thousand dollars. Overtime and a second crew cut it to three days for twenty-eight hundred. That's eight hundred dollars for two days: four hundred dollars per day saved. Fast tracking overlaps tasks planned in sequence. It costs little money, but adds risk: if the earlier output changes, the later work must be redone. Whenever compression is proposed, name the added cost for crashing, and the added risk for fast tracking.
Option Five
Escalating With Options and a Recommendation
Option five is escalation: passing the problem to someone with more authority, usually the sponsor. Here that's Helen, the network director, who funds the project. Escalate when the recovery lies outside your delegated authority: it overspends the agreed tolerance, trades scope against date, or needs another manager's people. Escalating isn't failure. Escalating late is, and so is escalating with no options. A useful escalation gives the task, the cause, the effect on finish and cost, the options, and a recommendation. And a recovery step needs a formal change request when it changes the approved scope, schedule or budget: re-planning that moves the official finish, descoping a deliverable, or crashing past the budget. A reassignment inside the existing budget and dates usually doesn't. A change made informally removes the record that explains why the project drifted.
Choosing a Recovery
Matching the Option to the Cause
No option is free. So the choice starts with the cause. A resource gap points to reassigning or adding capacity. An estimate error points to re-planning. A dependency delay points to escalation, or compressing later work. Rework points to fixing the defect's cause first. Before choosing, ask whether the task is on the critical path, so you don't buy time the float already covers. After choosing, ask who must approve it. Then tell everyone affected. Which constraint should give way first is contested. One side protects scope: a smaller deliverable may not meet the need, and cut items cost more to add back later. The other protects time and cost: some dates are fixed, and delivering the most valuable parts on time serves people better. That's for the sponsor's priorities to decide.
Quick Check
A Crew Idle Waiting for Parts
Quick check. A wiring task is waiting for parts the supplier hasn't delivered. The crew is ready, and idle. Which recovery fits best? Pause, and decide. Raise it with Helen. This is a dependency delay, so extra effort can't supply the missing parts. A sponsor can press the supplier, or approve an alternative. More crew would only add people who wait. And the estimate isn't wrong: once the parts arrive, the work is the size the plan said. Compressing later work is the other sound move.
Prevention
Right-Sizing and a Definition of Done
Recovery is expensive, and much of it can be prevented. Right-sizing breaks work into tasks small enough to finish and check within a few days, or one reporting period. A two-day task can't hide at ninety percent for two weeks. A definition of done states, in writing, what must be true before a task may be called finished: checks passed, approvals obtained, output handed over. For the kits: two hundred packed, the count confirmed by a second person, boxes labeled and moved to the loading area. Nearly done becomes a yes-or-no question. Early warning signs show trouble before a task is formally late: repeated ninety-percent reports, a growing to-do list, a dependency chased again and again, rising overtime, vague answers, and items reopened. When one appears, stop asking what percent is done. Ask what exactly remains, and who's doing it this week.
Case Resolved
A Second Inspector Saves Opening Day
Back to Priya and the fit-out stuck at ninety percent. She stops asking for a percentage, and asks Sam for a list of what remains. It holds one item: an electrical safety inspection of the exam rooms. Only one qualified inspector is booked, and she's on another site until day twenty-five. So the cause is a resource gap, hidden by a missing definition of done. The rooms were finished without the inspection counted as part of the task. The original plan ended on day nineteen: fit-out by day ten, plus nine days. With doors opening on day thirty-one, that left eleven days of float. Waiting for the inspector ends the chain on day thirty-four, four days past opening. Re-planning alone would just accept that. Skipping the inspection would cut quality on a safety item, so that's out. She adds capacity: a second qualified inspector, at a nine-hundred-dollar premium, who can inspect on day twenty-one. The chain now ends on day thirty, with zero float. The cost fits the reserve Helen delegated to her, so no change request is needed. But she tells Helen about the spend, and that any further slip now reaches opening day.
Key Takeaways
Ask What Remains, Then Choose
To recap: when a task stalls, ask what exactly remains, not what percent is done. Name the cause, estimate error, resource gap, dependency delay or rework, before choosing a recovery. Check the float before buying time, because only critical delays move the finish. Every option, re-plan, capacity, descope, compress or escalate, costs something, so state the cost. And prevent the next stall with right-sized tasks and a written definition of done.
About Project Management at UPI Study
Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Why take it here
Why students take Project Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Handling Incomplete Tasks: Consequences and Recovery
What are the main causes of incomplete project tasks?
Does a delayed task always move the project finish date?
What is the difference between descoping and cutting quality?
What is a definition of done and how does it prevent stalled tasks?
About the Project Management course
How many college credits is Project Management?
How much does Project Management cost and what is included?
Which universities accept UPI Study credits?
How long does Project Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Project Management.
73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →