Most of them are probably in the 300 range. But we have some projects that span a year or so. So they'll be closer to 900. We have two Templates we created in WF (one Waterfall, one Agile) that the PM's use as a starting point. In the Template, we have the Milestone Tasks & Approvals already set and links to documents in tasks that would require a document. For example, the Task to Create a Project Charter has a link to our Project Charter Template. Predecessors are set as well. Then the PM would modify it to suit their project (add, change, and delete tasks). Update the estimates (Duration and Planned Hours). They should be adding details about the task in the Description (but they don't always do that J ). As a rule of thumb that I learned on Task Names, all Tasks start with a verb. It was a neat trick I picked up somewhere. It helps with clarity. For example, I used to have a task that simply said "Requirements". Well what does that entail? Am I gathering requirements? Writing them? Drafting them? Finalizing them? Obtaining sign off? When you add the verb it makes it more clear and it usually becomes obvious that you need more than one task. In this example, I would want to gather reqs with the business user, write them, re-verify them with the user(s), and obtain sign off. So one task can become four. Some may say just include them all in one task. But that gets hard to manage and track where you're at (especially on larger efforts). And putting them in one task would usually be underestimated. When it's broken down, you get better estimates. Number projects per PM depends on the size of the project. We have one very large project, so that PM gets only one project. But in general, most PM's have 2-4 projects. Vic Alejandro, PMP, CSM | IT | Sr. IT Project Manager Denver Water | t: (303-628-7262) | c: (303-319-6473) "http://www.denverwater.org/">
http://www.denverwater.org INTEGRITY | VISION | PASSION | EXCELLENCE | RESPECT
