RACI Scrum Model for Controlling of Change User Requirement in Software Projects

Requirement’s evolution is mandatory for any software project. Users can propose requirements changes at any stage of SDLC. Although changes in requirements may affect on cost, schedule and quality of a software project; but change should be allowed when it is inevitable to meet the customer expectations. Traditional software development processes are not much efficient to manage the rapid change in requirements. This paper explains why users change their requirement and what is the impact of change in a project’s cost, schedule and quality and it attempts to decrease change in required by proposed model can do this task.

Subscribe to the Developer Insider Newsletter

From the hottest programming languages to commentary on the Linux OS, get the developer and open source news and tips you need to know. Delivered Tuesdays and Thursdays

Subscribe to the Developer Insider Newsletter

From the hottest programming languages to commentary on the Linux OS, get the developer and open source news and tips you need to know. Delivered Tuesdays and Thursdays

Resource Details

Provided by:
International Journal of Application or Innovation in Engineering & Management (IJAIEM)
Topic:
Software
Format:
PDF