Nimble Work Management
Kairon - Gen AI Solutions
AKT/ AKC Access
→ Agile Methodology
→ Agile Software Development
→ Agile Program Management
→ Scrum Methodology
→ Kanban Methodology
→ Extreme Programming (XP)
→ Behaviour Driven Development (BDD)
→ Feature Driven Development (FDD)
→ Adaptive Software Development (ASD)
→ Dynamic System Development Method (DSDM)
→ Sustainable Pace
→ Story Mapping
→ Test Driven Development
→ Acceptance Test Driven Development
→ Iterative & Incremental Development
→ Pair Programming
→ Unit Testing
→ Acceptance Testing
→ Agile Planning
→ Refactoring in Agile
→ Burndown Chart
→ Lead Time & Cycle Time
→ Agile Velocity
→ Definition of Done
→ Backlog Refinement
→ User Stories
→ Scaled Agile Frameworks
→ Large Scale Scrum (LeSS)
→ Scrum of Scrums
→ Agile Release Train
→ Is SAFe Agile?
→ SAFe Implementations
→ Enterprise Agility With SAFe
→ What is Project Management Lifecycle?
→ What is a Project Management Office (PMO)?
→ What is Agile Project Management?
→ Importance of Project Management
→ What is a Project Roadmap?
→ What is Resource Management?
→ What is Work Management?
The concept of sustainable pace originated in XP (eXtreme Programming). In “Extreme Programming Explained” Kent Beck argued for a 40-hour work week and against working overtime for longer than a week. Ron Jeffries later argued that this practice should be called sustainable pace.
Img Src: staff.com
Sustainable pace is an essential part of Agile. In fact, one of the principles of the Agile Manifesto explicitly talks about sustainable pace:
The Scrum Guide doesn’t mention sustainable pace. But it does put the power to decide what will be done in the next sprint firmly in the hands of the development team.
Scrum says quality goals shouldn’t change during a sprint. And you’ll see later how quality suffers from speed. So, working at a sustainable pace is implicit in Scrum and under the control of the development team.
Well, actually, the boost doesn’t last that long. The detrimental effects of speeding take hold immediately. After about a week the boost decreases rapidly, turning into a deepening loss after 3 to 4 weeks.
Start at the low end. Potentially even taking a sprint, shortened if you like, to complete a single issue in full accordance with your Definition of Done.
But there’s no denying the mountain of research that confirms that working at a sustainable pace is actually the most productive way to work. Kanban’s WIP limit is one of it’s gold nuggets to help you find and maintain that sustainable pace.
So, slow down, get clear on the tasks that deliver the most value, and get those finished. Your productivity will skyrocket.
Signup for updates!
Humanize Work. And be Nimble!