Clarify project coordination, product value and Scrum effectiveness through a retail delivery-app case, with practical decisions, handoffs and role-conflict scenarios.
This guide explains the accountabilities and their interfaces in an organisation that has both a wider project and a Scrum Team. Actual spending and governance authority must be agreed in the organisation rather than inferred from a title.
Start with the work to be owned
A job title needs a clear responsibility and decision boundary. Use a running example to make the responsibilities visible. Different goals should connect rather than compete. The person who coordinates the project does not automatically order the Product Backlog.
The project manager surfaces constraints, dependencies and commitment implications. They help route investment or scope decisions beyond delegated authority.
Who plans the work?
A high-level integration plan and a Sprint delivery plan serve different decisions. A team needs clarity without losing its ability to organise the work. Several roles can interact with stakeholders while serving different purposes. The route depends on the problem, its impact and who can act.
The project manager handles relevant project issues within authority and escalates where necessary. Product trade-offs still need the Product Owner and Developers as appropriate.
Budget and commercial authority
Scrum accountabilities do not by themselves define every funding or contracting right. One request can affect both product work and a controlled commitment. A coordination deadline cannot redefine an unfinished result as usable. Useful reporting connects evidence with the next decision.
Combine component readiness, supplier commitments, cost, risks and integrated forecasts. Keep status dates and definitions consistent across the view.
Can one person hold two roles?
Combining responsibilities needs explicit capacity and conflict checks. Write the decisions the people need to coordinate. Use accountabilities and evidence to choose a response. Use the responsibilities to clarify tomorrow’s work.
A clear arrangement lets the delivery-app team learn while store operations, suppliers and funding remain coordinated. The roles support related decisions without quietly overriding each other.
Contents
- Start with the work to be owned
- One delivery-app initiative
- Objectives and goals
- Value and priority decisions
- Who plans the work?
- Task assignment and self-management
- Stakeholder engagement
- Impediments and issues
- Budget and commercial authority
- Change requests and backlog changes
- Quality and Done
- Reporting and forecasts
- Can one person hold two roles?
- Build a responsibility agreement
- Resolve a role-conflict scenario
- Your role compass
Using the PDF
Each numbered page contains an explanation, an original worked situation and a practical action. The bookmarks navigate the learning pages. A templates advertisement follows content page 5 and a Coursera Plus advertisement follows content page 15. The entire advertisement image is linked. Promotional links may earn Coursya a commission. A purchase is optional.
Frequently asked questions
Which decisions does the retail delivery-app case examine?
The case separates project coordination, product value and Scrum Team effectiveness. It follows decisions about planned work, dependencies and spending authority across the three roles.
How many pages are in the ebook?
The ebook contains 19 pages.
How can I download the ebook?
Use the download button on this page to open the ebook and save a copy.


