Handling Automation Projects: Scope, Critical Path and Changes
Plan an automation project with tasks, dependencies and slack, find the critical path, convert it to dates and price a change request by its real effect.
In this lesson you will
- Write a scope with an in and an out list
- Find the critical path and slack
- Turn project days into calendar dates
- Handle a change request step by step
About 25 minutes
“Just one small addition”
Ravi has agreed to build the enquiry assistant for his friend’s accountancy. Halfway through, she says, ‘Could it also look up the status of a client’s file? Just a small addition.’ It sounds small. But the lookup is the longest part of the project, and the two tasks that depend on it cannot start until it finishes. A ‘small’ change lands on the one task where delay hurts most. This is why professional projects use two simple tools: a map of what depends on what, and a way to see which tasks have no slack.
Scope first
A project goes wrong most often at its edges. Write the scope as a short list of what you will deliver, and a short list of what you will not. ‘An assistant that answers questions from twelve agreed notes and hands the rest to a person’ is a scope. ‘An assistant for the office’ is a wish. When the client asks for something outside the list, that is not a problem. It is a change request, and you handle it with a clear question: what does it cost in time and in money?
Dependencies and the critical path
Break the project into tasks with a length in days, and write down which tasks must finish before another can start. The chain of tasks that sets the earliest possible finish is the critical path. A delay on that chain delays the whole project. Every other task has some slack, which is the number of days it can slip without moving the finish. The program below holds eight tasks with made-up lengths, works out the earliest and latest start of each, finds the critical path and the slack, and converts the length into a date, counting working days from Monday the 16th of November 2026. Then it applies the change request.
import networkx as nx
import numpy as np
tasks = { # name: (days, depends on)
"scope": (2, []), "map": (3, ["scope"]), "intake": (4, ["map"]), "lookup": (5, ["map"]),
"checks": (3, ["intake", "lookup"]), "testset": (3, ["map"]),
"evaluate": (2, ["checks", "testset"]), "handover": (2, ["evaluate"]),
}
def plan(tasks):
g = nx.DiGraph()
for t, (d, deps) in tasks.items():
g.add_node(t, d=d)
for x in deps:
g.add_edge(x, t)
early, late = {}, {}
order = list(nx.topological_sort(g))
for t in order:
early[t] = max([early[x] + tasks[x][0] for x in g.predecessors(t)], default=0)
end = max(early[t] + tasks[t][0] for t in order)
for t in reversed(order):
late[t] = min([late[x] for x in g.successors(t)], default=end) - tasks[t][0]
slack = {t: late[t] - early[t] for t in order}
return end, [t for t in order if slack[t] == 0], slack
def finish(days):
return str(np.busday_offset("2026-11-16", days - 1, roll="forward"))
end, crit, slack = plan(tasks)
print("project days:", end)
print("critical tasks:", crit)
print("slack: intake", slack["intake"], "| testset", slack["testset"])
print("starts Mon 16 Nov, last day:", finish(end))
tasks["lookup"] = (8, ["map"]) # a change request: richer lookup
end2, crit2, slack2 = plan(tasks)
print("after the change, days:", end2)
print("last day now:", finish(end2))
print("intake slack now:", slack2["intake"])
project days: 17
critical tasks: ['scope', 'map', 'lookup', 'checks', 'evaluate', 'handover']
slack: intake 1 | testset 5
starts Mon 16 Nov, last day: 2026-12-08
after the change, days: 20
last day now: 2026-12-11
intake slack now: 4
The project takes 17 working days. The critical path is: scope, map, lookup, checks, evaluate, handover. The testing set task has 5 days of slack, so it can slip a full week without any effect, and the intake task has 1 day. Starting on Monday 16 November, the last working day is Tue 8 Dec. Now the change request. Making the lookup richer lengthens it from 5 days to 8, and because lookup is on the critical path, the whole project grows to 20 days and the last day moves to Fri 11 Dec. Notice that the intake task, which had 1 day of slack, now has 4: the longer lookup gives other branches more room, while the end date still moves. The change is real work that cost the client three working days.
How to handle a change request
- Write the request down in the client’s words.
- Work out which tasks it adds or lengthens, and whether they are on the critical path.
- State the effect on the finish date and on the fee, using the same method as the original quote.
- Let the client choose: accept the new date and fee, swap it for something else or drop it.
- Record the decision, and update the plan, so everyone works from the same one.
Keeping a project healthy
- Review the plan weekly and look first at the critical tasks.
- Tell the client early about any slip. Bad news gets worse the longer it waits.
- Use slack deliberately. A task with spare days can absorb a delay elsewhere, if you start it later.
- Test with saved examples before hand-over, as in lesson 24, and agree the hand-over checklist at the start.
- Agree who will look after the workflow afterwards, as in lesson 28.
Saying yes to small additions without checking the plan. A tiny change on the critical path moves the end date, however small it sounds.
The tasks, lengths and dates are made up for teaching. The dates are real calendar dates for 2026, counting only working days and ignoring public holidays, which differ by country, so check yours. Contract and change terms are outlines, not legal advice.
Practice for this lesson
Check what you learned
Five quick questions. Pick an answer and you will see straight away whether it is right and why.
What is the critical path?
- The most expensive tasks
- The first task only
- The tasks nobody likes
- The chain of tasks that sets the earliest finish
A delay on it delays the whole project.
What is slack?
- Time lost to meetings
- Days a task can slip without moving the finish
- A kind of fee
- A missing task
The testing set task had five days of it.
Why did the change request move the end date?
- The client paid late
- Testing was removed
- The lookup task is on the critical path
- Weekends were added
Making lookup longer lengthened the longest chain.
What is the first thing to do with a request outside the scope?
- Treat it as a change request and work out its time and cost
- Say yes at once
- Ignore it
- Delete the plan
A clear question about time and money keeps trust.
Why tell the client early about a slip?
- Clients enjoy surprises
- It avoids tests
- Bad news gets worse the longer it waits
- It lowers the fee
Early warning leaves room to choose.
Summary
- Scope is a list of what you will and will not deliver.
- The critical path sets the finish; other tasks have slack.
- A change on the critical path moves the end date.
- Treat extras as change requests with time and cost.
Questions
Do I need project software for this?
No. A table with task, days and dependencies works. The program shows the calculation behind the charts that tools draw.
What if the client refuses to pay for a change?
Then the scope stays as agreed. Having the scope and the change process in writing from the start makes this conversation easier.
Are the dates real?
The dates are real 2026 calendar dates counting working days only. The tasks and lengths are made up.
