Project plan vs problem solving
- Thread starter Gideon
- Start date
GTD & Project Management Methods
Gideon,
From a GTD Point of view a Problem usually leads into a project, for example a problem may be that the Garage is untidy and needs to be cleared out which would be captured as a thought as part of the capture phase.
A Project would then be created when time/energy available - Garage Tidy Project, next actions might be to sort through a cupboard, then to put identified trash out, stuff that could be sold/ebay'd, etc.
You could also think of this in terms of the Problem being the Objective of the Project.
From a Project Management Point of View, a problem could be something unforseen when the project was started, which would then be managed using an issue log, which would detail what the identified issue is, , what the impact of that issue is and what countermeasures can be put in place to reduce the impact or risk on the project.
As an example, computer hardware/software required for a project is being quoted on a longer than average leadtime from the preferred supplier, which would be the issue. The impact would be a 2 week delay on the project, countermeasures would be try to source from an alternative supplier or source an alternative product.
Hope this helps.
Gideon,
From a GTD Point of view a Problem usually leads into a project, for example a problem may be that the Garage is untidy and needs to be cleared out which would be captured as a thought as part of the capture phase.
A Project would then be created when time/energy available - Garage Tidy Project, next actions might be to sort through a cupboard, then to put identified trash out, stuff that could be sold/ebay'd, etc.
You could also think of this in terms of the Problem being the Objective of the Project.
From a Project Management Point of View, a problem could be something unforseen when the project was started, which would then be managed using an issue log, which would detail what the identified issue is, , what the impact of that issue is and what countermeasures can be put in place to reduce the impact or risk on the project.
As an example, computer hardware/software required for a project is being quoted on a longer than average leadtime from the preferred supplier, which would be the issue. The impact would be a 2 week delay on the project, countermeasures would be try to source from an alternative supplier or source an alternative product.
Hope this helps.
Gideon;71109 said:
I say: No.
A project plan is your initial approach for solving a problem.
The actual process of solving the problem usually does not follow the plan exactly. Life's too messy.
This is why GTD has a Project (goal) and a Next Action. Because so much can change between the Next Action and completion of the Project, GTD doesn't force you to plan that out rigidly. You can come up with whatever plans you want, but you only need to record the goal and the next step. The plans can change, as they should.
I say no, a project plan is only the first part of your problem solving, not the whole thing. It is your initial approach for solving a problem.
Oogiem
0
Gideon;71109 said:
Not to me.
Project planning is what you think will work to accomplish your goal and how to go about doing it. Problem solving is for when Murphy shows up.
Example from my life:
Project plan is
Put scale into sheep chute
Run sheep into sweep
Take weights in chute
Problem solving is
Sheep won't step on scale because they slip so find a bit of pond liner rubber I forgot to put into the trash and use it to make a less slippery step.
Lambs can wriggle out under the chute and get into the wrong sort pen so get small jug panels and tie them onto the chute sides using baling twine.
