PM/Manage Project

Login Register

Help!!

How to start with ManageProject.

Documentation

Documentation about project management such as the project phases or the different objects managed by a PM such as actions, requirements, etc.

Cf page.

Create a new project

The project is the root of the project management then you should create one by clicking Create project !

This action will create a new project in build () or an appplication in run () according to your choice.

You can define its OKRs (Objectives and Key Results) by clicking here (objectives) or here (key results).

Nota: Only 15 projects for each user can be created. If there already are 15 projects, you have to delete one.

Tools provided

Project's phase

Each project is created with its 5 phases :

1. Pre-project: To understand how the project can generate benefits and to estimate costs.
2. Start: Macro frame.
3. Preparing: How to Execute, monitor, control and close the project.
4. Work: Execute the planed project to complete the objectives.
5. Closing: To archive data collected during the project and close the project.

You can see phases by clicking on phases.

The stakeholders , inputs , tasks and outputs are pre-filled.

You can remove a stakeholder, input or output by clearing his role and name (for stakeholder) or name and URL (for input or output).

The tasks are pre-filled with the phase's outputs. For each task, you have to complete with the RACI: Responsable, Accountable, Consulted and Informed. You can add to it a period to get alert on the dashboard about tasks in progress.

Alerts

When the project or application (run) is on fire!!

You have to fill a description, the fire's impacts, why it is an alert and how this alert will be set as ended. It also keeps record of the local decisions.

You can also create actions to reduce this alert (specifically linked to this alert) and monitor them.

For applications (run), you can also link the alert to a version.

Cf page.

Risks

To keep project or application (run) risks to a minimum !!

Fill the risk's probability to occur and the impact level. The risk score is evaluate. If the score is high, you should add actions to lower the probability and/or the impacts.

For applications (run), you can also link the risk to a version.

Cf page.

Defects

To manage the defect and keep the project or application (run) quality !!

To create a new defect, you must describe the steps (and the environment) to reproduce the issue and what is expected.

You must qualify the defect, if it is blocking (primary service is no more available) and on the prod environment, this defect must be resolved very quickly.

You can manage the defects from the creation to de deployment with the status.

For applications, you can also link the defect to the detected version and to the solving version.

Cf page.

Budget

To manage the budget and keep the project or application (run) on tracks (funds and schedule) !!

You can add a new funding to the project. A founding is for a specific project phase.

You can keep the records of the done/cost at date and the CPI (Cost Performance Indice)/SPI ( Schedule Performance Indice) calculated by clicking on "Add current situation" icon and fill the current and expected percentages.

For applications (run), you can also link the budget line to a specific version.

Cf page.

Follow up

To communicate the project or application (run) progress (or its lack) !!

You can add a new follow up to the project with the general trend, the near past, present and future.

It also can be used to keep records of the taken decisions and to put forward the decisions to be taken.

Cf page.

Actions

To manage and to keep log of the actions for the project or application (run) !!

To be managed, an action must have a deadline and a person in charge.

An action can be linked to an alert, risk or an assumption. If an action is linked to such object, it has to be created in the linking object.

Cf page.

Requirement

To keep what is expected for the project or application (run) !!

It has the frame of the stories: AS xxxx I CAN xxxx IN ORDER TO xxxx, but there are not sorted.

You can specify the gained value (useful to prioritize) and set a priority (could/should/must).

Cf page.

Change requests

To keep record of the changes for the project or application (run) !!

The change is requested by someone to get gains. The impacts must been evaluated and the change request must be rejected or approved before the deadline.

After an approved change request, the requirement should be updated (and maybe the budget).

Cf page.

Assumptions

To manage the assumptions and to keep record of them during the project or application (run) !!

Assumptions are hypothesis taken by the project. These assumptions need to be checked for the project to be more accurate.

To verify assumption, actions can be add to it.

Cf page.

Decisions

To share the decisions and to keep record of them during the project or application (run) !!

A decision is taken by someone and has an effect date. You can add the issue and the choices led to the decision.

Cf page.

Documents

To keep trace and access to the application's (run) documentation every time!!

A document must have a name and a type, it should have also a link and a application's (run) version.

You can also keep the track of the version of a same document by using the "add a new version of the document" function. The document's type will stay the same.

Note: Only the last 20 version's documents are listed in the document.

Note 2: For the projects, the document are in the input and output phases.

Cf page.

Versions

To know to the application's (run) versions.

It has a type (evolutive/corrective and major/minor), and you can track his status (work, deployed, closed).

Cf page.

Environment

To know the run's environments.

It has a type (dev, test, prod), and you can add what version is on the environment.

Cf page.