Guides for consultancies, coaches, and trainers
Practical answers for firms that assess other people’s backlogs: baselining a client backlog so the findings hold up, presenting hard findings, pricing the work, and keeping fixed-bid engagements profitable.
Running client assessments
What's in the report I deliver to a client?
The white-labeled backlog assessment report, section by section, with the real sample PDF as the reference: what each section shows, why it is there in a coaching or training engagement, what you can change, and what the client receives.
How do I audit a client backlog?
The baseline assessment a consultancy, coach, or trainer runs at the start of an engagement: what to ask for, why to score every story instead of sampling, how to package the findings as a deliverable, and how to re-score to show the change.
How do I present requirements findings to a client?
How a coach or consultant delivers hard findings about a client's backlog with the product owner in the room: rest on a stated standard, lead with aggregates, anonymize authors, pair every problem with a rewrite, and close on the re-score.
What does a low-scoring story actually cost?
One story from vague to shipped defect: what a story that looks ready hides, what scoring flags in it, and who pays when nobody acts. The guide to send a product owner who says the team has always worked this way, and the pre-read for a definition-of-ready workshop.
How do I audit a backlog when the project is already slipping?
The mid-flight assessment, where the room is already taking sides: score what remains rather than re-litigating delivered sprints, split the slip into named causes a neutral engine can back, and turn the findings into a quality gate and a re-baselined date.
Selling backlog assessments
How do I price a backlog audit?
Pricing a backlog assessment as a productized service for consultancies and training firms: fixed-fee tiers by backlog size, a diagnostic, a workshop tier, and a measured-engagement tier, anchored against the spend the assessment de-risks and proves.
How do I protect fixed-bid margins from scope creep?
The delivery lane: scope creep on fixed-bid work starts in the requirements, not the change requests. How agencies, dev shops, and consultancies that take fixed-fee work catch vague, oversized stories before signing, and put evidence behind every scope conversation.
How do I estimate work from a backlog I didn't write?
Split an inherited backlog three ways before you plan or price from it: what you can size, what needs one question answered, and what cannot be sized as written. How a PMO consultant or delivery lead forecasts each bucket and presents the split as rigour rather than hedging.
New to the program?
Start with how a project works to see the engagement flow end to end, or read the setup and workflow reference for concepts, credits, and uploads.