How We Run Discovery Sprints in Five Working Days — Lessons From Delivery

Field notes from Shriram IT Ventures delivery work on How We Run Discovery Sprints in Five Working Days: the constraints that matter, the shortcuts that haunt you, and a checklist we still use.

Who this is for

Teams that write trade-offs down before coding burn fewer sprints when a stakeholder changes their mind mid-build. We keep ADRs short on purpose.

Decisions that still look smart in 18 months

Use boring technology where the risk is operational. Save novelty for the one wedge that makes the product worth buying.

Build checklist we actually use

Use boring technology where the risk is operational. Save novelty for the one wedge that makes the product worth buying.

Failure modes we keep seeing

Teams that write trade-offs down before coding burn fewer sprints when a stakeholder changes their mind mid-build. We keep ADRs short on purpose.

How we measure rollout

Ignore the buzzwords. For How We Run Discovery Sprints in Five Working Days, the hard constraint is usually data ownership or ops capacity — not how many features fit on a roadmap slide.

We update this when delivery patterns change on live client work.