The “why” of the project. The goal is to have a compelling and clear vision for the effort.
This is the “What” of the project and it states what will be done in the project to achieve its higher purpose. This should include technical, business, product, and team objectives.
An assessment of how big the resources needed will be to deliver this service based on assessment of resources and organizational readiness for agile.
An assessment of how complex delivering this service will be based on assessment of scope and organizational readiness for agile.
Known/assumed customer needs, anticipated functional and non-functional requirements.
Executive/Stakeholder, project team organization chart (especially if there are multiple teams operating at the same time), organizational governance structures.
Space, equipment, people/roles, skillsets and capabilities, collaboration support, and tools. While you may not have names for all the teams that you will form for the project, you should have an idea of what roles you think will be needed.
Strategies, methodologies, processes, tools and techniques the team will follow.
Success Criteria
What determines the success outside the solution itself? Should be concise, realistic, and directly measurable.
Ordering, importance, and trade-offs within the project objectives (simulates a high-level product roadmap or release plan) as well as relative to other projects the organization is sponsoring.
Defines where the product is headed and is tied to the vision and strategic goals. This is a key element that should be included.
Restrictions, limits, boundaries that apply to the team, process, product, and/or schedule.
Top risks, known issues, and relevant organizational history that impacts readiness, specific points of uncertainty, and which includes mitigation plans for each.
Key stakeholder approval that authorizes the project and other necessary signatures.