1. What?
• Quick run over the client brief to ensure
everyone is on the same page, and there's no
new requirements.

2. Why?
• KPI’s
• Overall acceptance criteria not in KPI’s
• Any examples or similar projects?

3. Gather?
• Take top line ‘epics’, initial ideas
• Work with stakeholders to create smaller user stories
(not formal user story workshop, but more a way to
really elicit as many requirements as possible)
• Try to elicit as many specifics as possible i.e ‘certain
locations – which locations exactly as they may not
have good 3G’
• For each ‘story’ briefly discuss what success looks like /
acceptance criteria etc.
• Risk mitigation.
• Take the opportunity to add additional ideas

4. Estimate
• Make top line assumptions around requirements
for initial cost estimate
• Take the general requirements, and if possible
from experience come up with an approach,
focussing on each user story / epic / single
requirement if required, suggest potential
platforms (such as punchtab for gamification,
titanium for mobile build).
• Propose ballparks costs if possible else discuss
with team.

5. Usuals
• Estimated traffic and hosting
• Testing percentage
• Tech oversight percentage

6. Next steps
• Client sign of on estimate and rough proposal
-> full scoping and refined estimate and
technical approach.