Chapter 3 · Planning and Risk
Project Management and the Roles in a Software Team
- Page 8 of 18
- 18 min read
ClinicQueue now has a prioritised backlog. Nadia knows what she wants first, and the team knows what the stories mean. But a backlog does not build itself. Someone has to make sure the right people work on the right things, that the money and the time are enough, that problems are seen early, and that Nadia hears the truth about progress. That work is project management, and it is part of software engineering even when nobody has "manager" in their job title.
On the previous page, User Stories, Use Cases and Prioritising, you decided what to build first. This page is about how the team organises itself to build it: what project management balances, who does what in a software team, how a team keeps everyone informed, and what to do when the customer changes her mind. Every scenario on this page is invented.
What you will learn
- What project management is, and why scope, time, cost and quality must be balanced against each other.
- What a project manager does, and why the Scrum Guide has no project manager at all.
- The other roles in a software team: product owner or product manager, developers, tester, designer, DevOps and the customer.
- How teams communicate: stand-ups, status reports and a RACI responsibility table.
- How to handle a client who changes her mind without either refusing every change or accepting every change silently.
What project management is
A project is temporary work with a goal, a start and an end: "launch ClinicQueue v1 for the clinic" is a project; "keep the clinic's computers running" is ongoing operations. Project management is planning, organising and tracking that work so the goal is reached within the limits the customer can accept.
Four things to balance
Almost every project decision touches four quantities:
| Dimension | Meaning | ClinicQueue v1 (invented numbers) |
|---|---|---|
| Scope | What will be delivered: features, screens, documents | Online booking, SMS reminder, front-desk queue screen |
| Time | When it will be delivered | Go live in about four weeks |
| Cost | Money and effort: people, services, hosting | A fixed team of five, an SMS service paid per message |
| Quality | How well it works: correct, reliable, secure, easy to use | No double bookings; patient data kept private; Rina can read the queue at a glance |
These four are linked: if one changes, another must change too. Many books draw a triangle of scope, time and cost with quality in the middle.
Example:
SCOPE
/\
/ \ Push one corner and another one moves:
/ \ - more scope -> more time or more cost
/ \ - less time -> less scope or more cost
/ QUALITY\ - less cost -> less scope or more time
/__________\ - none of them -> quality quietly drops
TIME COSTThe trade-off in practice
At the end of the first week, Nadia asks for one more feature.
Invented scenario:
Nadia: "The other clinic in our street takes a booking fee online. Can patients pay a small
deposit when they book? Same launch date, of course."
Lena estimates the payment feature at about 6 extra working days for Farhan and Aiko,
plus testing by Kwame. The launch is about three weeks away and the plan has a small buffer.Lena does not answer "yes" or "no". She shows Nadia the options, each with its price:
| Option | What changes | Cost to Nadia |
|---|---|---|
| A. Add payment, move the date | Scope up, time up | Launch about 1.5 weeks later |
| B. Add payment, add a developer | Scope up, cost up | Extra fees, and a new person needs time to learn the code, so the date may still slip |
| C. Swap scope | Payment in, something else out | For example, the SMS reminder moves to the next release |
| D. Keep the plan | Payment marked "Won't have this time" and planned for v2 | No change now; patients pay at the desk as today |
| E. Same date, same team, add payment | Nothing visible changes | Testing gets squeezed; bugs reach patients. Lena refuses this one. |
Option E is the trap. When scope grows and nothing else is allowed to move, quality is what pays, and the time is only borrowed: it comes back later as bugs and rework. A good project lead makes that hidden cost visible instead of promising the impossible. Notice the MoSCoW wording from the previous page in option D: "Won't have this time" keeps the idea alive without breaking the plan. Nadia chose D, because a reliable launch mattered more to her than a deposit.
The project manager, and how Scrum differs
What a project manager does
In a traditional project, one person, the project manager, is answerable for delivering the project. Typical responsibilities:
- Plan: break down and estimate the work, build a schedule and budget (Planning, Estimation and Scheduling).
- Organise: who works on what; get the people, tools and accounts needed.
- Track: compare progress with the plan and act early when they drift.
- Manage changes: record each change request, assess it, get the customer's decision.
- Manage risks: spot what could go wrong and prepare (Risk Management).
- Communicate: keep the customer, team and everyone affected informed.
- Remove blockers: chase the missing password, the late decision, the unanswered email.
A project manager usually does not write the code or design it; the job is to create the conditions in which the team can.
Scrum has no project manager
As Agile, Scrum and Kanban showed, the 2020 Scrum Guide defines three accountabilities (Developers, Product Owner, Scrum Master) for a small team that manages its own work, and never mentions a project manager. The duties of a project manager do not disappear; they are shared:
| Project manager duty | Who covers it in Scrum |
|---|---|
| Decide what is built first, accept or reject scope changes | Product Owner (orders the Product Backlog) |
| Plan the work of the next few weeks, track daily progress | Developers (Sprint Planning, Daily Scrum, Sprint Backlog) |
| Remove blockers, improve how the team works | Scrum Master |
| Show progress to the customer | The whole Scrum Team at the Sprint Review |
| Budget, contracts, long-range dates | Not defined by Scrum; often the Product Owner or the organisation |
In real organisations you will see both pictures. Some companies keep a project manager next to Scrum teams for budgets and contracts; others give those duties to the Product Owner. Practitioners disagree whether the extra role helps (one person sees the whole project) or hurts (a second boss for a self-managing team). A useful test: if a project manager assigns tasks to individual developers, the team no longer manages its own work, which goes against the self-managing team the Scrum Guide describes.
For ClinicQueue, Lena is the project lead. When the team uses Scrum, she acts as Scrum Master, and Nadia makes the product decisions about priority, which is the Product Owner's job. Lena still handles the contract and the weekly report to Nadia, because a small clinic has nobody else to do it. Small teams often mix roles like this; the important thing is that everyone knows who decides what.
The other roles in a software team
A role is a set of responsibilities, not a person. One person can hold several roles, and one role can be shared.
| Role | Main responsibilities | ClinicQueue |
|---|---|---|
| Customer / client | Pays, sets the goal, accepts the result | Nadia |
| Product owner (Scrum) or product manager (job title) | Decides what is most valuable and in which order; agrees with the team what each item must achieve for users (its acceptance criteria) | Nadia decides priorities; Lena helps her write and order backlog items |
| Project manager / project lead | Plans, tracks, communicates, removes blockers | Lena |
| Developers | Design, build and fix the software; estimate their own work | Farhan (backend), Aiko (frontend) |
| Tester / QA | Plans and runs tests, reports defects, helps the team build quality in | Kwame |
| UX designer | Studies users, designs screens and flows, tests them with real people | Omar |
| DevOps / operations | Servers, deployment, monitoring, backups | No one full-time; Farhan does it with a checklist |
| Users | Use the product every day; give feedback | Dr. Rahman, Rina, patients |
Some notes on the words:
- Product owner vs product manager. "Product Owner" is a Scrum accountability. "Product manager" is a common job title in companies that build products for many customers; it often includes market research and long-term strategy. In a small client project like ClinicQueue, the person who knows the clinic best usually decides priorities.
- "Developers" in Scrum is an accountability, not a job title. As on the Agile page, ClinicQueue counts Kwame and Omar as Developers too when it uses Scrum, because they help build each Increment.
- Testers are not the only ones responsible for quality. Kwame finds problems, but developers write unit tests, Omar checks that screens are usable, and Nadia checks that the product does what the clinic needs.
- DevOps is both a way of working (developers and operations share responsibility for running the software) and a job title. Even without a DevOps engineer, someone must own deployment and backups.
- A solo freelancer holds every role except customer and user; naming them still helps ("today I am the tester").
Communication: keeping everyone informed
The team of five plus Nadia makes six people, and six people form 15 pairs who might need to talk (6 × 5 / 2). That does not work by chance, so teams use a few regular habits.
Stand-ups
A stand-up is a short daily meeting where the team synchronises. In Scrum it is the Daily Scrum; outside Scrum, many teams hold a similar daily check. The goal is to plan the next day's work and to surface blockers, not to report hours to a manager.
Example:
Weak update (Aiko): "Yesterday I worked on the booking page. Today I will keep working on it."
Useful update (Aiko): "The booking page shows free slots now. Today I connect the 'Book' button
to Farhan's API. I am blocked on one thing: the API returns times
without a time zone. Farhan, can we look at it after this meeting?"The useful update names progress, the next step, and a blocker with a person who can solve it. The blocker is discussed after the stand-up, by the people who need to be there.
Status reports
The customer does not attend stand-ups. Nadia gets a short written status report every Friday. A good status report is honest, short and the same shape every week, so Nadia can compare one week with the next.
Template:
ClinicQueue status report, week 2 Overall: AMBER
Done this week: booking API saves bookings and rejects a taken slot (milestone M1)
Planned next week: booking pages in the browser, queue screen, SMS reminder
Schedule: go live by working day 17; 1 of 3 buffer days used
Risks and issues: SMS provider needs a registration document from the clinic (2 extra days)
Decisions needed: Nadia: send the clinic registration document to Lena by Tuesday
Changes: online deposit moved to v2 ("Won't have this time"), agreed on MondayThe colour is a simple convention: green is on track, amber is at risk but under control, red means the goal cannot be met without a decision. "Decisions needed" is often the most important line: it turns a report into a request the customer can act on. The next page shows where the 3-day buffer comes from.
A RACI responsibility table
Many team problems are not technical; they are "I thought you were doing that". A RACI table (also called a responsibility assignment matrix) lists the main activities and, for each one, who is:
- R, Responsible: does the work. There can be several.
- A, Accountable: is ultimately answerable for it and signs it off. Some methods make it a rule to have exactly one A per activity.
- C, Consulted: gives input before or during the work (two-way communication).
- I, Informed: is told about the result (one-way communication).
Example:
| Activity | Nadia | Lena | Farhan | Aiko | Kwame | Omar |
|---|---|---|---|---|---|---|
| Order the product backlog | A | R | C | C | C | C |
| Design the booking screens | C | I | C | C | I | A, R |
| Build the booking API | I | I | A, R | C | C | - |
| System testing before release | I | I | C | C | A, R | C |
| Deploy to the clinic server | I | A | R | I | C | - |
| Accept the release (go live) | A | R | I | I | C | I |
Read a row left to right: for "Accept the release", Nadia is accountable (she says yes or no), Lena prepares the acceptance meeting, Kwame is consulted because he knows the open defects, and the rest are informed. Two checks find most problems: every row has exactly one A and at least one R. A person with an A on almost every row is a bottleneck; a row with five C's will be slow.
Managing stakeholders, including a client who changes her mind
A stakeholder is anyone who affects the project or is affected by it. You identified ClinicQueue's stakeholders on Requirements Engineering: Finding Out What to Build. Managing them means giving each the information and the say they need: Nadia gets the weekly report and decides; Dr. Rahman gets a ten-minute demo; Rina helps test and is trained before go live.
When the client changes her mind
Customers change their minds. Often that is good news: they learned something by seeing working software. The Agile Manifesto's principles even say "Welcome changing requirements, even late in development." Welcoming change does not mean every change is free. The skill is to make the cost of each change visible and let the customer choose.
Invented scenario:
Sprint review, week 2. Nadia sees the booking pages for the first time.
Nadia: "Patients must be able to choose their doctor. I did not think of it before."
Friday: "Actually, maybe not. Dr. Rahman says patients should just take the first free slot."
Monday: "Let us do it after all, but only for follow-up visits."Three answers in five days is frustrating, but anger does not help, and neither does silently building each version. Lena uses a repeatable process:
- Listen for the reason. Why does Nadia want this? Follow-up patients want to see the same doctor who treated them. That reason is stable even if the first wording was not.
- Write a change request. One short record, so the decision does not live only in someone's memory.
- Assess the impact on scope, time, cost and quality, with the developers' estimate.
- Present options (as in the payment example above) and let the customer decide. Lena recommends; Nadia decides.
- Record and share the decision in the backlog and the next status report. If it changes again, the record shows what was agreed and when.
Lena records it with the change request template from Requirements Engineering: Finding Out What to Build: who asked, the change, the reason, what it affects, the effort and the decision. The developers estimate one more story (2 points), about 2 extra days for Farhan and Aiko. The lines that matter for the decision are the options:
Example:
Change request CR-05 Date: 2026-10-26
Change: Patients booking a follow-up visit can choose their doctor
Options: 1) add it to v1 and move go live by 2 days
2) add it to v1 and move "Patient cancels a booking online" to v2
3) plan it for v2
Decision: Option 3, agreed by Nadia on 2026-10-27Nadia keeps online cancelling in release 1, because a patient who cancels frees the slot for someone else, and choosing a doctor is planned for v2. The whole team and Dr. Rahman are told, and the decision goes into the week 3 status report.
Practitioners differ on how formal this should be. Fixed-price contracts often need signed change requests, because every change affects money. Agile teams often treat a backlog item as the change request and let the Product Owner reorder freely. Both agree on the essentials: changes are visible, someone with authority decides, and the decision is recorded. For a freelancer, the written record is also protection.
Where this shows up at work
- "Anything blocking you?" in a stand-up: a clear, honest, early answer is one of the most valued habits in any team.
- Agencies and freelancers send weekly status reports to clients and keep a change log; disputes about money are usually disputes about scope that nobody wrote down.
- Job adverts say "project manager", "product manager", "product owner" or "Scrum Master". Read the responsibilities, not the title; they vary between companies.
Common mistakes
- Saying yes to every change without showing its cost. The customer believes the change was free, and the team pays with overtime and bugs. Fix: for each change, show the impact on scope, time, cost and quality, and offer options.
- Letting quality be the silent variable. When scope and date are both fixed, testing gets cut without anyone deciding it. Fix: say out loud which corner must move, and refuse to trade away testing.
- Turning the stand-up into a status meeting for a manager. People report hours instead of blockers, and it grows to 40 minutes. Fix: keep it short and solve problems afterwards with the right people.
- Two people accountable, or nobody. "We both thought the other one sent the document." Fix: one A per activity in a RACI table, and check it when roles change.
- Green status reports until the week of the deadline. Hiding bad news makes it worse. Fix: report amber early with a decision needed; customers forgive problems more easily than surprises.
Try it yourself
- Easy: For each duty, say who covers it in a Scrum team (Product Owner, Developers or Scrum Master): (a) ordering the Product Backlog; (b) choosing how to build a story during the sprint; (c) helping the team remove a blocker that keeps coming back; (d) deciding that the online deposit moves to a later release.
- Medium: Write a RACI row for "Write and send the SMS reminder text" for the people in the table above (Nadia, Lena, Farhan, Aiko, Kwame, Omar). Then find the problem in this row for "Choose the SMS provider": Nadia A, Lena A, Farhan R, Aiko I, Kwame I, Omar -.
- Hard: One week before go live, Nadia asks for the queue screen to also show each patient's waiting time, and she wants it "in this release, it is small". Farhan and Aiko estimate 4 working days plus 1 day of testing. The plan has 2 buffer days left. Write Lena's reply to Nadia: the impact, at least three options, a recommendation, and what will be recorded.
Answers
- (a) Product Owner. (b) Developers: they own the Sprint Backlog and decide how to do the work. (c) Scrum Master: helping the team work effectively, including getting past obstacles that keep coming back, is the Scrum Master's part. (d) Product Owner, because it is a decision about what is built and in which order; in ClinicQueue that is Nadia.
- One reasonable row for the reminder text: Nadia A (the text speaks for her clinic, so she approves it), Omar R (writes clear, friendly wording), Farhan R (puts it in the system and checks the length fits one SMS), Kwame C (tests it with real names and dates), Lena I, Aiko I. Other answers are fine if they have exactly one A, at least one R, and a reason for each letter. The problem in the provider row is two A's: Nadia and Lena are both accountable, so each may wait for the other. Fix: one A, for example Nadia A (she pays for the service) and Lena C or R (she compares providers).
- Model answer: "Nadia, the waiting-time display needs about 4 days of development and 1 day of testing, 5 days in total. We have 2 buffer days left, so adding it now would move go live by about 3 days and leave no safety margin for the launch week. Options: (1) keep the launch date and add waiting times in the first update two weeks after launch; (2) add it now and move go live by about 3 days; (3) show a simpler version now, the number of patients ahead in the queue, which Aiko estimates at 1 day, and the full waiting time later. I recommend option 3: patients get useful information at launch and we keep a buffer. I will record your decision as a change request and include it in Friday's status report." A good answer contains: the arithmetic (5 days needed versus 2 available, so about 3 days over); at least three real options that move different corners (time, scope, a smaller version); no option that cuts testing; a clear recommendation with a reason; the decision left to Nadia; and a written record.
Summary
- Project management balances scope, time, cost and quality; changing one forces another to change, and quality is the corner that must not move silently.
- A project manager plans, organises, tracks, manages changes and risks, communicates and removes blockers.
- The 2020 Scrum Guide has three accountabilities (Developers, Product Owner, Scrum Master) and no project manager; the project manager's duties are shared among them.
- Other roles include the customer, product owner or manager, developers, tester, designer, DevOps and users; one person can hold several roles.
- Stand-ups, honest weekly status reports and a RACI table with one A per activity keep everyone informed; changes from the client are welcomed, assessed, decided by the client and recorded.
Next: Planning, Estimation and Scheduling: how Lena breaks ClinicQueue into tasks, estimates them, and works out which tasks decide the launch date.

