Written by Lindsay Curtis
Lindsay Curtis writes about communications, education, healthcare research, and parenting. She has extensive experience as a Project Manager, primarily in the healthcare and higher education sectors. A writer by day and a reader by night, she currently works as a Communications Officer for the University of Toronto. She also provides freelance copywriting and social media strategy services for businesses of all sizes. Learn more about Lindsay at www.curtiscommunications.org.
Have your say!
00
You May Also Like
1 Comment
Leave a Reply Cancel Reply
You must be logged in to post a comment.
Walter Boggs
For software projects and other types of knowledge work where the schedule and task details are changing often, aim for a resource plan that is tied to high-level activities only. Try to get key resources who are dedicated to your project for longer blocks of time, and then make it your business to ensure they always have the right work to do. Fiddling with schedules is bad enough without also having to micro-manage a resource plan.
Of course, this approach suggest lean and agile PM processes, but if you’re stuck with waterfall, think lean anyway.