Every active engagement at Devotion Technologies runs on a weekly rhythm: a working demo, a short review, and a clear plan for the week ahead. This article walks through what happens in each session, what we need from you, and how to get the most out of the time.
Applies to: Fixed-scope and time & materials engagements with an assigned delivery pod. Single-specialist placements follow a lighter version of this process — ask your project manager for specifics.
What happens in a weekly demo
Demos are held at the end of every sprint and run for 30 to 45 minutes. Rather than a slide deck, the team walks through the actual working software — a feature, an API endpoint, or an infrastructure change — running in a staging environment you can access yourself.
- The engineer who built the feature walks it through live, not a project manager relaying it secondhand.
- You can interact with what's shown, not just watch a recording.
- Anything not finished is flagged honestly, along with what moved it.
Before the call: what to prepare
A few minutes of preparation on your side makes the session far more useful for both teams.
- Review the sprint board. Tickets marked "Ready for review" are what will be demoed — skim titles beforehand so nothing is a surprise.
- Note open questions. Drop them in the shared channel ahead of time if they need research, so the answer isn't rushed live.
- Have a stakeholder present. If a decision needs sign-off, the person who can actually approve it should be on the call.
The sprint review that follows
Immediately after the demo, we run a short review covering three things: what got done against what was planned, anything that's blocked, and the priorities for the coming week. This is also where scope changes are raised — never silently absorbed into the existing sprint.
If a scope change comes up
Any request that falls outside the original proposal is scoped and quoted before it's added to a sprint. This keeps timelines and budgets predictable, and means nothing is billed without you seeing it coming first.
Tip: If you already know a change is coming, mention it a sprint early. It gives the team time to sequence work around it instead of interrupting one already in progress.
After the call
Within a few hours, your project manager shares a short written recap: what was demoed, decisions made, and what's planned for the next sprint. Nothing discussed live is left to memory — if it mattered, it's written down.
Was this article helpful?
Thanks — a note has been sent to our documentation team.