Change Impact Analysis in Agile Development (original) (raw)

Any change that will influence the system’s safety requirements after we have finished the safety analysis and safety planning for development of safety-critical software will require a change impact analysis. One of the reasons for using Scrum is its declarations to “embrace change”. Using agile development we may add new requirements, change existing requirements and make current requirements more detailed both in the product backlog and in the sprint backlogs. Problems, methods and necessary reports related to the consequences of such changes have been discussed and analysed in the SUSS (Agile Development of Safety Critical Software) project. We have come up with an extended Scrum model which includes the change impact analysis for all potential changes to the Scrum backlog. In addition, we have designed a change impact analysis process plus a template for a change impact analysis report. Before we entered the software development part of the project, which is Scrum’s domain, we ...

Sign up for access to the world's latest research.

checkGet notified about relevant papers

checkSave papers to use in your research

checkJoin the discussion with peers

checkTrack your impact