How to reduce user story reopen count in scrum development?

Vinod Kumar Chauhan*

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contribution book

1 Citation (Scopus)

Abstract

A user story (US) is reopened for reworking due to shortcomings from four major fronts-business analyst (BA), developer, quality analyst (QA) and environmental issues. BA is responsible for capturing requirements and documenting the requirements in the form of user stories; developer is responsible for the implementation of the user story; and the QA is responsible for testing of US. Now if any of three does not perform his job accurately then the probability of reopening of US increases. So we can reduce the probability of reopening of US by improving on shortcoming from three ends BA, developer and QA. As for as environmental issues, are concerned, they can be controlled by QA, developer and BA. The aim of the paper is to identify different areas from BA, Developer and QA's end to reduce the probability of reopening of a US and thereby reducing the user story reopen count in the Scrum development.

Original languageEnglish
Title of host publication2015 International Conference on Computing for Sustainable Global Development, INDIACom 2015
EditorsM. N. Hoda
Place of PublicationPiscataway, NJ
PublisherIEEE
Pages2204-2208
Number of pages5
ISBN (Electronic)9789380544168
Publication statusPublished - 4 May 2015
Event9th INDIACom; 2015 2nd International Conference on Computing For Sustainable Global Development, INDIACom 2015 - New Delhi, India
Duration: 11 Mar 201513 Mar 2015

Conference

Conference9th INDIACom; 2015 2nd International Conference on Computing For Sustainable Global Development, INDIACom 2015
Country/TerritoryIndia
CityNew Delhi
Period11/03/1513/03/15

Keywords

  • bug
  • bug reopening
  • business analyst
  • developer
  • quality analyst
  • scrum
  • user story
  • user story reopening

Fingerprint

Dive into the research topics of 'How to reduce user story reopen count in scrum development?'. Together they form a unique fingerprint.

Cite this