How To Create A Program Management Plan Smartsheet
How To Create A Program Management Plan Smartsheet
Content Center Managing Work Business process management
Team leaders must create a solid program management plan to successfully manage a program. We’ve
gathered advice and tips from experts on how to create an effective plan, including what you need and the
steps to take.
Included on this page, you’ll find the key components of a program management plan and steps to take
when developing a plan. Experts share tips to help you get started and download a customizable program
management plan template.
In this article
“When I think about a program management plan, it's a strategic roadmap that documents everything that
you need to be able to do to run a program,” says Jeff Givens, Senior Vice President of Operations at JDA
TSG, a business process outsourcing firm. “That's timelines, milestones, responsibilities, deadlines, and future
expectations.”
A good program management plan is vital to executing and managing a program effectively. You can learn
more about best practices in managing a program in this guide.
“Who are the program’s stakeholders, and how will communications be managed?” asks Alan Zucker,
Founding Principal at Project Management Essentials, LLC. “Similar to project management, program
stakeholder engagement is critical to success. Stakeholders are identified (and) their needs are assessed.”
Identification of Responsibilities and Accountabilities: The program management plan outlines key tasks
and areas of work for moving the program forward, and it designates which team members or groups are
responsible and accountable for completing them.
Givens describes what the plan must set out: “Who is going to be responsible and accountable?” He adds
that program managers and teams will often use what’s called a RACI chart (which stands for responsible,
accountable, consulted, or informed) to provide details on how various people or groups will be involved
with or kept informed of certain tasks.
Learn more about the RACI matrix, what it represents, and how it works. Download a free RACI template to
decide who is accountable for each aspect of the program.
Schedule, Timelines, and Deadlines: The plan will set the schedule and timeline for the program and
deadlines for important tasks.
“Timelines are always going to be there, along with adjustable milestones — what you expect to have done
by certain points, and how to measure yourself against those things. Those always need to be created,”
explains Givens.
The plan may provide an overall roadmap and work breakdown structure for the program. It can also explain
how your team will manage and change timelines when necessary.
Dependencies and Constraints: Many program tasks will be dependent on the completion of others. Some
work will also be constrained by other jobs or by other particulars of the program. The program management
plan should include the details about those dependencies and constraints.
Program Structure: The program management plan will detail how the organization will handle the program
and how leaders will work with program leaders. The plan also outlines how program leadership will interact
with and oversee project leaders and other team members.
“This includes the leadership and oversight layer — leadership or executive leadership committees — above
the program manager, as well as the structure and relationship between the program manager and the
project managers,” clarifies Zucker. “If the program is large enough to have a program management or
execution office, the function and structure of that organization will also be described.” Learn more about
the structure and work of a program management office.
Program Governance: Closely tied to program structure, governance provides more details on the how. The
program management plan should set out the authority and responsibilities of various company or program
team leaders. Governance may also decide how often leadership groups will meet and how to bring
important issues to the appropriate leaders for decisions.
Program Execution: The plan will offer basic details on how the program will manage critical parts of the
work.
“Projects manage their execution, and the program needs to define how it will manage and coordinate items
that impact the program, such as risk, change, interdependencies, and status reporting,” explains Zucker.
“These elements are managed at both the project and program (level). This section describes what needs to
be elevated to the program and how the program will address them.”
Cost Management: The plan can include a section that covers the program’s budget and expenditures. It
may also provide details on the people who are responsible for managing costs and have the authority to
approve budget changes.
Communications Plan: The plan might also cover how program leaders and the team will perform and
manage communications, such as the frequency and types of communications and who will provide it.
Zucker also points out that the team understands the stakeholders’ information needs, “and a
communications strategy is developed to support those needs.”
Download a range of project communications plan templates. You can modify the templates for program
management and customize them to fit your needs.
Risk Management: A program management plan will often detail how leaders assess, monitor, and deal with
risks.
Change Management Plan: There should also be a section that covers how to identify and manage any
needed change. The plan will also outline a clear process for ensuring those changes happen efficiently.
“A change management process will always need to be present,” advises Givens, from JDA TSG. “What
happens when the unknown does come? How do you systematically handle that change, rather than just
flailing about trying to handle something?”
“How are we going to measure, assess, and address the program's success?” asks Zucker. “This section
describes the key performance metrics established for the program.”
Closeout Procedure: The plan should also include a section that explains what the team must do whenever
leaders have decided to close the program. In many ways, the closeout procedure will be similar to a project
closeout. It might include an overall evaluation of the program, lessons learned, and how to use those
lessons learned in future work.
4. Agree on Responsibilities
The finished plan must detail responsibilities and accountabilities. Who will be doing which tasks? Who
ultimately will be responsible for their completion?
“Create an agreement on the responsibilities and accountabilities for everyone who's involved, so that you
can hold them accountable to those elements,” says Givens. “Everything from timelines and milestones and
deadlines and expectations is going to bridge off of (that).”
6. Adjust as Needed
A key function of having and monitoring checkpoints is to evaluate and understand when to make
adjustments.
“One (goal) is to fail fast,” states Givens. “If something isn't working, you have to change it. If an idea you tried
didn't work, it's time to change and fail fast, and move to the next thing that can work — while working off of
your accountabilities and responsibilities.”
“Adjust the plan as the program progresses,” says Zucker. “No plan is perfect. We need to assess and adjust
the plan continually.”
“Whatever you think this project or program is going to be, inevitably it's going to be somewhat different,”
explains Givens. “Hold on to what the original vision as the long-term truth. (But) as you notice it starting to
go in a different direction, adapt to that change, rather than trying to force it to be something that you
thought it was originally. Don't lose the forest to the trees. If you're at a place where a certain element of a
plan is not working, that doesn’t mean the program can’t work. It means whatever is happening within the
plan itself isn't working.
Givens says some components might stay constant. including maximum budget and responsibilities of team
members. “But everything else needs to be flexible, so that you're able to adapt to what reality is going to
be.”
Meet Deadlines, but Think Twice About Delivering Too Early: Your team will want to meet deadlines with
good work. However, there can be a danger in finishing too early before some deadlines — especially if
you’re an external group doing work for a client, Givens says.
“Some people say underpromise and overdeliver (on deadlines). I think there's danger in that,” he adds. “If
you set a deadline of January 1, and you come in on December 1, and say, Hey, we're ready to go, oftentimes,
clients will say, Well, we're not ready to go. Then they're going to start second-guessing everything you did.
And for a month, you revisit everything.”
Understand How to Balance Competing Interests: Many people inside and outside your organization may
be involved in the program, including top organizational leaders, top project managers, and other important
stakeholders. The program management plan must include a structure that helps program leaders deal with
organizational politics and nuances.
“Program management is not easy,” Zucker says. “It is like herding cats. Leaders and project managers may
have competing interests and priorities. Project managers are often strong leaders in their domains. The
program management plan needs to balance these competing interests, management styles, and needs.”
Product
Resources
Company
Learn
English