This document provides an outline for a project plan, including sections for the project background, goals and requirements, scope, implementation plan, risks, schedule, team, and stakeholders. The scope section defines what will and will not be included in the project. The implementation plan summarizes the proposed solution and how the project goals will be met. A high-level timeline is also described.

1. Example Project Plan Whiteboard
Project Name
Target Release
Epic
Document Status
Document Owner
Project Lead
Developers
Project Planning Notes:
We need to answer the following questions.
Why: Present the Business Case
What and When: Use the Roadmaps for the details
How: Development plan and budget (labor, hosting, software needed, other operational costs)
Who: Resources (budget) and partners evaluated
Note: Not all sections of this plan need to be used, the purpose of this template is to help you
organize your thoughts.
Principles:
Project Background and Description
[Describe how this project came about, who is involved, and the purpose]
Background and strategic fit
You can cover the business case here, the why

2. Goals & High-Level Requirements:
[Describe the high-level goals and requirements for the project]
Requirements
# Title User Story Importance Notes
1
EXAMPLE: The new system must include the following:
Ability to allow both internal and external users to access the application without downloading
any software
Ability to interface with the existing data warehouse application
Ability to incorporate automated routing and notifications based on business rules
User interaction and design
Include any mockups, diagrams, or visual designs relating to these requirements
Scope:
list what is in scope for the project
What and when, refer to the roadmaps (when can be addressed in schedule)
[Project scope defines the boundaries of a project. It not only defines what you are doing, but it
sets limits for what will not be done as part of the project.]
[Describe how you plan to implement the project. For example, will all parts of the project be
rolled out at once or will it be incremental? What will be included in each release?]
List any critical assumptions
Affected Business Processes or Systems [List business processes or systems that will be impacted
by this project and describe how they will be affected.]

3. Guidelines for a Scope Statement
Purpose: Map reality against the vision and establish what is essential for success that can
be accomplished within the constraints of the project. Shiftless essential features into future
releases.
Length: As succinct as possible
Guidelines: Be SMART (Specific, Measurable, Achievable, Results-based, Time-oriented).
Clearly state what is out of scope.
ImplementationPlan:
Implementation Plan (Use this section if you need to highlight implementation details)
Include recommendations that lead to the project's proposed solution. Summarize what you’re
proposing to do and how you’re going to meet the project goals
Out of Scope:
list what is out of scope for the project
[Describe any specific components that are excluded from this project]
Risks:
Risks: list any known risks to the project
Dependencies: list of known dependencies if related to risk
Tools:
list tools to be used in the project
Schedule:
High-Level Timeline/Schedule
[Describe what the high-level timeline/schedule will be to plan, design, develop and deploy the
project. Generally, by when you expect this project to be finished?]
Sprint plan high-level

4. Project Team and Stakeholders
Team
 Who (which resource partners)
 Resources
 External Customers
 Internal Customers
Stakeholders (example)
 Application Team
 Cloud DevOps
 Cloud Leadership
 Cloud Platform Services
 Members of Cloud Governance Working Team
Questions:
Below is a list of questions to be addressed because of this planning document: