Non-functional Requirements in Scrum

How should we handle reliability, availability, portability, scalability, usability, maintainability in Scrum product backlog?


These are constraints which should be part of either the Tasks of a backlog item/user story or acceptance criteria.

Example - Data migration projects where no business functionality/features are there we just need to create a utility which will migrate the data. For such requirement, we can create a user story which is to create the utlity which will allow me to handle the data migration and its tasks should have the constaints like reliability, availability, portability, scalability, usability, maintainability.


Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros
Read more