...
- A clear, well-communicated, mutual understanding of key milestones, phases and dates for a release
- A clear release checklist, describing:
- Key activities during each phase of the release: choosing a release manager, how JIRA is organized, etc.
- How to build, verify, install, and run the entire application, step by step
- How to organize, cut and tag, deploy, and announce a new release
- All this information should be described in Draft Updated Release Process
- The ability to create integrated builds on a constant basis
- Always have a fresh, full stack version of "Project" visible – a daily build
- Currently, this will require us to invest up front in build automation
- Enough information and/or collaborative availability that teams can cross architectural boundaries to help out when needed