Comments for A Day in the Life of a Project Manager: Issues, Insights, & ImplementationFollow one Project Manager through the daily ups and downs of the Project Life. Larry draws on his current project management practice and wealth of project experience to shed light on the issues and challenges of project management today. His eye for detail, sense of humor, insights, and personal observations are sure to entertain and inform.Comment by Larry Cone on Letter to a PM - What is MS Project good for- August 26, 2008 Just re-read my RANT - the blog entry that started this thread. I really had a head of steam up - must have been right after a particularly messy project status review. I agree with Hotsam that level of detail is a common culprit with MS Project. Ive done it myself, using the task list in the project plan as a to do list, or a list of things I dont want to forget. Thinking more about process steps, particularly checkpoints rather than tasks makes for a plan that is easier to execute.http://networking.ittoolbox.com/r/rss.asp?url=http://it.toolbox.com/blogs/coneblog/letter-... Comment by hotsam on Letter to a PM - What is MS Project good for- August 26, 2008 Even though MS Project is a piece of garbage, and is usually only used because it is the cheapest option, it is not the problem. Much of the problem lies in the level of detail that is in software development schedules. It's impossible to plan out a schedule at a low level of detail when the tasks are level of effort (LOE). LOE tasks are not discrete, have no firm start and finish dates, and don't belong in a schedule. A schedule is not a checklist. If you define your work packhttp://networking.ittoolbox.com/r/rss.asp?url=http://it.toolbox.com/blogs/coneblog/letter-... |