So, the Pre-Release Version of 2023.1 Release Notes is available on EpicWeb. There is a type called Story and I have no idea what it means. Anyone have any insight?
In Jira*, people start with User Stories - short blips that describe the business (not technical) problem.
User Stories | Examples and Template | Atlassian
*It’s an Agile programming thing but that’s built into Jira, the ticketing system that Epicor Developers use. Epicor Ideas feeds Jira if I understood @timshuwy correctly.
2 Likes
We’ve reached the point in the simulation where our programming not only runs off abstractions,
but user requests too.
Depending on the project, if you don’t watch your epics closely enough they can end kinetically.
(I’ll show myself out)
Well, I am still learning the Epicor way around Jira, so if I misstate the facts, I will pre-apologize.
We have multiple layers…
- IDEA: This comes from “Epicor Ideas” (aka AHA!) and is something that you all can create, vote on, etc. Epicor employees can also create ideas and vote. When an Idea gains enough importance through votes, then it would become either an EPIC or a STORY. MOST of the time it becomes an EPIC, but for very small ideas, we might make it a story, and assign it to another pre-existing EPIC.
- STORY: a small piece of an EPIC… but from Our point of view, We the Product management team typically skips the STORY and goes directly to an EPIC. then development creates multiple stories that will complete the epic. For example. I could have an EPIC to add a new field, which turns into several stories… one for a study, one for the schema change, one for updating the screens, one for documentation, etc. Note that in most cases, if you turn in a BUG, the bug becomes a STORY that is ranked separately by the “Sustaining” dev team, and fixed for a future release.
- EPIC: Again, this is where Product Management typically works… we turn an Idea into an EPIC, which is then sized by Development, and then ranked for importance. We assign the EPIC to a RELEASE. In our world, we like to keep the EPICS small enough to fit into one release. In other words, we dont want an EPIC to extend beyond one release. If it does, then it is cut into smaller epics.
- Initiative: This is typically multiple EPICS and can cross over multiple releases.
Here is an example of an IDEA that became an EPIC:
- https://epicor-manufacturing.ideas.aha.io/ideas/ERP-I-148 was an idea… it received 119 votes.
- We promoted it to an EPIC ERP-45821. It was then “sized” It has been scheduled to go into the 2023.2 release (insert Safe harbor statement here).
- that epic already has one task (ERP-47495) to design and discover how to resolve this feature, and ERP-47751 to do the schema changes (adding a new Shipping Calendar id to the SITE table). There will be more stories as we put additional requirements onto the epic. In fact, as I was typing this, a new question came from development on some of the requirements.