#Portfolio epic definition free#

It seems to me that the story/task debate in Jira is similar. On receipt of work requests we had a process to triage and classify them (as bug or change) and another process to manage the work request depending on whether it was a bug or a change. Initially we couldn't agree what to call the 'things' users should submit but eventually settled on 'work request'. I felt strongly that we shouldn't ask users to pre-determine the categorisation of the 'thing' they were highlighting users shouldn't be expected to know the difference between a change and a bug - only that they wanted something done.

Sign up and learn more about the best tool for project management.įor me this brings to mind a debate I had in a previous role where I was responsible for managing an application that received bug reports and change requests from users.

#Portfolio epic definition free#

We are also holding a free webinar 'How to get started in Jira' on April, 28 and we'll be happy to see you.

Tasks are finished weekly by the consultants.Įxample: Record current status, Prepare meeting, roadmap implementation, testing Tasks: Tasks are single to-dos and problems, which should be done and solved before going live with the new Jira instance. Stories: The story represent the goal, namely implementing a Jira instance for a customer.Įxample: “Implementing Jira instance Customer X”ģ. Epic: In our Consulting team Epics represent single services.Ģ. Implementing a Jira instance for a companyġ. Tasks are oftentimes part of a story and cross-linked.Įxample: Article Research, Article creation, Proofreading, Publishing Practical example from Actonic's Consulting team Tasks: Tasks are single to-dos, assigned to one employee and planned in a specific sprint. The project lead is assigned to the Story to keep an overview.Įxample: Article creation “Epic vs. Stories: We use Stories to plan big to-dos or projects, which are going to be part of multiple sprints and with multiple tasks and employees. Epic: Our Marketing team uses Epics in order to define the topic of the task.Ģ. Practical example from Actonic's Marketing teamġ. Project leads and stakeholders are at the same time keeping an overview and status updates along every step of the way. Stories and Tasks belonging to the same epic, are sometimes linked or co-dependent.īy using Epics, Stories and Tasks, Jira teams are able to record small and big successes throughout the year.Epics are most likely part of a roadmap for products, team or customer projects. Epics are oftentimes not part of one, but of many sprints.An Epic could present the theme/topic to which a task belongs or represent a big project, for example “Migration customer X” in consulting or “Website Relaunch” in marketing.Teams commit to finishing Stories mostly in the next few sprints.Įpics represent either topics or overriding goals, which are then broken down into Stories and Tasks.This allows users to go from their ticket to the Story to have a look at general information and for project leads to get an overview of tickets and their status. All related Tasks can be linked to the Story.A story can be assigned to the project lead.Stories entail the most important project information: vision, goal, benefits, project team etc.Stories can be a bigger project, like the creation of new landing pages in marketing or the migration of instances in consulting. Tasks can be part of Stories, which means that Stories can be seen as the overriding task, sometimes called User Story. Tasks can be cross-linked and can block each other.They are being worked on actively, can be forwarded to someone else for feedback and can be marked as done when finished.Tasks can be assigned to a responsible employee (assignee).They could be part of a bigger project or planned by themselves.Tasks are being used to plan specific tasks which should not take more than 1 working day.Set up from smallest to biggest element Tasks Definition and distinction is oftentimes done for developer teams and their processes, which is why we want to explain them in relation to Marketing and Consulting teams. Planning, structuring, executing and monitoring tasks and their progress in Jira is made possible by Jira’s elements called Epic, Story and Task. How are these issue types used in Marketing and Consulting?