{"id":988605,"date":"2026-10-03T14:00:00","date_gmt":"2026-10-03T14:00:00","guid":{"rendered":"https:\/\/croncodestudio.com\/en\/?post_type=croncode_post&p=988605"},"modified":"2026-09-08T22:58:43","modified_gmt":"2026-09-08T22:58:43","slug":"what-a-sprint-demo-should-show-a-client","status":"publish","type":"croncode_post","link":"https:\/\/croncodestudio.com\/en\/journal\/what-a-sprint-demo-should-show-a-client\/","title":{"rendered":"What a Sprint Demo Should Show a Client"},"content":{"rendered":"
\n

A sprint demo is a shared look at software that exists. If the only artifact is a slide, you had a status meeting. At Croncode<\/a> we demo a TestFlight (or a staging URL) that a client can tap after the call. The point is not theater. The point is to agree what shipped, what failed, and what stays on the not-now list. Engineering sits in Istanbul. The LLC that can sign sits in Albuquerque.<\/p>\n

\n

A sprint demo should show a build the client can hold, the first job completed, one failed path, and what is not in the increment. A deck without a binary is a status meeting.<\/p>\n<\/blockquote>\n

What is the minimum demo script?<\/h2>\n
    \n
  1. Name the build number and who can install it.<\/li>\n
  2. Finish the first job once, live, on a small phone if you can.<\/li>\n
  3. Trigger one error or empty state on purpose.<\/li>\n
  4. Show the written not-now items you refused this week.<\/li>\n
  5. Name the next increment in one sentence.<\/li>\n<\/ol>\n

    Design QA should already have a pass: design QA<\/a>. Process choice lives outside the demo: fixed scope vs agile<\/a>. Sequence: idea to App Store<\/a>.<\/p>\n

    Which artifacts waste the hour?<\/h2>\n\n\n\n\n\n\n\n\n
    Artifact<\/th>\nUse<\/th>\nSkip<\/th>\n<\/tr>\n<\/thead>\n
    TestFlight<\/td>\nAlways for iOS<\/td>\nNever if a binary exists<\/td>\n<\/tr>\n
    Figma<\/td>\nTo compare a future increment<\/td>\nAs a substitute for the build<\/td>\n<\/tr>\n
    Burn-down chart<\/td>\nIf the contract is agile hours<\/td>\nIf it hides a missing job<\/td>\n<\/tr>\n
    Competitor video<\/td>\nTo name a job they fail<\/td>\nAs a promise you will copy. Teardowns<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    If the increment is a paywall, show StoreKit, not a picture: honest paywalls<\/a>. If it is an AI path, show timeout and retry: fail-safe AI<\/a>.<\/p>\n

    When should the client speak?<\/h2>\n

    After the job, not during the first tap path. Ask: can a stranger finish this without us on the call. Ask: which not-now item they want to fight for. Do not take a new epic in the last five minutes without writing the cost. Feature creep: feature creep<\/a>.<\/p>\n

    People on our side of the call: Goktug Unver<\/a>, Yusufhan Sokur<\/a>, Ozgur Ismet Ozkan<\/a>. Dual-track weeks: products and client software<\/a>.<\/p>\n

    How do consumer apps change the demo?<\/h2>\n

    Show the job, not a studio reel. Closet: save a garment and build a look. Decision: structure one choice. Case: follow one clue. Journey: confirm one window. Those products: YourStyle<\/a>, Numira<\/a>, Spylie<\/a>, Luviport<\/a>. We do not demo fake rankings.<\/p>\n

    What we build: what Croncode builds<\/a>. How we ship: Istanbul shipping<\/a>.<\/p>\n

    What mistakes turn demos into theater?<\/h2>\n