Process Hacking With Rangle Flow
summary
Rangle.io refines a delivery recipe used across dozens of short MVP projects over three years and proves it scales: a team of 70 JavaScript developers runs Scrum by the book, with a prioritized backlog, two‑week sprints, reviewed pull requests, CI and continuous deployment (staging updated per PR). Product owners sit with the team, QA joins early, and clarity‑canvas kickoffs compress discovery. The claim is concrete: these practices shrink work‑in‑progress, speed feedback, build client trust, and reliably produce shippable increments.
AI-written summary · about
chapters (17)
- 0:00Intro
- 4:00Three Modes
- 5:30The Key Idea
- 7:20Why Would We Build Things We Don't Need?
- 8:40How Do We Solve This?
- 9:57What's Wrong with Work in Progress?
- 12:31Why Scrum?
- 17:22Key Practices
- 21:03The Importance of Prioritizing
- 24:06Working with the Product Owner
- 29:44Handling PO's Commitments
- 31:01Continuous Delivery
- 36:04What Happens to QA?
- 39:45The Project kickoff
- 41:42Lean UX
- 43:38A Rose by Other Name: Process Hacking
- 44:37From Agile Teams to Agile Organization
related talks
22mOptimizing Product Development: Balancing Speed, Quality, and Process
52mToo many cooks! Supporting augmented teams without getting salty
40mRun Circles, Not Relays
22mCreating a team mindset of continuous improvement
39mScaling R&D to thousands of people without dedicated QA
25mDevOps Handbook Experiments in Accelerating Delivery
44mContinuous Delivery of HTML5 Applications
11mWorking with sharp tools - A case study of Continuous deployment