Agility in non software teams, lessons from the front lines
summary
Five practical lessons: get an explicit invitation to instruct before changing HR, finance or legal routines; choose the right tool for the job (don’t force Scrum/Sprints/Jira on repeatable invoice or payroll work); separate transactional queuing work from creative, feedback-driven policy work using Cynefin thinking; define success as business outcomes and measure what matters (impact, not activity); work inside systemic constraints and rethink whether people are a single team or multiple role-focused streams.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:23Cornish flag
- 2:23Non software teams
- 3:35Who is this talk for
- 5:05Five Lessons
- 5:43Invitation
- 6:48Freedom of choice
- 9:13Agile vs Scrum
- 12:03What do you actually do
- 14:35Transactional work
- 17:45Creative work
- 23:02What do you do
- 26:01What actually matters
- 30:09Acknowledge your system
- 30:36Ask them to reflect
- 33:27Scrum teams
- 37:09Match the work
related talks
35mAgility at Scale: A Meeting of Mindsets
26mAgile values and principles for non software teams
51mAgility at Scale: A Meeting of Mindsets
39mAgility at Scale: A Meeting of Mindsets
29mBusiness Agility Panel
43mTaking Agile to the Enterprise – strategy lessons from seven years in transformation
05mCompany-Wide Agility
26mGet agile and don't die trying