Getting Things Done – The Book

This is an article providing a summary “book club” reading of Mr. David Allen’s  “Getting Things Done”. I’m reading from the 2001  Penguin Books edition.

This is also the second book in my 2008 business books reading list.

This is a very famous book, the method described here by David Allen created a small sensation and got rapidly many thousands of fans. Therefore it’s quite difficult to say something new about the book or the method, you can find it everywhere in internet. I will just limit the post to a small summary and will describe in  a later post how I applied the method to my own work.

The scope of the book is to permit people to function productively even with an overwhelming number of things to do (due to what Peter Drucker termed “the knowledge work”), thanks to a method based on two key objectives:

  1. capturing all the things that need to get done into a proper system
  2. disciplining yourself to make front-end decisions about all those inputs
"the workings of an automatic transmission are more complicated than a manual transmission,
[t]o simplify a complex event, you need a complex system".
[Allen in Wired, 2007]

The method basic requirements are :

  1. you cannot fully trust your memory; anything you consider unfinished must be captured in a trusted system outside your mind that you know you will come back to regularly and sort through.
  2. you must clarify exactly what your commitment is and decide what you have to do to make progress toward fulfilling it.
  3. Once you have decided on all the actions you need to take, you must keep reminders of them organized in a system you review regularly.

The workflow process consists of five distinct phases (every phase described in a separate post):

  1. Collect
  2. Process
  3. Organize
  4. Review
  5. Do

Project Management – 1: What is a project?

This is a first post in a series where I will write down what I learned about project management.

It will contain general advices inspired by the PMI Body of Knowledge (PMBOK) but tailored to software projects as well with practical examples from waterfall, iterative and agile methodologies.

First of all What’s a project?

A project is defined as a temporary effort aimed to create a unique deliverable.

Temporary means that every project has a definite beginning and a definit end; i.e. the duration is finite.
Projects are not ongoing efforts, as operational word could be or some normal software maintenance work (e.g. routinely fixing bugs on a web sites) which are ongoing and repetitive and their objective is to sustain the business.
The objective of  a project is to attain its deliverable and then terminate.

A deliverable could be a quantifiable product (as a new mobile phone but also intended as a software feature or an update), a capability to perform a service (as a new business function, for example a customer service) or a result (as a document showing if a current trend is present or not).
Uniqueness is an importan attribute, even if some features in a web application have repetitive elements, the project work remain unique.

Finally, projects – because of the above characteristics – cannot be addressed within the organization’s normal operational work but need a strategic consideration.

Table of Contents after the jump