The things I've read about agile say, "use what works." I take that to mean the document should be of length and detail commensurate to the task. Now, there are some misconceptions out there that agile means "no documentation or analysis at all" but that's not the case. I believe with any documentation that the agile approach is a good one. Note that the cost may be included in the factors or the PM may have another opinion. Finally multiply and sum score*weight and choose the best. Then give each factor weight and give every solution score in each factor. In the DAR form you should add some evaluation factors like future maintainability or other factors that are not included implicitly in the impact analysis. Also, if you need to do this to choose between several fix solutions to solve the bug, you will need to repeat the impact analysis for every possible solution and consolidate all data into one Decision Analysis and Resolution (DAR) form to know which solution is the best. We used this with CRs but you can use it with bugs the same way. Similarly, the PM needs all the information to know the cost and schedule. ![]() We used the above order because the designer will need to know the the impact from analyst point of view to get better insight of the change and so does the tester need to know the opinion of the analyst and the architect. If you have Bidirectional Traceability Matrix it will make it easier. ![]() To cover all possible impacts you need to walk through the dependencies. Estimation and Impact on Schedule: The project manager estimates the effort needed and the cost of the change and the impact on project schedule.Impact on Test: The QC writes the test cases need to be updated.Impact on Design and Architecture: In this section the architect and the designer mention which parts of the model need to be modified or redone to support the change.Impact on Requirements: In this section the Analyst writes what needs to be changed in the Use Cases to support the change requested.We use it to evaluate Change Requests and before working on them (and possibly to reject some). ![]() The templates I have seen for impact analysis where made inside the company I work for.
0 Comments
Leave a Reply. |