Back to Forum

Need help to fulfill story status related requirement

Last post 03:17 pm March 30, 2020 by Ian Mitchell
3 replies
vishal Rajadhyaksha
12:57 pm March 30, 2020

We decided to have below statuses for user story -:

1. Yet to be started

2. In Progress

3. In Testing

4. In UAT

5. UAT Done

-------------------------------------------------------------------

6. Candidate for Release Testing

7. Release Testing Done

------------------------------------------------------------------

Now, for status 6 and 7 we have separate board. 

What we want is - : While closing the sprint, all stories in "UAT Done" status should get moved to "Candidate for release Testing" status in next sprint.

 

 

 

 

Ian Mitchell
01:08 pm March 30, 2020

What we want is - : While closing the sprint, all stories in "UAT Done" status should get moved to "Candidate for release Testing" status in next sprint.

What would that mean in terms of developing a fully tested increment of release quality during the current Sprint?

vishal Rajadhyaksha
01:36 pm March 30, 2020

What would that mean in terms of developing a fully tested increment of release quality during the current Sprint?

It means in current sprint we are not providing anything of release quality. I agree.

But, Release Testing happens once in 3-4 months. Client wants to visualize all items on board which are candidates for Release Testing. 

So, what options do I have ?

Ian Mitchell
03:17 pm March 30, 2020

Why not start by putting transparency over:

  • the fact that Scrum is not currently being implemented,
  • there are no Sprints happening yet at all, and
  • there must be deep and pervasive organizational change if the benefits expected of Scrum are to accrue.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.