The purpose of an impact analysis is to evaluate the effects, both pro and con, of an item under consideration—anything from solutions to a stated problem to a pending organizational change. In order to be sure that the team understands all the ramifications of a possible change and not just the obvious ones, it's important to consider the situation from multiple perspectives.
There are many ways to record what has happened in a day. This Excel workbook records activities/events/incidents as they occur throughout a workday. At the end of the day, the diary is updated to an Incidence Log for review at the end of a period
The purpose of this document is to provide an overall ICT communication strategy and plan for internal and external communication between staff as per their designated roles and responsibilities using specific communication channels such as emails, intranet, etc. This plan identifies audiences, communication channels, frequency, messages and standards.
Looking for a better way to understand and apply the earned value concept and S-curves efficiently and effectively? Use this template in conjunction with the Earned Value: Monitoring Projects More Effectively article, which illustrates a better practice for applying earned value to analyze and report project schedule and cost data quickly and accurately.
This Interface Requirements document outlines application designs that impact application usability, which include are not limited to content presentation, application navigation and user assistance.
Now more than ever, it's challenging to schedule meetings that cater to workers in multiple time zones. The International Meeting Planner helps you choose the optimal time for your international meetings based on the number of attendees—and the local time—in each time zone. The red-amber-green color coding shows you (and the team) at a glance how friendly (or unfriendly) a suggested meeting time is for up to nine time zones.
One way to use a requirements traceability matrix is to trace the relationship between categories of requirements. An Inter-Requirements Traceability Matrix can be used to capture this information.
This document can be used to keep track of any issues that arise during the project. It is advisable to keep track of such issues, especially if they can not be solved quickly, or if many issues arise in a short time. Also, it is recommendable not to remove any documented issues once they are solved.
The issue management process is fundamental to the successful delivery of the project. It ensures that each issue identified within the project environment is documented, prioritized and resolved within an appropriate timeframe. Use this document as a framework to identify, document, prioritize and resolve your project's issues.
