Epic Story Task
--
In Agile software development Epic Story & Task are very accustomed words. For managing agile software development JIRA is a great tool. JIRA provide a fairly broad approach to agile terms and functionality. In general, Epic, Story & Task all are Issue Types in JIRA.
Epic: Collection of features or large body of work or somethings so big or large user story that is eventually broken down into smaller stories. Example, any web site authentication module can be an Epic.
Time to complete 2–4 weeks.
Owner: Product Owner
Creator: Anyone
Story: Functional requirement that provides some business value. Stories describe work that must be done to create and deliver a feature for a product. It represents user story. For estimation generally use fibonacci numbers approach. Example, in authentication module login, forgot password, sns login service etc. are the Story.
Time to complete: ⅓ sprint
Owner: product Owner
Creator: Anyone
Task: The day-to-day things you must do to complete a Story. Represents development tasks to accomplish the user story. A task is very concrete band always belongs to a user story. Example, login page UI/UX, API, FE etc. are the Task.
Time to complete: <8 hour
Owner: Product Owner
Creator: Team Member
Story point — Cheating
30 Mins = 1 Story Point
1 hour = 2 story points
4 hours = 8 Story points
1 day = 16 story points
2 days = 32 story points
3 days = 48 story points
4 days = 64 story points
Relating the above to the traditional fibonacci numbers
30 Mins = 0.5 Story Point
1 hour = 1 story points
4 hours = 3 Story points
1 day = 5 story points
2 days = 8 story points
3 days = 13 story points
4 days = 21 story points
