Neha_Varshneya

 Profile Answers by Neha_Varshneya 

• Oct 8th, 2007

 

If you have a proper change management control process planned for your project it shouldn't be a big deal then. This process should be planned at the very beginning of the project itself. So, if your customer requests for any change you just follow the process and analyze the impact of this change on your project's budget and schedule and depending on that either accept the request or reject it. What is more important is to have a preplanned formal control process for any scope changes to your project that should help even if you have a team of 10 and would prevent the scope creep.

goksn

 Profile Answers by goksn 

• Aug 28th, 2009

 

For change control, we need to see two sides

Impact within the project (among the modules within the project)
Impact within the other projects of the organization (If applicable).

For any change control process, we testers need to ask the following questions,

- What is the need for the change-business wise?
- What is the need for the change-technically?
- What is the impact on this change within other systems of our organization (if it is any)?
-How much this change will take to implement (to deploy in production system)?
-When are you going to deploy?
-What are all the modules are getting affected?
-What are the business areas are getting affected?
-Is unit testing done for this change?
-Is black box testing done for this change?
-If anything goes wrong, what is the procedure for revert the change and making the system as it was?
-Who is the development responsibility?
-Who is the testing responsibility?
-Who is the immediate support resource and their contact mail id and contact number? (24/7)