The document discusses different approaches to software development like waterfall and test-driven development (TTD). Waterfall has issues like finishing all work before moving forward, low business details and user experience involvement. TTD provides benefits like parallel work, high business and user experience involvement, and faster feedback. It also discusses using kanban to visualize workflow, forecast delivery, address bugs, and scale teams as a whole system by adding roles like coaches and leads as more developers are added.

1. Understand The
System (Kanban)
Diego Pacheco

3. Big Architecture Rocks
Platform / Tools / Languages / Big Dependencies
DevOps, Kubernetes, A/B Testing, Etc...
What's the Right Problem
Business Requirements, UX , Tech Feasibility
User Stories, Swagger API, UX Design
Deliver the Right Solution
Sw Design, Test, Code, Deploy, (A/B Tests Results)
P2
P1

5. ❏ Waterfall ISSUES
❏ Finish all before move
❏ Assume is DONE
❏ SEQUENTIAL
❏ LOW BIZ DETAILS.
❏ No UX. BA doing UX.
❏ Bad Tech Surprises
❏ Low Feedback
❏ SLOW
❏ Project Culture
Waterfall

6. ❏ TTA BENEFITS
❏ Finish all ONE move
❏ Assume is LESS
❏ PARALLEL
❏ HIGH BIZ DETAILS.
❏ UX. BA + ARCH + UX.
❏ Good Tech Validation
❏ HIGH Feedback
❏ FAST
❏ Product Culture
TTA

7. ❏ TTA BENEFITS
❏ Finish all ONE move
❏ Assume is LESS
❏ PARALLEL
❏ HIGH BIZ DETAILS.
❏ UX. BA + ARCH + UX.
❏ Good Tech Validation
❏ HIGH Feedback
❏ FAST
❏ Product Culture
❏ Waterfall ISSUES
❏ Finish all before move
❏ Assume is DONE
❏ SEQUENTIAL
❏ LOW BIZ DETAILS.
❏ No UX. BA doing UX.
❏ Bad Tech Surprises
❏ Low Feedback
❏ SLOW
❏ Project Culture

9. Engineers : 12
Throughput: 4 * 12 = 48
Weeks : 4
Forecast : 4 * 48 = 192M
❏ Forecast Formula
❏ Self Tuning System
❏ Productivity Goals
❏ Weekly Confidence Scores
❏ Remember: Now | Later | Way Later
❏ Bubbles:
❏ Holidays | Vacations
❏ Meetings
❏ Bugs | Refactorings
❏ Deviation

10. ❏ Forecasting 101
❏ Use a google docs / sheets.
❏ Get Discovery & Delivery Leads to talk.
❏ Count: US, Bugs, Engineers, Weeks, Throughput.
❏ Do the MATH!
❏ Be Honest
❏ Have Confidence Scores per Week
❏ Self-tuning: Feedbacks, RCAs, Retros, Time.

11. ❏ Bugs need to go through the Discovery
❏ Clarification on what's critical and whats is not
❏ We need to RAISE the TECH BAR so we reduce
BUGS therefore reduce deviation.
❏ Speed up without high Tech bar will create much more
bugs and unsustainable PIECE.

12. ❏ How do we Speed UP? Just more DEVS? NO.
❏ PO does not Exist: Triads: UX + ARCH + PO.
❏ Same number of UX + BA + ARCH in discovery. Do we
have that right?
❏ As we add more developers:
❏ Engineer Leads
❏ Coaches
❏ As More “Big Things” in parallel - More people on
Foundation too.

13. P2
P1
1 People
1 arch
8 people
1 coach
1 eng lead
6 devs
3 people
1 ba
1 ux
1 arch
Scale the system as a
WHOLE.
TEAM == 12

14. Understand The
System (Kanban)
Diego Pacheco