10 Signs You Don’t Really Know Microsoft Project
December 25, 2007 from PMConnection
1. You manually create a Project Summary Task
Wrong:
2. You "hard code" dates
Wrong:
3. You don't input the teams estimated Duration on all tasks
Wrong:
4. Your tasks don't start with a verb
5. You assign Predecessors to Summary Tasks
Wrong:
6. You assign Resources to Summary Tasks
Wrong:
7. You never inspect the critical path tasks
8. You never search for (or eliminate) Resource Over-Allocations
9. You never Baseline your schedule
10. You never update your schedule to align with reality
For help with Microsoft Project, try this link
Social Bookmark this page
RSS Feed for Exclusive Articles
This article is syndicated from PMConnection
. The original article is available here. Read more in PMConnection, Project Management News .
No tag for this post.
Popularity: 1%
Reminder : PMToolbox has ZERO tolerance to copyright violation and agrees to follow strictly PMI's Professional Responsibility. That's why each post on this site includes a link to the original version at its source site.
Comments
Got something to say?
[?]
Type in a relevant tag, and click the button, and help organize this blog's information.
[More Help]
[More Help]
EV
Crm Applications
Education and Training
Information Engineering
Project and Program Management
Microsoft Project
Estimating
Tools
application portfolio management
templates
Methodologies
sharepoint
Deliverable Templates
Prince2
Application Development Methodology
MS Project
Project Office
Construction
associations
IT Service Management
EVM
Business Intelligence Tools
Cost Benefit Analysis
SPI
IT governance
Knowledge Management Processes
Program Management Office
Package Selection
best practices
portfolio management
Software
PMO
Project Management
Information Technology Planning
enterprise architecture
Hosted
metadata
Systems Development
Earned Value
Resources
Risk Management Programs
Industry-Specific
ITIL
CPI
Articles
