Live sprint tracker - progress, decisions, and backlog for Sprint 1
Day 5 of 10 - June 29 → July 10, 2026
kindo-deloitte-internal.pages.dev live with full content for internal team use.| Date | Event | Details |
|---|---|---|
| Jul 10 (Fri) | Kush Design Session | 90 min, virtual. Skills, memory, self-improving agents. Context-gathering + requirements for net new agent pipeline. Tony, Charlie, Kush + team. |
| Jul 10 (Fri) | Deloitte Training Cohort 2 | Second training cohort launch. LMS technical review ✅ complete (Charlie approved). Domain consistency fix in progress. |
| Jul 10 (Fri) | Sprint 1 End | Sprint Review + Retro. Show-don't-tell evidence for all completed items. |
| Jul 13 (Mon) | Sprint 2 Planning | Engineering team returns (Madison early Jul, Sean week of Jul 7). Code work unblocked. |
| Jul 27 | Monthly Portfolio - Houston | Ron in Houston. Video evidence + working links for Ron/Forge Point. |
Three-layer cadence: 2-week sprints, monthly portfolio, quarterly deep dives
Execution cadence. Ship code, build agents, deliver results.
| Planning | Monday (every 2 weeks) |
| Standups | Mon/Wed/Fri (team only) |
| Review + Retro | Friday (every 2 weeks) |
| Tony attends | Planning + Review only |
Show results to executives. Video evidence + working links.
| First meeting | ~Late July (Jul 27) |
| Attendees | Tony, Charlie + Ron |
| Format | Show, don't tell (see below) |
| Note | Same city as quarterly deep dive to avoid over-travel |
In-person design sessions. Strategic alignment + release planning.
| Duration | ~5-7 days |
| Q3 location | Houston, TX (aligned with July monthly portfolio - Ron anchor event Jul 27) |
| With | Team + Ron + key engineers |
| Output | Quarter release plan |
| Artifact | Cadence | Description | Status |
|---|---|---|---|
| Sprint Backlog | Updated daily | Items committed for current sprint, status, blockers | Sprint 1 |
| Burndown | Real-time | Story points or items remaining vs time | Sprint 1 |
| Sprint Review Deck | End of sprint | Video evidence + working links of shipped work | Sprint 1 |
| Definition of Ready | Standing | Criteria for items entering sprint (see below) | Defined |
| Definition of Done | Standing | Criteria for items being complete (see below) | Defined |
We're moving at 5× traditional speed. Words can't keep up. Ron didn't understand net new revenue agents until the third time Tony explained it - and Ron is the sharpest person in the room. If Ron needs three reps to absorb a verbal summary, everyone else needs more.
The old way (what we stop doing):
The new way (what every portfolio item needs):
| Month | Location | Notes |
|---|---|---|
| July | Houston | Ron in Houston Jul 27 - anchor event |
| August | San Francisco | Krishna's base |
| September | Austin | Tony's base |
| October | Los Angeles | Charlie's base |
Deep dives aligned with monthly portfolio locations to avoid over-travel (Q3 → Houston, Q4 → Los Angeles).
Current team, role evolution, and Value First hiring plan
| Role | Count | Region | Focus | Status |
|---|---|---|---|---|
| AI PMO / Soft Skills | 1-2 | LatAm (preferred) | Requirements gathering, stakeholder mgmt, verification | Interviewing |
| Engineer | 1-2 | Eastern Europe or LatAm | MLflow, Kindo agent configuration, integrations | Planning |
Process: Invoice → Charlie → Ron. Charlie vets technical candidates. LatAm for soft-skills (live meetings), Eastern Europe for code (Charlie's preference).
| Team | Status | Expected Back | Impact |
|---|---|---|---|
| Agent Runtime (Madison) | PTO | Early July | 2.5 weeks PTO - multi-agent, agent features blocked |
| Agent Runtime (Sean) | PTO | Week of Jul 7 | Working ~2 days/week past 2 weeks + off next week |
| Core Kindo (Brian Van) | PTO | Mid-July | Core platform changes blocked |
| Charlie (Agent Runtime lead) | Active | - | Shipped memory prototype solo |
Sprint 1 implication: Focus on soft-skills deliverables (requirements, agent design, research) that don't need Kindo eng. Engineering-dependent items slot into Sprint 2+ when team is back.
Agent portfolio with June 24 priority shift - SOC for AI is the new #1
| ID | Agent | Status | Revenue Class | Blocker |
|---|---|---|---|---|
| A.1 | Threat Monitoring | PROD | Contracted | - |
| A.2 | Threat Intel | PROD | Contracted | - |
| A.3 | Threat Hunt | PROD | Contracted | - |
| A.4 | Detection Engineering | PROD | Contracted | - |
| A.5 | CTEM | BUILT | Contracted | Deployment pending |
| A.6 | Vitals Dashboard | DEPRIORITIZED | Alliance | Kush shifted to SOC for AI |
| A.7 | Quality Audit Agent | REQS | Alliance | Design sprint needed |
| A.8 | Cloud Security Agent | PLANNED | Alliance | - |
| A.9 | IR Agent | PLANNED | Alliance | - |
| A.10 | IoT/OT Monitor | DEPRIORITIZED | Alliance | Kush shifted to SOC for AI |
| A.11 | Custom Client Agents | REQS | Alliance | Shadow & document method |
| A.12 | Identity Agent → IdaaS | PLANNED | Alliance | Tim Corder engagement |
| A.13 | GRC Agent → GRC aaS | PLANNED | Alliance | Nathan Ellis engagement |
| NEW | SOC for AI | #1 Priority | Alliance | Research + integration mapping |
"Shadow IT for AI" - discover which AI tools, agents, LLMs, copilots, MCP servers run across endpoints, SaaS, cloud; then govern, policy-enforce, remediate. Now #1 priority (Kush deprioritized A6 + A10). Distinct from A.1 (Threat Monitoring) - A.1 is Deloitte's existing SOC agent; SOC for AI coexists with / complements it.
Layer A - Shadow AI Discovery
Which AI, by whom, how much, what risk. Via CASB/SSE + IdP + DLP + SIEM the client already owns.
Layer B - Endpoint / EDR Telemetry
Orchestrate EDR/SIEM agents already on the machine (CrowdStrike-style). No new agent installs - Deloitte was explicit.
Mechanism: API-level orchestration of existing monitoring agents; build domain-specialized agents inside Kindo. No core architecture change. ~80% soft-skills / ~20% engineering.
Validated Market Timing:
Source: SOC for AI - Scope & Research doc (Jun 25). Tenant-safe = research-grade, needs Charlie's sign-off. Registry status needs Victor/Charlie confirmation (Q1).
Already in Kindo - can start immediately (confirm registry):
| Platform | SOC-for-AI Capability | In Kindo? | Tenant-safe? |
|---|---|---|---|
| CrowdStrike Falcon | Shadow AI Discovery - AI apps, agents, LLM runtimes, MCP servers | Confirmed | Per-tenant (see Q2) |
| Splunk / Datadog | SIEM + observability for AI activity | Confirmed | Yes |
| Grafana / Sumo Logic / Google SecOps | Dashboarding, log analytics, security ops | Confirmed | Yes |
Microsoft Stack - covered via Microsoft MCP:
| Platform | Capability | Tenant | Priority |
|---|---|---|---|
| MS Defender for Endpoint | Shadow-AI discovery (Agent 365 - GA May, preview Jun 2026) | Azure-native | Via MCP |
| MS Intune | AI agent policy enforcement on devices | Azure-native | Via MCP |
| MS Purview | DLP / data classification for AI | Azure-native | Via MCP |
| Nightfall / Netskope / Cyberhaven / Okta | GenAI DLP, CASB, data lineage, OAuth-consent discovery | Validate | P3 |
Quarterly in-person sessions - strategic alignment + release planning with Deloitte
These items were categorized under “design sessions” in Tony’s meeting notes. More than half of what Deloitte raised maps to these sessions.
| # | Topic | Description | Owner |
|---|---|---|---|
| 1 | Net New Revenue Agents | Design + deploy agents that generate alliance revenue (Tier 2/3 packages) | Tony / Joana |
| 2 | Threat Remediation | Extend A.1-A.5 into automated remediation workflows | Charlie / Victor |
| 3 | Deloitte Roadmap (Azure/GCP) | Cloud platform alignment and multi-cloud strategy | Charlie |
| 4 | Institutional Knowledge / Memory | Skills, memory, compound learning flywheel. Don't equip Deloitte to build what we want to build (Charlie) | Charlie |
| 5 | AI Cyber Guard / Tower | Control plane co-development | Charlie |
| 6 | Lifecycle Hooks | Generic lifecycle hooks - Kush says yes but NOT most important. Ship fast MVP, don't over-engineer. Deployment speed > stickiness features. | Charlie |
| 7 | Workflow Acceleration | Accelerate deployment cycle (time-to-value for new Kindo customers) | Victor / Joana |
| 8 | SOC for AI | Shadow IT discovery, AI governance, integration mapping | Joana / Victor |
90 min, virtual. Skills, memory, self-improving agents. Context-gathering + requirements for net new agent pipeline. Tony, Charlie, Kush + team. Aligned with Sprint 1 end date.
Houston, TX - aligned with July monthly portfolio (Ron in Houston Jul 27). 5-7 day in-person session. Team + Ron + key engineers. Output: Q3 release plan, SOC for AI architecture, net new revenue agent designs.
Los Angeles, CA - aligned with October monthly portfolio (Charlie's base). Review Q3 results, plan Q4 releases, expand to service lines beyond D&RaaS (Identity aaS, GRC aaS).
Day 5/10. Focus on soft-skills deliverables while engineering is on PTO. Kush Design Session + Cohort 2 launch both on Jul 10. LMS technical review complete — Charlie approved all 4 Technical-track videos.
This is ~80% soft-skills work - agent configuration, not code. Warren accelerates: research (done), design docs, agent config specs, Kindo setup. Goal isn't just a design - it's a working agent in Kindo by sprint end. Human effort = scope confirmation (Joana's 5 Qs) + validation + review. Warren does the build grunt work.
| Item | Type | Owner | Effort | Dependencies / Risks |
|---|---|---|---|---|
| SOC for AI - Scope Confirmation Get answers to Joana's 5 questions from Charlie & Victor: registry check, CrowdStrike tenant isolation, Microsoft path, first deliverable sizing, control plane alignment |
P0 | Joana | 1d | Partial: 2/5 resolved, 3 open Q1 (registry) ✅ Q3 (Microsoft) ✅ - Q2 (CrowdStrike tenant) open - Q4 (first deliverable) open - Q5 (scope + control plane) open. Remaining 3 to be resolved in today's planning. |
| SOC for AI - Requirements Questionnaire → Krishna Generate SOC for AI questionnaire (same format as A.6). Send to Krishna who routes to right person. Answers refine which monitoring tools Deloitte's clients actually use - improves agent design accuracy. |
P0 | Tony + Joana + Warren | 0.5d | Done + Sent Deployed Jun 29. Sent to Krishna Jul 1. 5 sections, 19 questions, priority-tagged, Deloitte client language. Awaiting responses. |
| SOC for AI - AI Discovery Agent: Design + Build v1 in Kindo Design + configure in Kindo: CrowdStrike Falcon (if tenant-safe) + MS Defender; AI app/agent inventory; dashboard; tenant-scoped data. Warren produces agent config spec + builds draft in Kindo. Human effort = review + validate. Per Joana's §4. |
P1 | Warren + Victor | 2d human / 6d Warren | Blocked: Scope Q2, Q4, Q5 open Registry and Microsoft path confirmed. CrowdStrike tenant (Q2) still gates Layer B. Kush Design Session Jul 10 may resolve remaining questions. |
Show-don't-tell: every criterion needs evidence, not a status update.
An item can enter the sprint when ALL of these are true:
| # | Criteria | Why |
|---|---|---|
| 1 | Clear outcome defined - what does "done" look like in business terms, not technical terms? | Victor's point: business value, not technical value |
| 2 | Owner assigned - single person accountable | No orphan items |
| 3 | Dependencies identified - blocked/unblocked explicitly tagged | Victor's framework: shoot where we're unblocked |
| 4 | Effort estimated - days, not points. Be honest. | Tony needs to know what to expect without asking |
| 5 | Classified soft-skill vs code - which work type? Determines who can execute. | ~80% soft-skills moves without Brian's team |
| 6 | Passes tenant filter (if integration) - tenant-scoped? data stays in tenant? SOC 2 II / BAA / DLP? | Tony's note #1: "Deloitte only" |
| 7 | Fits the sprint - total committed work ≤ team capacity | Don't overcommit then under-deliver |
| 8 | Acceptance criteria written - how will we verify it's done? | "Show don't tell" starts here |
An item is done when ALL of these are true:
| # | Criteria | Evidence Required |
|---|---|---|
| 1 | Acceptance criteria met - every criterion checked off with proof | Screenshots, video, or live URL |
| 2 | Business done, not just technical done - stakeholder can see and use it | Working link or deployed artifact |
| 3 | Evidence attached - "show don't tell" proof in the same message as the completion claim | Video walkthrough, screen recording, API response |
| 4 | Integrations pass tenant + compliance check | Tenant filter results documented |
| 5 | No open blockers or regressions | Verification report |
| 6 | Reviewed - at least one other team member has seen the output | Reviewer name + feedback |
| 7 | Documented so Warren can report status | Warren updates programmatically |
| 8 | Owner confirmed done | Explicit sign-off |
Items that produce a built artifact (agent, integration, code in Kindo) - ranked by strategic priority
Parallel track - program management work that needs an owner and date but doesn't produce a product artifact. Not sprint-rankable. Joana's track.
| Item | Owner | Target Date | Notes |
|---|---|---|---|
| Deloitte Training Cohort 2 Launch | Joana | Jul 10 | Second cohort goes live. LMS pending Charlie's technical review. |
| Scaling Story for Ron / Forge Point | Tony + Joana | During Sprint 1 | Capture while Tony is present - he goes biweekly after. 3-5× revenue growth narrative for Forge Point VC. |
| Monthly Portfolio Prep (July) | Joana | Ahead of Jul 27 Houston | Video evidence + working links for shipped functionality. |
| Value First Hiring | Joana / Victor | Ongoing | Interviews in progress. Invoice → Charlie → Ron. |
| Deep Dive Prep / Calendar + Budget | Tony / Joana | TBD | Done - deep dives aligned to monthly portfolio cities (Houston Q3, LA Q4). |
| Warren Scrum Artifacts Setup | Joana + Warren + Victor | Sprint 1 | Configure Warren for sprint backlog, burndown, status delivery. Verify accuracy before Tony relies on it. |
Items requiring team input - updated July 3
5 scope questions sent Jun 25. 2 resolved (Q1, Q3). 3 remaining (Q2, Q4, Q5) - target resolution before Kush Design Session Jul 10. Source: SOC for AI - Scope & Research doc.
/questionnaire.
110 days of empirical data (Mar 9 - Jun 26, 2026) - what worked, what failed, what was killed
| Initiative | Grade | Key Evidence |
|---|---|---|
| Kindo × Deloitte Dashboards | 85% | 2 production dashboards, daily cron, 240 deploys. Owner (Joana) + same-day loop + cron refresh |
| Strategic Dashboards | 80% | Same-day delivery pattern. Revenue Map for Ron dinner = built same day Tony directed |
| Kindo LMS | 75% | T1-T4 deployed (T1/T2 Joana-confirmed). P1/P3/P4 visual re-times done. Next-button gating shipped. P2 provenance fix + T3 seam fix pending. Cohort 2 target: Jul 10. |
| Tony CoS Dashboard | 55% | 136 deploys, CI/CD working. But: DM capture unverified, Phase 2 never started |
| Autonomous Pipeline | 40% | Architecture complete (43 routes). But: 0 agents dispatched for 42+ days. Pipeline became meta-work |
March-April: Build
Pipeline architecture, 67 routes, Sprint 0, first dashboards. Every problem solved by adding.
May: Peak Complexity
6 new Pages in 3 weeks. 5 AI eval crons. 4 daily dossiers. Maximum complexity = diminishing returns.
June: Subtract
7 systems killed. 0% dossier engagement. Silence First. Human-only review. Higher signal than anything added.
| # | Capability | Who Reacted | When |
|---|---|---|---|
| 1 | Thinking model / decision OS | Igor: "Jarvis not Siri" | May 15 |
| 2 | Knowledge extraction | Steve Ward: "floored" | May 25 |
| 3 | AIPMO / autonomous PM | Valent: SOW signed ($5K) | Apr-Jun |
| 4 | Dependency mapping | NFL corpus proof point | Apr |
| 5 | Sprint planning / estimation | Hector: "that's money" | Jun |
Warren = Autonomous Delivery Partner - the product is the method, Warren is the engine
Every load-bearing milestone (85% of outcomes) used these 5 components. Each Sprint 1 item should map to this template.
A human on the customer side driving the loop (the "Tony" equivalent). Sprint 1 check: Who is the owner for each item?
Customer's own words, not our interpretation. Sprint 1 check: Do we have source material in their language?
Deterministic rules, written - never probabilistic process docs. Sprint 1 check: Are the rules codified or still in people's heads?
Keeps the output alive after initial delivery. Sprint 1 check: Will this need automated updates or is it one-shot?
Output framed in the customer's framework, not VtKl's internal language. Sprint 1 check: Are we using Krishna's/Kush's words or ours?
01 - Owner + Same-Day Loop
The mechanism. Without a named owner driving the loop, nothing ships. Present in: Kindo dashboards, CDO thesis, Execution Plan + Revenue Map, Strategic Portfolio Design, Great Subtraction.
11 - Narrative (Recipient's Framework)
The communication layer. Without narrative framing, output ships but doesn't land. Ron needed visual revenue framing. Igor needed "Jarvis" framing. Krishna needed triage language.
E
Executive
Revenue Map for Ron dinner (May 21-23). Visual, revenue-framed.
S
Strategic
Sprint plan + GANTT + questionnaire (Jun 8-9). Full planning cycle in one thread.
O
Operational
Daily dashboard refresh via cron. 240 deploys. Deloitte logs in daily.
Each person migrated UP in altitude over 110 days. Sprint 1 should respect these altitudes.
| Person | Started As | Evolved To | Sprint 1 Altitude |
|---|---|---|---|
| Tony | Operator (every function) | Teacher → Subtractor | Strategic direction only. Biweekly. |
| Victor | Ops Support | Chief Operating Intelligence | Tactical execution + Warren calibration |
| Joana | Program Delivery | Delivery Authority | Scrum lead + agent design |
| Charlie | Builder | Platform Architect | Architecture decisions only |
| Warren | Engineering Tool | Autonomous Delivery Partner | Execution engine - absorbs operations |
"I don't want to do design partnership work where we equip them to build stuff that we want to build." Deloitte can execute faster than T&C on skills/memory if they know the HOW. Share the WHAT, never the HOW. This applies to all IK/memory sessions with Kush.
Tony (Jun 26): needs questionnaires for SOC for AI, A.7, A.11 - same format as A.6. Forward to Krishna who identifies who answers (resolves Adelina maternity leave gap without guessing org structure).
| Agent | Method | Adelina Coverage | Status |
|---|---|---|---|
| SOC for AI | Questionnaire (framed as Kush's priority) | Krishna routes to right person | Sent to Krishna Jul 1 |
| A.7 Quality Audit | Design Sprint questionnaire (~3hr session) | Krishna routes to QA lead | Sprint 2+ Prep |
| A.11 Custom Agents | Shadow & Document (SOPs + ride-along) | Shiva/Harish (client delivery) | Sprint 2+ Prep |
Channel activity and progress updates — most recent first
🔵 #deloitte-agents-design
🟢 #client-kindo-deloitte
🟡 #client-kindo-training
agents/soc-for-ai-discovery/t-and-c/kindo-deloitte-internal created, deployed to kindo-deloitte-internal.pages.dev