This video is gold. Thank you so much for sharing your valuable knowledge. I've been looking for around 3 hours and nothing that I read or watch on RUclips comes close to the information you shared here. You are a life saver! I feel honored being your firs comment here lol
While searching for explanation of this topic I got a lot garbage results. This video should be placed at the top of youtube search results regarding this topic.
I am struggling to find how these concepts are cut into releases. It seems that both Epics and Features can span releases. I don't think 'Release' was mentioned at all. Stories and Bugs are clearly in Releases.
I would argue that since Epic should mean "too big for a sprint" that is may or may not span a release. I suggest you think of "levels of work". On the problem side, what do you want to call something that can be done by one person is less than a day? I would suggest "task". For something that can take a few people one or more days but less than a sprint?: I would suggest "story". For something that takes one or more people and longer than a sprint? I would suggest "epic". So what about feature? I would use feature to describe a solution that takes one or more people to work on, typically longer than a sprint. Our issue, of course, is that people come to us with features, we have to work to figure out why they want that feature. Turn a solution into a problem to be solved. Releases are collections of stories, perhaps epics, and features that we expect will be delivered by a given date.
Just a general architectural question. Do you link bugs from sprint/iteration 10 to Feature/User Story/Epic from sprint/iteration 5 (across sprints/iterations)? This way, DevOps can be a good documentation for a new stakeholder/QA/developer to catch up by reviewing all linked work items/features/epics since the beginning of time.
I think it is a reasonable idea to link any defect to the original story that it is a defect against. A defect, however, may be at many different levels of the functional decomposition. Some flexibility may be needed here.
This video is gold. Thank you so much for sharing your valuable knowledge. I've been looking for around 3 hours and nothing that I read or watch on RUclips comes close to the information you shared here. You are a life saver! I feel honored being your firs comment here lol
After years of reading and trying to implement... This man just rocked it! Absolutely clear and consistent.
While searching for explanation of this topic I got a lot garbage results. This video should be placed at the top of youtube search results regarding this topic.
Five Stars ***** ...This tutorial is very valuable and genius!! Thank you for taking the time to explain
I am struggling to find how these concepts are cut into releases. It seems that both Epics and Features can span releases. I don't think 'Release' was mentioned at all. Stories and Bugs are clearly in Releases.
I would argue that since Epic should mean "too big for a sprint" that is may or may not span a release. I suggest you think of "levels of work". On the problem side, what do you want to call something that can be done by one person is less than a day? I would suggest "task". For something that can take a few people one or more days but less than a sprint?: I would suggest "story". For something that takes one or more people and longer than a sprint? I would suggest "epic". So what about feature? I would use feature to describe a solution that takes one or more people to work on, typically longer than a sprint. Our issue, of course, is that people come to us with features, we have to work to figure out why they want that feature. Turn a solution into a problem to be solved.
Releases are collections of stories, perhaps epics, and features that we expect will be delivered by a given date.
Just a general architectural question. Do you link bugs from sprint/iteration 10 to Feature/User Story/Epic from sprint/iteration 5 (across sprints/iterations)? This way, DevOps can be a good documentation for a new stakeholder/QA/developer to catch up by reviewing all linked work items/features/epics since the beginning of time.
I think it is a reasonable idea to link any defect to the original story that it is a defect against. A defect, however, may be at many different levels of the functional decomposition. Some flexibility may be needed here.
so good.