{"id":14,"date":"2025-12-08T12:09:45","date_gmt":"2025-12-08T12:09:45","guid":{"rendered":"https:\/\/steadyrabbit.in\/blogs\/?p=14"},"modified":"2025-12-09T10:45:58","modified_gmt":"2025-12-09T10:45:58","slug":"plan-left-code-left-measure-left-a-sprint-by-sprint-guide-to-real-shift-left","status":"publish","type":"post","link":"https:\/\/steadyrabbit.in\/blogs\/plan-left-code-left-measure-left-a-sprint-by-sprint-guide-to-real-shift-left\/","title":{"rendered":"Plan-Left, Code-Left, Measure-Left: A Sprint-by-Sprint Guide to Real Shift-Left"},"content":{"rendered":"\n

Ship predictably by moving planning, testing and metrics to the very start of every iteration.<\/p>\n\n\n\n

\u201cShift-Left\u201d dies in committees when it means \u201cQA starts earlier.\u201d Real shift-left moves planning<\/strong>, testing<\/strong>, metrics<\/strong>, and risk gates<\/strong> to the very start of every sprint. In this deep dive we unpack the Plan-Left \u2192 Code-Left \u2192 Measure-Left<\/em> triangle we use inside every Micro-GCC squad to hit 95-100 % schedule adherence across 40+ engagements.
<\/p>\n\n\n\n

Why \u201cQA Earlier\u201d<\/strong><\/p>\n\n\n\n

Teams add a tester during backlog grooming and call it shift-left\u2014then wonder why releases still burn. The reason: only one<\/strong> of four failure modes happens in QA. The rest hide in unclear requirements, un-observed code, and lagging metrics.<\/p>\n\n\n\n

Four failure roots<\/strong>
<\/p>\n\n\n\n

    \n
  1. Ambiguous requirements (Plan)
    <\/li>\n\n\n\n
  2. Implicit code paths (Code)
    <\/li>\n\n\n\n
  3. Late feedback loops (Measure)
    <\/li>\n\n\n\n
  4. Defects in QA (classic)<\/li>\n<\/ol>\n\n\n\n

    Shift-left that fixes only #4 reduces rework ~15 %. Tackle all four and rework plummets 40-60 %.
    <\/p>\n\n\n\n

    Artifacts you need before sprint kickoff
    <\/strong><\/p>\n\n\n\n

    Artifact<\/strong><\/td>Purpose<\/strong><\/td>Owner<\/strong><\/td><\/tr>
    Risk Matrix<\/strong><\/td>Ranks user stories by business & tech risk<\/td>Squad Lead<\/td><\/tr>
    Definition of Ready (DoR)<\/strong><\/td>8-point checklist (persona, acceptance tests, perf NFR, risk)<\/td>Product Lead<\/td><\/tr>
    Architecture Spike<\/strong><\/td>2-hour whiteboard or Mermaid diagram<\/td>Tech Lead<\/td><\/tr>
    Capacity Forecast<\/strong><\/td>SteadCAST auto-pulls PTO, velocity deltas<\/td>Delivery Lead<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    How to implement:<\/em><\/p>\n\n\n\n

      \n
    • Add a Plan-Left column<\/strong> to the sprint board. No card moves to \u201cIn-Progress\u201d until DoR \u2713.
      <\/li>\n\n\n\n
    • Risk Matrix auto-expands into Jira labels (\u201crisk-high\u201d, \u201cperf-critical\u201d).
      <\/li>\n\n\n\n
    • Capacity Forecast posts a Slack alert if velocity dips > 15 %.
      <\/li>\n<\/ul>\n\n\n\n

      Code-Left: GenAI Tests & SBOM on Every PR (420 w)<\/strong><\/h4>\n\n\n\n
        \n
      1. GenAI Unit-Test Scaffolds<\/strong>
        <\/strong>\n
          \n
        • GitHub Action calls our test-writer (> 80 % line coverage).
          <\/li>\n\n\n\n
        • Developer reviews, tweaks, commits in same PR.
          <\/li>\n<\/ul>\n<\/li>\n\n\n\n
        • Static Analysis Gates<\/strong>
          <\/strong>\n
            \n
          • ESLint \/ golangci-lint fail fast.
            <\/li>\n<\/ul>\n<\/li>\n\n\n\n
          • SBOM Generation<\/strong>
            <\/strong>\n
              \n
            • CycloneDX JSON artifact persists to S3; hash posted to PR.
              <\/li>\n<\/ul>\n<\/li>\n\n\n\n
            • Peer Review \u2194 Pair Review<\/strong>
              <\/strong>\n
                \n
              • Risk-high stories trigger 2-reviewer rule; others 1.
                <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

                Tip:<\/strong> hide GenAI test noise\u2014diff-filter *-gen.test.js by default; reviewers focus on logic, not snapshots.
                <\/p>\n\n\n\n

                Measure-Left: Leading Indicators in the Same Sprint (280 w)<\/strong><\/h4>\n\n\n\n

                Traditional metrics (velocity, escaped-defects) report too late. We track lead indicators<\/strong> that warn two sprints ahead:<\/p>\n\n\n\n

                Indicator<\/strong><\/td>Target<\/strong><\/td>Why it Matters<\/strong><\/td><\/tr>
                Risk-High WIP %<\/strong><\/td>< 25 % of sprint cards<\/td>Too many risk stories = schedule slip<\/td><\/tr>
                Time-to-First-Review<\/strong><\/td>< 2 h<\/td>Long waits \u2192 merge pile-ups<\/td><\/tr>
                Test Coverage \u0394<\/strong><\/td>+2 % each sprint until 80 %<\/td>Plateau early? Tech debt rising<\/td><\/tr>
                SBOM Build Time Penalty<\/strong><\/td>< 5 % of total CI time<\/td>Large \u0394 means dependency bloat<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                SteadCAST posts a Friday dashboard; Squad retro reviews any amber\/red cells.
                <\/p>\n\n\n\n

                Sprint-by-Sprint Rollout Checklist (185 w)<\/strong><\/h4>\n\n\n\n
                Sprint<\/strong><\/td>Additions<\/strong><\/td><\/tr>
                Week 0<\/strong><\/td>Install SBOM Action, baseline coverage, create Risk Matrix template<\/td><\/tr>
                1<\/td>Enforce DoR on top 50 % stories; start GenAI tests (optional toggle)<\/td><\/tr>
                2<\/td>Move all stories through Plan-Left column; enable dual-review rule<\/td><\/tr>
                3<\/td>Activate Measure-Left dashboard; alert thresholds at yellow<\/td><\/tr>
                4<\/td>Hold first \u201cPredictability Retro\u201d (look only at lead indicators)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                After Sprint 4 most squads report 30\u201340 % drop in re-work hours and one less hot-fix per release.<\/p>\n\n\n\n

                Common Pushbacks & Answers (120 w)<\/strong><\/h4>\n\n\n\n
                  \n
                • \u201cTests slow us down.\u201d<\/strong>\u2002Our GenAI scaffold adds 90 s per PR; re-work bugs cost hours.
                  <\/li>\n\n\n\n
                • \u201cWe can\u2019t write risk matrices for every story.\u201d<\/strong>\u2002Do it only for epics with \u22655 SP risk; copy labels to child stories.
                  <\/li>\n<\/ul>\n\n\n\n

                  \u201cSBOM timeouts in CI.\u201d<\/strong>\u2002Cache node modules \/ Go cache; SBOM diff-only mode cuts 70 %.
                  <\/p>\n\n\n\n

                  Real-World Impact: Wellness-App Case (110 w)<\/strong><\/h4>\n\n\n\n
                    \n
                  • Before:<\/strong> 36 % of sprints carried rollover, 5 hot-fixes post-launch.
                    <\/li>\n\n\n\n
                  • After Plan-Left:<\/strong> rollover 12 %.
                    <\/li>\n\n\n\n
                  • After Code-Left & Measure-Left:<\/strong> 0 hot-fixes; app-store approval first try.
                    <\/li>\n<\/ul>\n\n\n\n

                    Time saved: 2 engineer-weeks per quarter \u2192 re-invested in growth features.
                    <\/p>\n\n\n\n

                    Takeaway Checklist (70 w)<\/strong><\/h4>\n\n\n\n
                      \n
                    1. Add Plan-Left column & DoR.
                      <\/li>\n\n\n\n
                    2. Enable GenAI test scaffold & SBOM on PR.
                      <\/li>\n\n\n\n
                    3. Track Risk-High WIP, TTF-Review, Coverage \u0394, SBOM penalty.
                      <\/li>\n<\/ol>\n\n\n\n

                      Hold monthly predictability retro\u2014focus on lead indicators, not velocity excuses.<\/p>\n\n\n\n

                      <\/h4>\n","protected":false},"excerpt":{"rendered":"

                      Ship predictably by moving planning, testing and metrics to the very start of every iteration. \u201cShift-Left\u201d dies in committees when it means \u201cQA starts earlier.\u201d Real shift-left moves planning, testing, metrics, and risk gates to the very start of every sprint. In this deep dive we unpack the Plan-Left \u2192 Code-Left \u2192 Measure-Left triangle we […]<\/p>\n","protected":false},"author":1,"featured_media":15,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[11,10,9,14,13,12],"class_list":["post-14","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-shift-left-engineering","tag-ai","tag-chatgpt","tag-neural","tag-neuro","tag-programing","tag-robot"],"_links":{"self":[{"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/posts\/14","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/comments?post=14"}],"version-history":[{"count":12,"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/posts\/14\/revisions"}],"predecessor-version":[{"id":32,"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/posts\/14\/revisions\/32"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/media\/15"}],"wp:attachment":[{"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/media?parent=14"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/categories?post=14"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/steadyrabbit.in\/blogs\/wp-json\/wp\/v2\/tags?post=14"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}