This week the tweets covered the top tools and artifacts I like to use when managing a project. Next week will be part two of this series.

Tool # 1- Status Reports. Not just a report but also a call to action for executives and sponsors. Brings focus to milestones, budget, risks. Tip – There should be one and only one template for status reports used in the organization! Consistency is important for stakeholders.

Tool #2 - Risk Log and Management Plan Used to identify risks before they become issues and define strategies to deal with them. Tip - The Risk Log should be reviewed regularly and updated. I like to assign this to another team member to bring added focus to it.

Tool #3 - RequirementsTraceability Matrix. Provides a great way to ensure all requirements are covered throughout the project. Tip - The requirements traceability matrix should be organized by major functional area. Also include technical, security, and usability requirements.

Tool #4 - Scope Statements. Usually found in the charter. They serve as the anchor for the projects deliverables. Tip - I usually will copy the scope statements from the charter and put them on a seperate document to make it easier to socialize them to the team, stakeholders, and the organization.

Tool #5 - The Project Plan. Details how the project will be executed and managed. Contains the sub plans such as communication and QA plans. Tip - The project plan should only have the sub plans needed. Smaller projects do not need all of the sub plans that larger ones do.