C4084da9193caafee84540a0ee009c174bfcaa5b

Hi,

These are the steps for each change or issue:



  1. Capture: the first step is to identify and document it. We usually have an issue register used to capture them, along with everything related to them. 


  2. Examine: so, how is the change or issue is going to affect our project? How soon should we react?


  3. Propose: what options do we have? What are the consequences of each option? Which one is the best?


  4. Decide: based on the importance of the matter and tolerances, who should decide about it? Let that person decide.


  5. Implement: now we should implement the selected option and continue recording its result in the register.

Most of these are not possible or effective without having a proper configuration management system. This system documents all the building parts of the product, and their related information, along with dependencies between the elements. So, when one element changes, we would know what other elements might change and we can check them. This makes the “examine” step possible. Besides that, it captures the whole history of the product and is used to make sure nothing is missed. 

Our last theme is progress. How do you measure the performance of the project? Let’s say you can only provide two pieces of information for the performance; what would you choose?


Regards,

- Nader