project flow & tracker

General Analysis

Analysis is not so effective if it is not  intimately associated with a code sprint itself (that is, itself done in an incremental and iterative manner). However, I did want to get a "total immersion" mindset before starting out. To do so I reviewed:

Feedback from previous PFT users

Roadmap from DrupalCon Barcelona 2007 presentation

Input from bibliography

Process toolsets

Drupal architectures

Project Flow & Tracker Barcelona (2007)

So over the past couple of years I have been working on web applications using the Drupal CMS as a web application framework, and I have used a lot of project and configuration management tools in the past. But excited about a year ago with using Drupal itself as a project management tool and a rapid prototyping tool at the same time, I developed the Project Flow and Tracker, designed to be a Drupal installation profile (in case that doesn't translate instantly and intuitively into something for you, it is a downloadable Drupal, which, when you download it and install it, will become a Project Flow and Tracker instead of just a plain vanilla Drupal installation).

So I went to Barcelona DrupalCon in late 2007 and gave a presentation on it and got a lot of really cool feedback. And, I actually used it with some clients, and got a lot of really useful feedback there.

Enough time has passed for a couple of things to happen:

Drupal itself is much more powerful (panels 2, nodequeue, jquery ...) and the ideas have had some time to mature pretty well.

Project Flow & Tracker Washington: The Making of (early 2009)

This is a log of how Project Flow & Tracker was built.


Drupal with Agile

Drupal on agile, agile on Drupal

Agile basically means getting it done right. It does for getting it done what object oriented analysis, design and programming does for software:  it divides all the complexity into bite-sized chunks.

So if your project is set up right, you find yourself bleary eyed in the saddle on a Monday morn, with the definite idea of putting your shoulder to the wheel, but without any idea at all of where (it costs too much to redo the thinking five times); but you can fire up something (whether it's a spreadsheet, a sophisticated application, dotproject, whatever), but you got yourself a Google map on all your clients, projects, phases, milestones, tasks, tests, days, so you can Zoom out and dizzyingly zoom in on what you got to do right now. Then at some point soon, and the easier the better, the lowest cost in pain and time the better, at some time you have the equivalent of a pile of tasks to do, that you can just do and cross off as having been done and you have that sweet feeling of having really moved along.

Syndicate content