My weakest area would have to be in developing the work plan. Actually, once I get started it becomes a little easier, but to have a project come to me, I do get a bit overwhelmed as to where to start, what has to be done, etc...
Often times, I go by the philosophy of "let someone do it that knows what to do." Perhaps this is a great way of thinking if I need someone to fix my car or to work on my plumbing. But I also think that this is valid when it comes to developing a new application. After all, I'm not the one doing the work. The real workers are the people in the trenches and busting out the deliverables.
That being said...Because I have "trouble" with developing the initial work plan, is it advisable to have other team members draft the work that they need to do - i.e. have them start the workplan? Or is this not acceptable?
I know, I know, I do have to do it by myself sometime and practice makes perfect. :-)
Andrew BallSenior/Head of PMO| a3g LtdAshford, United Kingdom
I find the best and most successful way is to ask the specialists on the team. They are closer to and have the technical expertise to know what needs to be delivered and can estimate based on knowledge rather than hunches.
I always insist that Project/Programme Teams hold workshops at a very early stage of the lifecycle, it can be used as team building but exercises can generate the Product List, WBS etc. The Risk Register can be instigated, entries assessed, owners assigned etc.
These should be held centrally but can at a push be virtual if necessary. These events ensure that all involved have a common goal/vision, understand what is required and breaks down barriers.
There will always be an argument over time constraints, these should be challenged as the benefits outweigh any costs. Saving Changes...
Paul NaybourFounder and Director| Parallel Project TrainingNailsworth, United Kingdom
Many project managers use a professional project planner to draw up the schedule. This can be highly effective as they can provide invaluable support to the project manager in maingingin and overview of project status.
www.projectaccelerator.co.uk Saving Changes...
Jeff ArmstrongAgile Programme & Portfolio Consultant| business-docs.co.ukLondon, United Kingdom
I've always found that a roadmap format is a good place to start in project planning - it's not too involved, and the format lends itself well to workshops.
i.e. in this case: those of us who dislike creating a large MS project gantt from scratch can start with a simpler, more intuitive diagram format - one that your stakeholders will like :-)
PM me if you'd like to find out more!
Saving Changes...
Elizabeth HarrinDirector| RebelsGuideToPM.comLondon, England, United Kingdom
You have to involve the team in preparing the work plan; as you say, they are the ones doing the work at the end of the day. They will know what to include - there is an element of trust involved but you can manage the process and ensure the best outcome for everyone.
If you try to do it all alone, you'll end up missing out tasks and finding that the team do not commit to the plan or schedule. Not a good start for a project that you want to be a success. Saving Changes...
