Release Planning + architectural topics have to be discussed / refactored after 1. REL
→ Solutions Architect?
→ Longer-term planning – need answers to questions like “When will we be done?” or “Which features can I get by the end of the year?”
-> REL planning must balance customer value and overall quality against the constraints of scope, schedule, and budget (planning on fixed-date or fixed-scope releases)
epic = a large body of work that can be broken down into a number of smaller stories (eg performance-related work in a release), cannot be delivered within a single iteration and can span more than one project, if multiple projects are included in the board to which the epic belongs.
-> no standard form to represent epics (use user story formats “As a, I want, so that” or represent epics with a short phrase)
