huge story
September 4, 2008 by wellidy
Hi,
i´m begginer in agile way. In the first job following this way, one of the first doubt happend when one feature for the next version of my product is a huge story and is the must important.
The doubt is: is it really a story?
Reading in this site about epics and themes, i was confused. Cause epics are low priority and this is not my case.
Here, with the team, we consider this is a feature and we split it in 7 storys.
What you think or advise me?
tks in advance.
Bookmark/Search this post with:
Permalink
Best of AgileSoftwaredevelopment.com
- Scrum backlog templates and examples
- Simple Product Backlog Example
- Simple Sprint Backlog Example
- Developers Aren't Gonna Read It
- Can unit testing be a waste?
- Six Features of a Good User Story - INVEST Model
- Product backlog
- Performancing Metrics Module
- How to use agile methods for the fixed price contracts
- 7 Tips for Improving the Daily Scrum
- Are you assigning your top engineers to projects?
- Top 20 Best Agile Development Books, Ever
- Professionalism = Knowledge First, Experience Last
- Video tutorial: Managing your Scrum Product Backlog with the help of a simple Excel sheet
- Extreme Programming
- Video tutorial: Managing your Scrum Product Backlog with the help of a simple Excel sheet
- Five risks of solo programming
- Extreme Programming
- Video tutorial: Test Driven Development in practice
- 10 Signs That You're Not Agile
- Five steps for starting the Scrum project
- 10 Principles of Agile Project Time Management
- Destructive bonuses
Subscribe to updates
RSS feedNavigation
User login
Private blogs of the regular contributors
Recent comments
-
Dmytro Lapshyn (not verified)
-
Neeti Tayal (not verified)
-
Anonymous (not verified)
Comments
Epics are just big fat stories
September 4, 2008 by Artem, 12 weeks 6 days ago
Comment id: 1832
Epics are somewhat confusing term. Lately I started to prefer talking less about epics and more about "big fat stories" (I've got the idea from David Hussman). If a story is too big for an iteration, well, it still can be of high priority. Then you should just split it into smaller sub-stories.
How exactly to split big story into smaller ones is another interesting topic and is very context dependent. I usually try splitting into sub-stories that represent minimal possible, almost useless functionality + a number of upgrade stories.
Post new comment