Epics
- Support start with S- (STREAM/TYPE: Improvements/Bugs)
- Customer Projects start with C- (STREAM/TYPE: Project)
- Roadmap items start with R-
- Coud optimisation (STREAM/TYPE: Roadmap)
- Roadmap - other (STREAM/TYPE: Roadmap)
- Bugs start with B- (STREAM/TYPE: Improvements/Bugs)
- Pre-sales start with PS-
Don’t enter Start and Due Dates at the Epic level. Only at the story level
Epic fields
- Stream/Type
- Support. This is only for P1 or P2 tickets where a resolution is needed for a key piece of functionality for the customer.
- Customer Project. These are items that are specifically required to deliver the “absolute minimum per the customer spec document” to go live. Anything that is not critical to go live would move under Roadmap or Bugs.
- Roadmap. These are general roadmap items that are not associated with a specific pre-sales opportunity but could be related to a specific existing customer—either
- a) committed as part of an existing project but not critical to go live OR
- b) NOT committed to any timeline (i.e. we said we’ll do it to a specific customer or just generic things we want to do as a business in which case Customer=Internal).
- Pre-sales. These are “roadmap” times but work specifically related to a customer.
- Bugs. These are items a) where we have identified a bug and the customer is not necessarily aware or b) customer has identified the bug but it is a low priority.
- Customer - if it relates to a specific customer. If not, call it “Internal”
- Reference
- Area / Product
Story fields
- Stream
- Support
- Customer Project
- Roadmap-Committed
- Roadmap-Uncommitted
- Pre-sales
- Bugs
- Customer
- Reference
Example
Sheffield
- C-Sheffield - CLOSE THIS EPIC WHEN IT GOES LIVE.
- R-Roadmap
- Solr (Stream: Roadmap-Uncommitted, Customer: Sheffield)
- Importer (Stream: Roadmap-Committed, Customer: Sheffield). These dates are “hard dates”