Agile values and principles for non software teams
summary
Practical steps for non‑software teams at Capital One: set a clear start with why (six cross‑functional teams given a 10% web drop‑off reduction goal), make work visible (legal, ~20 people, mapped work, cut WIP, found a single sign‑off bottleneck and introduced two service classes with 2‑day vs 1‑week SLAs), and deliver early and often (help‑files owner moved releases from six‑monthly to weekly). Also adds regular pulse checks for HR, flags exec backlog visibility and performance reviews as unresolved thorns.
AI-written summary · about
chapters (8)
- 0:00Intro
- 4:25Agile values and principles
- 6:09Start with why
- 9:09Work visible
- 12:49Organizational priorities
- 13:53Observer feedback
- 16:57Sprint cycle
- 21:02Selfsufficient teams
related talks
27mLeading a Team with Values
45mAgility in non software teams, lessons from the front lines
15mDelivering value agility in a large company
46mAgile: principles over practices
01h 01mLeadership Lessons from the Agile Manifesto
18mAgile leadership and technical mastery, a harmonious alliance
33mEffective Agile Processes: It’s All About People
01h 10mAgile Cross Team Collaboration How Tos