Change Management

Thank you for your product ! I really enjoy the integration.

Changement Management or "Integrated changes" is an important subject in a project. The only place I found to centralise this information is to crete a section in the document.
But it would be nice to have a special place to document the change, analyze the impact, Evaluate, get approval or rejection and have a follow up if the change correcte the situation or not.

What do you think ?

Thank you

Nicolas

Hi,

Hi babynus,

Thank you for taking time to response. !

Yes it is a nice "Opportunity" and I was starting to analyze how it can be implemented in ProjeQtor.

First of all when I talk about "a section in the document" I was refering to a "Type of Documents" in order to group changes together.

If you ask ... Here is what I have in mind.

In terms of links

• A change is linked with one and only one project, but might be related with one or several activities.
• A change can be linked with a contract too or an order in ProjecQtor
• A change can be linked to one or more Risks
• A change can be linked to one or more Decisions

In terms of life cycle +- Status

• A change must be "Documented" (Name, Description,,
• "Evaluated" the following information should be feeded: Effort +- days/hours, Resources types, (1 days of Analyste, 3 days of programer), Impact on Scope (y/n) and the impact description, Impact on the Schedule (y/n) and a number of days/hours, Impact on Cost (y/n) and Amount,
• "Approved or Rejected" when approved or rejected the user should be able to explain why ! The most important time is when it is rejected ,
• "Implemented"
• and then "Closed" The following information should be documented : If the change fix the issue (y/n/partialy) and a description if the change did not fix completly the issue.

In terms of implementation

• It's very similar to a Risk. I would add "Changes" in the same menu as "Risk&Issue Management"
• I would use the same attributes as the Risks excepted I would remove : Likelihood, switch description with cause
• I would add "Approvers" on top of "Treatement"
• In the Treatment I would change Handled, done closed by Evaluated, Approved or Rejected, Implemented, Closed (Done could be used for Implemented, Cancelled for Rejected)
• In the Treatment Iwould add a description field near "Cancelled" to catch why the change has been cancelled

In terms of reporting

• I would use this information to justify/explained whay the project did cost more are take more time
• I would like to print a list of change with the total Amounts and the total of days...
• I would track changes by status..
• I would include this informations in the status meeting as I will do for the Risk.

Voila Voila ....