In this walkthrough, we will guide you through the management of our project, providing a recommended reading order for the documents in the management section. This document will also help understanding the documents in the management section and how they are related to each other.
As we are already using GitHub as a common platform for our project, we decided to use it for our management documents as well.
GitHub Issues will be used to track tasks and assign them to team members. An issue will be similar to a ticket and each issue will be associated with a milestone.
The GitHub Project feature will be used to create boards that will help us track the progress of the project.
The first document you should read is the Gantt Chart which provides a visual representation of the project timeline. This document will help you understand the project's schedule and the tasks that need to be completed.
Each category of task is associated to a Milestone on GitHub issues, where each closed issue (completed task) increases the percentage of completion of the Milestone.
The KPI's (Key Performance Indicators) are used to measure the completion of the project. You will be able to see the progress on each task week by week as well as the overall progress of the project.
After taking a look at the milestones, we recommend reading the RACI Matrix to give you an overview of the project member roles and responsibilities. This document will help you understand who is responsible for what and who should be consulted or informed about project decisions.
We are committed to having effective risk management systems (including frameworks and processes) to identify risks and anticipate them or limit their impact on the project. The Risk Management Plan will be used to define this strategy.
The Risk Management Plan is tightly linked with the Risk Matrix. This document is used to list the risks we raised and how we plan to manage them if they occur. It also precise the responsible people for each risk.
To conclude this walkthrough, the Weekly Reports are documents written every week which contain information about what was done during the previous week as well as the current status of the project and feedback about how the team felt.