Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.
How Long Is It a Project?
Jamie Phelps | Jul 22 2006
OK, this might sound stupid, but that's why I'm here, right? It's probably easiest to explain what I mean with an example. I redesigned a website for my church. The Project was to finish the redesign. That's done. Now, I am mostly responsible for keeping content updated and such until I can have a training session with the staff for the CMS after a big conference we are hosting the first week of August. So, the question is this: Is "Church Website" still a project? If not, do I just stick my NA's on context cards (hPDA, baby!)? I am in a similar situation with a site I finished for a client a while back. I still do periodic maintenance, and they just asked me to do some design adjustments as well. Is this still the same project? Is it a new project? Somewhere in between? I realize I could just keep adding stuff to those project cards, but it seems to defeat the purpose really of having a specific goal in mind. Why bother with a project list at all if it's just going to go on ad TIA 9 Comments
POSTED IN:
 Almost my entire work life...Submitted by andyc on July 31, 2006 - 12:43am.
Almost my entire work life falls into this way of working, since I rarely get to hand something over when I finish the initial implementation. There is usually something that can be defined as the deliverable of the project: when that's handed in, the project's done as far as I'm concerned. Any follow up is either a single next action (sometimes) or a new project (in GTD terms) in it's own right. Works for me, YMMV. » POSTED IN:
|
|
| EXPLORE 43Folders | THE GOOD STUFF |
