Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Scrum
Re-opened/Modified user stories and story points
Network:44



Hi,

The concern is with respect to implementation of scrum methodology where requirements are documented as features-stories and then story points are assigned to stories.

I've worked with various agile life cycle management software and typically making changes to a user story would record it in history, which in turn represents the tractability and evolution of requirements.

Now since a particular user story may get impacted as a result of adding a new feature, so it would need to be updated and reopened if new scope is added. However how should the story points be associated with this user story, so that while calculating velocity of this particular sprint only the story point additions that were done to incorporate new feature/function are used for metrics.

Is it really a good idea to open and a user story? I feel yes from the perspective of reviewing the evolution of product it should be done, but then this complicates the monitoring and controlling part while trying to ascertain various metrics i.e., velocity etc.

All inputs and thoughts would be highly appreciated.

Thanks & regards
Pawan Rai
Sort By:
Network:1611



Is a matter of your process. Nothing said that User Stories must be used and nothing said that if you use User Stories then Story Points must be used as estimation method. On the other side, if you record story changes into the same story traceability is lot unless you record version numbers or you record the story of changes in some place. And if you change something then you are not "reopening" it, is not the same than before, is other story and here is where your process to manage change takes place (my recommendation is putting in place a Configuration Management process, something mostly forgotten mainly into Agile based environments). Each time you change something that you have estimated the estimation must be reviewed, always.
...
1 reply by Pawan Rai
May 08, 2018 11:35 PM
Pawan Rai
...
Thank you Sergio,

About the configuration management system, yes the tool that we use takes care of recording the history and maintains the versions, and shows the latest version of the story. So in a way change management is also happening
Network:1897



If a story is completed (DONE) based on what is known at that time, it should remain DONE. If down the line that story's output requires modification based on newly found needs or an additional feature, a new story can be created for the missing outputs and linked to the original.
As an aside, hearing monitoring and controlling seems out of place in this context. Seems to be more of an anti-pattern while we are inside an Agile centric discussion.

But at the end of the day, choose what works for and be consistent.
...
1 reply by Pawan Rai
May 08, 2018 11:45 PM
Pawan Rai
...
Thank you Andrew.

As far as monitoring and controlling are concerned configuration management, change management is also happening at the same time, So in a way if we are making changes to a functionality covered under a user story it is more like a change request. Also since product backlog is acting like a full product functional document that can be shared with those team member that join at higher levels i.e. scrum master/lead, who need to have eagles eye view of the entire product before they start working.
Network:936



Pawan -

I agree with Andrew - if it is a change or an enhancement to a past completed & accepted story, then open a new work item for your product backlog.

Kiron
...
1 reply by Pawan Rai
May 08, 2018 11:49 PM
Pawan Rai
...
Thanks Kiron.

Just as with my previous explanation of how it relates to monitoring and controlling, if I create a new user story for this change, won't it be like unnecessarily creating more documentation against the principles of document as much as you need under agile.

However I agree with all "choose what works and be consistent"
Network:44



May 08, 2018 10:59 AM
Replying to Sergio Luis Conte
...
Is a matter of your process. Nothing said that User Stories must be used and nothing said that if you use User Stories then Story Points must be used as estimation method. On the other side, if you record story changes into the same story traceability is lot unless you record version numbers or you record the story of changes in some place. And if you change something then you are not "reopening" it, is not the same than before, is other story and here is where your process to manage change takes place (my recommendation is putting in place a Configuration Management process, something mostly forgotten mainly into Agile based environments). Each time you change something that you have estimated the estimation must be reviewed, always.
Thank you Sergio,

About the configuration management system, yes the tool that we use takes care of recording the history and maintains the versions, and shows the latest version of the story. So in a way change management is also happening
Network:44



May 08, 2018 12:39 PM
Replying to Andrew Craig
...
If a story is completed (DONE) based on what is known at that time, it should remain DONE. If down the line that story's output requires modification based on newly found needs or an additional feature, a new story can be created for the missing outputs and linked to the original.
As an aside, hearing monitoring and controlling seems out of place in this context. Seems to be more of an anti-pattern while we are inside an Agile centric discussion.

But at the end of the day, choose what works for and be consistent.
Thank you Andrew.

As far as monitoring and controlling are concerned configuration management, change management is also happening at the same time, So in a way if we are making changes to a functionality covered under a user story it is more like a change request. Also since product backlog is acting like a full product functional document that can be shared with those team member that join at higher levels i.e. scrum master/lead, who need to have eagles eye view of the entire product before they start working.
Network:44



May 08, 2018 5:09 PM
Replying to Kiron Bondale
...
Pawan -

I agree with Andrew - if it is a change or an enhancement to a past completed & accepted story, then open a new work item for your product backlog.

Kiron
Thanks Kiron.

Just as with my previous explanation of how it relates to monitoring and controlling, if I create a new user story for this change, won't it be like unnecessarily creating more documentation against the principles of document as much as you need under agile.

However I agree with all "choose what works and be consistent"
...
1 reply by Kiron Bondale
May 09, 2018 8:07 AM
Kiron Bondale
...
Pawan -

it comes down to the purpose for the documentation and making it minimally sufficient. If you have to replicate all the content which was in the original story, then I'd agree, but I'd suggest just focusing on the summary & details of the enhancement and include a reference to the original story if the team working on it needs that additional detail.

Tools like JIRA help as you could always clone the original story and modify the content based on the revised requirements...

Kiron
Network:936



May 08, 2018 11:49 PM
Replying to Pawan Rai
...
Thanks Kiron.

Just as with my previous explanation of how it relates to monitoring and controlling, if I create a new user story for this change, won't it be like unnecessarily creating more documentation against the principles of document as much as you need under agile.

However I agree with all "choose what works and be consistent"
Pawan -

it comes down to the purpose for the documentation and making it minimally sufficient. If you have to replicate all the content which was in the original story, then I'd agree, but I'd suggest just focusing on the summary & details of the enhancement and include a reference to the original story if the team working on it needs that additional detail.

Tools like JIRA help as you could always clone the original story and modify the content based on the revised requirements...

Kiron

Please login or join to reply

Content ID:
ADVERTISEMENTS

"The power of accurate observation is often called cynicism by those who don't have it."

- George Bernard Shaw

ADVERTISEMENT

Sponsors