Quarterly Planning and Epics

[Jhonatan Farias]

Hey Guys,

I would like to share with you a development process that my company is planning to do, to collect feedback to see if this is the best way of doing it.

For a better context, we have a CRM, with different modules (Contacts, Opportunities, Projects) and usually at the beginning of the quarter, based on clients' feedback and needs, we plan what we should deliver during this period.

And here it is where Jira appears, what we are planning to do is use the following hierarchy.

Epic: Q2/24  - Opportunities (Use the epic for everything that we want to develop in the quarter)

Story:  Features that we want to develop by the end of the quarter, as an example Opportunities - Reports Feature

Sub-tasks: What we need to do to complete the story above.

Do you think this is the best approach or there is something we can improve or do differently?

[Dexter de Vera]

Hi @Jhonatan Farias ,

1. You can use the Epic as functionally/features/parts of the product that your planning to build/update.
2. Story for user stories expected by client.
3. Subtask for breakdown of task needs to be done per story.
4. Use version for quarterly major releases.
5. Some organise sprints around completing work for a specific version.