First scrum cadence planning — aligning strategic decisions, team, and execution backlog
Sprint 1 Planning — 60 minutes. First formal scrum cadence session.
| Time | Topic | Owner | Goal |
|---|---|---|---|
| 0–8 min | Cadence & Ceremonies | Joana | Confirm scrum structure, ceremonies, artifacts |
| 8–15 min | Team & Hiring | Joana / Victor | Current team, Value First hires, role shifts |
| 15–25 min | Portfolio Overview | Joana | Agent status, priority shift, Kush decisions |
| 25–35 min | Deep Dive Sessions | Tony / Joana | Quarterly design sessions plan, first deep dive scope |
| 35–52 min | Sprint 1 Planning | All | Select backlog items, assign, define sprint goal |
| 52–60 min | Open Decisions | All | Blockers, needs-human items, next steps |
Three-layer cadence: 2-week sprints, monthly portfolio, quarterly deep dives
Execution cadence. Ship code, build agents, deliver results.
| Planning | Monday, Day 1 |
| Standups | Mon/Wed/Fri (team only) |
| Review + Retro | Friday, Day 10 |
| 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
| Person | Current Role | Evolving To | Sprint Role |
|---|---|---|---|
| Tony | Strategic leadership | Product Owner (biweekly) | Sprint planning + review only |
| Joana | Program delivery | Net new revenue agent design | Scrum lead + agent designer |
| Victor | Technical delivery | Net new revenue agent design | Technical lead + agent designer |
| Charlie | Chief Architect / Agent Runtime | Platform + architecture decisions | Technical advisor |
| AI Delivery Engine | Engineering & Ops AI | Autonomous Delivery Partner | Delivery method engine, scrum artifacts |
| Dukane | Delivery support | QA manager | Output quality review |
| 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 |
Reframed Jul 7 based on Kishore's clarification. SOC for AI monitors known Kindo agents for governance violations — not enterprise shadow AI discovery (handled by Deloitte's detection engineering team). Platform-native: all 5 objectives consume Kindo audit logs and control plane APIs.
🎯 Objective 1 — Detect unauthorized agent deployment/modification
🔌 Objective 2 — Detect unauthorized tool/data source connections
📊 Objective 3 — Detect behavioral drift from SOPs over time
🔒 Objective 4 — Detect guardrail/policy changes
🏯 Objective 5 — Detect cross-tenant data contamination
All governance monitoring data comes from Kindo's own control plane APIs and audit logs. No external integrations required for v1.
| Endpoint / Source | Data Provided |
|---|---|
GET /v1/agents/list |
Agent inventory (name, creator, models, recent runs) |
GET /v1/integrations/connections |
Integration connections (type, owner, creation date) |
GET /v1/models |
Enabled models |
| Audit Log (Enterprise) | All agent actions, config changes, tool invocations, DLP events |
| SMK/Syslog Forwarding | SIEM export for external detection rules |
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. View IK Approach | 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 |
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).
First sprint: focus on soft-skills deliverables while engineering is on PTO
Validate scope ✅ → Pivot to platform governance → Deliver Governance Monitor Agent PoC
Scope validated Jul 7 — Deloitte's SOC team confirmed SOC for AI = monitoring known Kindo agents, not enterprise shadow AI discovery. Sprint pivoted to platform governance. Deliverable: working Kindo Scheduled Agent that monitors agent inventory, integration connections, and model usage against governance baselines.
| Item | Type | Owner | Effort | Dependencies / Risks |
|---|---|---|---|---|
| SOC for AI — Scope Confirmation ✅ DONE. Deloitte (Kishore) confirmed: shadow AI discovery = their detection engineering team. SOC for AI = Kindo platform governance monitoring. 5 objectives defined. |
P0 | Joana | 1d | ✅ DONE |
| SOC for AI — Capability Mapping + Odin Assessment ✅ DONE. Kindo audit logging, RBAC, DLP mapped against 5 objectives. API endpoints confirmed (GET /v1/agents/list, GET /v1/integrations/connections, GET /v1/models). Gaps identified: drift detection, policy-change alerting, cross-tenant contamination detection. |
P0 | Delivery Team + AI Engine | 0.5d | ✅ DONE |
| SOC for AI — Governance Monitor Agent: Design + Build v1 in Kindo ⚠️ Blocked: Enterprise access needed for API Action steps. Agent design complete: 4-step workflow (agent inventory → integration connections → models → LLM governance analysis). Unblocked once Enterprise access confirmed. |
P1 | Delivery Team | 2d human / 2d AI-assisted | ⚠️ Blocked: Enterprise access needed |
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 + ✅/⚠️/❌ |
| 7 | Documented for automated status reporting | 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 |
|---|---|---|---|
| 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). |
| Automated Scrum Artifacts Setup | Joana + Delivery Team | Sprint 1 | Configure automated sprint backlog, burndown, status delivery. ⚠️ Verify accuracy before relying on automated output. |
Items requiring team input during Monday's planning
5 scope questions sent Jun 25. 2 resolved (Q1, Q3). 3 remaining (Q2, Q4, Q5) — resolve in today's planning. Source: SOC for AI — Scope & Research doc.
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 | 70% | Training videos re-generated (T1-T4), next-button gating shipped. Architecture stabilized on Deloitte-specific worker. |
| 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 |
Autonomous Delivery Partner — the product is the method, AI is the engine
Every load-bearing milestone (85% of outcomes) used these 5 components. Each Sprint 1 item should map to this template.
| # | Component | What It Means | Sprint 1 Check |
|---|---|---|---|
| 1 | Named Owner | A human on the customer side driving the loop (the "Tony" equivalent) | Who is the owner for each item? |
| 2 | Transcript / Intake Artifact | Customer's own words, not our interpretation | Do we have source material in their language? |
| 3 | Standing Rules | Deterministic rules, written — never probabilistic process docs | Are the rules codified or still in people's heads? |
| 4 | Cron-Sustained Refresh | Keeps the output alive after initial delivery | Will this need automated updates or is it one-shot? |
| 5 | Recipient's Narrative | Output framed in the customer's framework, not VtKl's internal language | Are we using Krishna's/Kush's words or ours? |
#1 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.
🏔️
Executive
Revenue Map for Ron dinner (May 21-23). Visual, revenue-framed.
⚙️
Strategic
Sprint plan + GANTT + questionnaire (Jun 8-9). Full planning cycle in one thread.
📊
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 + AI calibration |
| Joana | Program Delivery | Delivery Authority | Scrum lead + agent design |
| Charlie | Builder | Platform Architect | Architecture decisions only |
| AI Delivery Engine | 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 | ⚠️ Dependency — generate + send early in sprint |
| 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 |