I realize that project management and project delivery can – at times – seem like it’s all about detail. Detailed requirements are needed to document a proper scope for your engagement. Without good, detailed requirements you could end up delivering an end product or solution that your customer doesn’t want and their end users can’t use. Detailed communication is necessary to properly convey critical information to team members and to project clients. If we miss the mark on effective and efficient project communication we may send project team members down the wrong path on their assigned tasks, costing the project valuable time and money that can’t afford to be wasted.
Likewise, detail on project status reports is usually desirable as those project status reports are commonly the most distributed and observed piece of project data and information week in and week out. If we aren’t producing detail in our status reports, how will customers and key stakeholders be made aware of what’s happening on the project, what the financial health of the project is, where the project stands in relation to it’s anticipated delivery schedule, and what issues are being dealt with at any given point in time?
Likewise, detail on project status reports is usually desirable as those project status reports are commonly the most distributed and observed piece of project data and information week in and week out. If we aren’t producing detail in our status reports, how will customers and key stakeholders be made aware of what’s happening on the project, what the financial health of the project is, where the project stands in relation to it’s anticipated delivery schedule, and what issues are being dealt with at any given point in time?
RSS Feed
