-
When IT Is Your Company’s “Piggy Bank”
February 10, 2012
-
4 Key Things a Project Manager Must Do
February 10, 2012
-
Essential Project Management
February 10, 2012
-
8 Traits of Top Project Managers - Part 1
February 9, 2012
-
Agile Project Management - Engaging Your Customer!
February 9, 2012
-
9 Tips to Avoid Traps in Project Planning
February 9, 2012
-
Why Projects Succeed - Executive Sponsorship
February 8, 2012
-
On Customer Participation in Agile Projects
February 8, 2012
-
A Project Charter for Lazy Teams
February 8, 2012
-
The Power of Process: How Bad Project Management Kills Great Ideas
February 7, 2012
Project Scheduling Tips - Part II
March 8, 2009 | Author: PM Hut | Filed under: Project Management Best Practices, Scheduling
Project Scheduling Tips - Part II (#4 in the series Project Management Mistake - We Didn’t Have The Right Schedule)
By Lonnie Pacelli
- Make sure all your lowest level activities have a sole owner and are no longer than 40 hours in duration
- Break your project into phases that don’t exceed three schedule months
- Know the critical path of tasks through the project and keep clean finish-to-start dependencies between activities
- Make sure that your activities have associated deliverables that are relevant
- Ensure the team buys into the plan along the way; don’t do a grand reveal when the plan is complete.
- Remind and highlight team members of tasks needing to be completed within 1-2 weeks
Lonnie Pacelli is an internationally recognized project management and leadership author and consultant with over 20 years experience at Microsoft, Accenture and his own company, Leading on the Edge International. Read more about Lonnie, subscribe to his newsletter, see his books and articles, and get lots of free self-study seminars, webcasts and resources.
Related Articles
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.
- Agile Project Management
- Ask the Hut
- Certification
- Change Management
- Communications Management
- Computer Based Information Systems
- Concepts
- Corporate Transformation
- Cost Management
- Critical Chain Project Management
- Delegation
- History
- HR Management
- Implementing Project Management
- Integration Management
- Lessons Learned
- Management
- Miscellaneous
- People Issues
- PMBOK
- PRINCE2
- Procurement Management
- Program Management
- Project Lifecycle Phases
- Project Management Advantages
- Project Management Advantages
- Project Management as a Career
- Project Management Best Practices
- Project Management Charts
- Project Management Definitions
- Project Management Ethics
- Project Management for Beginners
- Project Management Guides
- Project Management Musings
- Project Management Office
- Project Management Proposals
- Project Management Templates
- Project Portfolio Management
- Project Workforce Management
- Quality Management
- Requirements Management
- Risk Management
- Scheduling
- Scope Management
- SCRUM
- Soft Management
- Time Management
- Training
- Uncategorized
1 person has left a comment
Lonnie’s ideas may work for small IT projects that don’t really need a plan. The recommendation for all projects is for the activity duration to be between 1 and 2 times the update cycle. On relatively stable major projects this could be as long as a couple of months. For more see Chapter 3 of the PMI Practice Standard for Scheduling. You can also download a stack of free scheduling resources (papers – not software) from http://www.mosaicprojects.com.au/Planning.html