Letting Agile Emerge - Our story
summary
Claim: agile adapts to team realities rather than forcing Scrum rituals. Implementation uses a Hive Kanban board for visibility and limiting work, moves the daily meeting to an asynchronous standup in Mattermost, and runs demos roughly monthly (Jan/Feb/Mar cadence) with two-developer project teams. Backlog items are tasks not stories, QA waits until client content entry, and automated regression tests come later using Drupal Test Traits. This reduces churn, preserves developer focus, and gives measurable progress by completed tasks and budget burn.
AI-written summary · about
chapters (34)
- 0:00Introduction and speaker intro
- 1:31Agile manifesto origins
- 2:15Four values of agile
- 3:17Twelve principles of agile
- 5:21Scrum methodology explained
- 7:07Scrum challenges and velocity
- 8:32What we like about scrum
- 9:14Daily standup changes
- 10:39Story points and developer pain
- 11:00Kanban methodology
- 13:27Kanban workflow and benefits
- 15:39Extreme programming basics
- 17:24Extreme programming practices
- 19:06Pair programming debate
- 20:09Customer test requirements
- 22:13Crystal methods overview
- 24:24Crystal properties and principles
- 26:09Crystal personal safety and focus
- 27:33Feature driven development
- 30:20Client communication with FDD
- 31:45DSDM methodology introduction
- 33:30DSDM time cost quality
- 35:41DSDM roles and phases
- 37:48Consultancy scrum explained
- 39:32Our agile journey and failures
- 40:34Current project lifecycle
- 41:39Kanban as our solution
- 43:06Weekly check-ins and demos
- 44:30Relaxed sprint cycles
- 45:33Velocity without story points
- 46:38QA and testing approach
- 48:03Client prioritization
- 48:44Empowering teams over processes
- 49:47Q&A and closing
