Effective Analysis and Documentation

Project

The goal of documenting projects in Confluence is not to replace the project management applications used in the company. The reasons to store projects in the knowledge base are easy access to basic project information and traceability. There are people in the organization who did not participate in the project but who need to understand its goals and impacts. For this reason, it must be possible to quickly find the project motivation, main phases, scope, and the parties involved. The documentation should also include links to artifacts affected by the project, such as systems or processes.

NOTE

If there is a dedicated tool for managing projects in the company, the information should be automatically synchronized or only referenced to avoid duplication.

1. Project Vision

The project vision clearly states the reasons for undertaking the project, its objectives, constraints, and direction concerning the solution. In other words, it should answer:

  • Why this initiative is important
  • How we will know when we are finished
  • What the formal boundaries of the project are - how the business may change or be altered by the delivery of the project
  • What is relevant to the project and what is not

aa

It is essential to know who the customer is and who the end-users are. Also, the analyst must identify entities (inside or outside of the project) that have a key interest in it.

aa

3. Plan

To get a high-level picture of the project, it is also important to know the basic project plan, main phases, milestones, activities, and timeframes of the project life cycle.

aa