[gansbrest]

It pretty much boils down to:

- Jira Epics (describe the why from the business standpoint)

- HQ meets two times a week to re-asses priority (drag up Epics up or down, or change priority) and monitor status

- Two week sprints where engineering leads along go through epics

- New sub-tickets created by engineering (including design) and assigned to specific people.

- Once thing are getting done, they are move to QA test status. After testing it either goes back to engineering or to Release Approved status.

- Engineer initiates and monitors the the release via CI/CD Jenkins pipeline.

That's pretty much it on the high level, unless I'm forgetting something.

One important note here - some time ago we made a decision to ignore "good ideas"/backog. We don't keep them in Jira until business is sure that we really need this particular functionality and ready to start building it right now.

That was somewhat radical and took some time to get used to, but it allowed everyone to focus on what's important now vs nice to haves to keep people busy with things noone really needs.

Overall there is no "generic" advice, everything is very org and stage specific. Common sense is the main guiding principle.