Linking Incidents to Stories? Is this good practice?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2014 07:00 AM
Hello,
Currently we have a process where by a Story (SCRUM) can be created from the Incident module. We have now had a request whether it is possible to link multiple Incidents to the Story. Generally is this best practice? I have managed to add the Incident tab to the Story form as a related list however depending on the permissions only some incidents are available to add to the story.
Any advice would be useful,
Thank you in advance,
Hong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2014 10:09 AM
I don't see why not. Its easy to imagine a bunch of people simultaneously reporting an incident which requires development to resolve. In such cases, why not have each relate to a story. You could use that quantity of Incidents reported as a metric that drives which stories to work on even.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2014 04:58 AM
I'm wondering if it is more logical to link an incident to a defect.
You could however link several incidents to a problem or a change then link those to some stories.
One thing is sure. SDLC is to be use on a project.
A story is an expressed requirement for a functionality that is produced on a sprint.
You may want to know where the stories come from (generally from workshops but why not). It will definitely not come from an incident..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2014 09:57 AM
I disagree. I think its hard enough teaching IT what an Incident is and practically hopeless teaching a business culture. With more and more adoption of ticket submission portals, people use inappropriate vectors of entry all the time. We might, from our ivory tower, decide that someone should have used an existing Catalog Item to order ServiceXYZ, but instead they used the "report an issue" button and created an incident because they didn't know the difference.
Unless one builds a fancy task conversion utility, or manually recreates these things when they come in, I suspect a lot of requirement descriptions and feature enhancements will come in via Incident whether its an ideal world or not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2014 12:45 PM
Thanks for your reply
Do you really disagree?
Why don't you link incidents to defects and .... enhancements like rfedoruk said.
Keep the stories to your projects and link them to sprints.
If you do a new release of your application, you can add as many defects and enhancements you want in your release.
and these defects and enhancements may come from incidents.
Im eagerly waiting for the next reply from the ivory tower.