Agile Zone is brought to you in partnership with:

Jurgen Appelo calls himself a creative networker. But sometimes he's a writer, speaker, trainer, entrepreneur, illustrator, manager, blogger, reader, dreamer, leader, freethinker, or… Dutch guy. Since 2008 Jurgen writes a popular blog at, covering the creative economy, agile management, and personal development. He is the author of the book Management 3.0, which describes the role of the manager in agile organizations. And he wrote the little book How to Change the World, which describes a supermodel for change management. Jurgen is CEO of the business network Happy Melly, and co-founder of the Agile Lean Europe network and the Stoos Network. He is also a speaker who is regularly invited to talk at business seminars and conferences around the world. After studying Software Engineering at the Delft University of Technology, and earning his Master’s degree in 1994, Jurgen Appelo has busied himself starting up and leading a variety of Dutch businesses, always in the position of team leader, manager, or executive. Jurgen has experience in leading a horde of 100 software developers, development managers, project managers, business consultants, service managers, and kangaroos, some of which he hired accidentally. Nowadays he works full-time managing the Happy Melly ecosystem, developing innovative courseware, books, and other types of original content. But sometimes Jurgen puts it all aside to spend time on his ever-growing collection of science fiction and fantasy literature, which he stacks in a self-designed book case. It is 4 meters high. Jurgen lives in Rotterdam (The Netherlands) -- and in Brussels (Belgium) -- with his partner Raoul. He has two kids, and an imaginary hamster called George. Jurgen has posted 145 posts at DZone. You can read more from them at their website. View Full User Profile

10 Principles of Agile Project Management

  • submit to reddit
Project Time Management is one of the nine knowledge areas of the Project Management Body of Knowledge (PMBOK). It deals with the definition of activities (what are we going to do), the sequencing of the activities (in what order are we going to do them), and the development and control of the schedule (when are we going to perform those activities).

Agile Time Management
Over the past couple of weeks I have been trying to find out what the main principles of time management are in the case of agile software development. I was able to distinguish 10 principles so far, and I will present them here for your convenience. With each principle I also include a reference to an online article that (as far as I can tell) nicely describes the ideas behind it. If you don't agree with my list, or if you know some better reference material, feel free to add your thoughts!

1. Use a Definition of "Done"
How? Define what "Done" means and only count the activities that are Done.
Why? Prevent the build-up of hidden tasks ("technical debt") that cost a lot of time to fix down the road.
See: The Definition of "Done"

2. Use Timeboxes to Manage Work
How? Set a start- and end date for a collection of activities, and don't allow changes to those dates.
Why? Timeboxes keep people focused on what's most important. Don't lose time to perfectionism.
See: Time Boxing is an Effective Getting Things Done Strategy

3. Don't Add Slack to Task Estimates
How? Don't use scheduling and buffering of tasks. Add one buffer to the end of the timebox/project.
Why? All safety margins for tasks will be used ("Parkinson's Law" and "Student's Syndrom'").
See: Critical Chain Scheduling and Buffer Management

4. Defer Decisions
How? Make decisions only at the latest responsible time. "No Decision" is also a decision.
Why? The environment may change, making earlier decisions a waste of time.
See: Real Options Underlie Agile Practices

5. Reduce Cycle Time
How? Iterative cycles should be as short as possible.
Why? Speed up the learning feedback loop, and decrease the time-to-market.
See: Lean Software Development: Why reduce cycle-time?

6. Keep the Pipeline Short and Thin
How? Limit the amount of work-in-progress, and the number of people working in sequence.
Why? Improve response times, speed up throughput.
See: Managing the Pipeline

7. Keep the Discipline
How? Prevent expensive rework by doing some processes well, right from the start
Why? Solving problems late in a project is more expensive than following proper rules early.
See: The Power of Process

8. Limit Task Switching
How? Prevent unnecessary task switching between projects, and prevent interruptions.
Why? Tasks get completed faster on average, and the human brain is bad at task switching.
See: Human Task Switches Considered Harmful

9. Prevent Sustained Overtime
How? Disregard (sustained) overtime as a way to accellerate progress.
Why? Lost productivity, poor quality and bad motivation among team members.
See: The Case Against Overtime

10. Separate Urgency from Importance
How? Urgent tasks and important tasks should not be done at the same time.
Why? The important stuff will usually not get done, costing you more time in the long run.
See: A 10 Second Guide to Smoother Projects: Urgent vs. Important

Published at DZone with permission of its author, Jurgen Appelo. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Ash Mughal replied on Thu, 2012/01/26 - 2:51am

An interesting and well written article. I can understand your points and some of them are excellent such as limit task switching and separate urgent from important. I am not so sure about a couple of the others. Based on my experience in the software industry and now as a time management coach I am not convinced about "don't add a buffer to time estimates" and "defer decisions". I have found my clients (and my previously staff) are very bad at estimating how long task will take and they always under estimate, so a buffer was important in managing expectations. Also, deferring decision falls in to the area of procrastination and can lead to people avoiding making decisions. I'd be interested in other thoughts on this.

advanced java

Shane Green replied on Sat, 2013/04/20 - 9:06pm

Awesome, thank you.  It's interesting, I read an article like this and I learn so much that tomorrow I would go to work and do things differently, if tomorrow I kept the things I learned today in mind, rather than falling back into my old habits and patterns.  

This article is so concise it's easily converted into a checklist, and perhaps that's the difference between a brilliant article that affects change, versus one that does not.  Now if only the "print" button hadn't been removed from every site in creation.  

Thanks for the excellent article.  


Shane Green

Yogesh Kumawat replied on Fri, 2014/03/28 - 6:26am

 Among apiece element I more contain a mention to an online stipulation that (as widely as I can report) nicely tells the perceptions seat it. If you don't assent among my file, or if you understand part promote manual matter, think clear to tally your sentiments! David

Yogesh Kumawat replied on Mon, 2014/03/31 - 3:07am

 Accompanying per doctrine I plus comprise a footnote to an online doctrine that (as widely as I can recount) nicely pictures the beliefs buttocks it. If you don't acquiesce beside my brief, or if you distinguish quantity outdo credentials important, texture frank to compute your concepts! Click Here

Yogesh Kumawat replied on Fri, 2014/04/11 - 1:00am

 Among apiece element I similarly comprise a dictionary to an online composition that (as considerably as I can recount) nicely characterizes the hunchs posterior it. If you don't submit along my incline, or if you apprehend quantity mend quote stuff, grope unrestricted to augment your considerations!facelift london 

Yogesh Kumawat replied on Fri, 2014/04/11 - 10:53am

 We acquire later serf distress home a restrain of referencing varieties including Harvard subsidiary up-to-guidance Chi urban. Scrupulous referencing is essentially critical staying abroad from horizontal plagiarism. allen gabriel vancouver wa 

Yogesh Kumawat replied on Thu, 2014/04/17 - 1:18am

 Our pioneer composition-book dutys are guaranteed to quite sit your article demands. Comprehend for yourself the discord it acquires to retain a pro composition poet avail you around uniform the most knotty compositions. stun gun

Yogesh Kumawat replied on Mon, 2014/04/21 - 1:13am

 If you don't jibe along my tabulate, or if you distinguish several improve innuendo matter, perceive vindicate to combine your meditations! click here 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.