Use this Example to Write a Project Brief - YouTube

Channel: teamgantt

[0]
Hi.
[1]
This is Jason with Team Gantt.
[3]
A project plan is arguably the most important document created
[6]
on your project, and any good plan
[8]
starts with a project brief.
[10]
Today I'm going to help you create a project brief that
[13]
will keep your project from going off the rails.
[15]
[MUSIC PLAYING]
[24]
At its core, a brief should communicate your project
[27]
approach and the process your team
[29]
will use to manage the project according to scope.
[32]
If it's handled with care and great consideration,
[34]
a good brief should act as an agreement
[36]
on project objectives, scope, major deliverables, milestones,
[42]
timing, activities, process, and even resources
[47]
needed to deliver your product.
[50]
If you take the time to create a good process around how
[53]
your plan is built, and you consider all of those factors,
[56]
you can create a great plan that will work for everyone.
[59]
Now you could easily slap together
[61]
a document that shows dates and deliverables,
[64]
but if you're managing a project that
[65]
has a hefty budget, lofty goals, and a whole lot of decisions
[69]
attached, you'll find that it's important to take the time
[71]
to get this document right.
[74]
With the right amount of background information
[75]
on your project scope and requirements,
[78]
and with a good level of input and collaboration
[80]
with your team and your clients, you
[82]
can make a solid, workable plan that will guide everyone
[85]
through your project, and it doesn't
[87]
have to be difficult to create.
[89]
To many people, a project plan is a dry document
[92]
that lists dates.
[93]
To people who are invested in your project,
[95]
the plan is the project guide that
[97]
will dictate how you will get to project milestones, decisions,
[100]
and eventually project completion.
[103]
At a minimum, a project plan answers some basic questions
[106]
about the project like what are the major deliverables?
[109]
How will we get to those deliverables and the deadline?
[112]
Who is on the project team, and what role will they
[115]
play in those deliverables?
[117]
When will the team meet milestones,
[118]
and when will other members of the team
[120]
play a role in contributing to or providing feedback
[123]
on those deliverables?
[124]
Look at it this way, your plan should educate any reviewer,
[128]
coworkers and clients included, on the logistics
[131]
of the project.
[132]
They trust that you've got this, so when reviewing a document,
[135]
they truly believe that you've considered every possible risk,
[138]
and if you have, it feels good to know that you've done
[140]
a good job, and you're trusted.
[143]
The first step in creating a good plan
[145]
is drafting up a good project brief
[147]
to go over with the client.
[149]
Picture it.
[150]
You work for a web design agency,
[151]
and your team just scored a big new project.
[154]
Your new client is an internationally recognized art
[157]
museum, and their website is woefully out of date.
[160]
In fact, it hasn't been redesigned since 2007.
[164]
The site architecture, visual design, content, and code
[168]
are ripe for change.
[169]
And it's up to you to make it happen.
[171]
Your clients aren't very web savvy,
[173]
so they're looking to you as the expert
[175]
to determine a process that will work.
[178]
They'll also lean on you to let them
[179]
know what you need in terms of content like photos and text.
[183]
That's right.
[184]
It's all on you, and the scope you have in place
[186]
will support an end to end project.
[188]
We've put together an example of a project
[191]
brief in our free Guide to Project Planning for you
[193]
to download and use.
[195]
And when you're ready to create your Project Gantt chart,
[198]
you want to use the best and easiest web-based Gantt chart
[200]
software out there.
[202]
Team Gantt is used and loved by thousands
[204]
of teams in over 60 countries.
[206]
We think you'll love it too.
[208]
To sign up for a free 30-day trial,
[210]
go to teamgantt.com/signup.
[213]
Quite often, you'll receive a ton of project details, pages
[217]
upon pages of requirements, team biographies, invoicing
[220]
instructions, contractual clauses, and the like.
[223]
It's very critical that you read through all
[225]
of that documentation, but when it comes to creating a plan,
[229]
this is what you need to know no matter what type of project
[232]
you're managing-- project goals, the client or team's intended
[237]
process or methodology, the team and their expertise,
[242]
expectations on deliverables, expectation on iteration
[245]
and collaboration when creating and revising deliverables,
[249]
who the client stakeholder team is,
[251]
and, specifically, who the main decision makers are,
[254]
the amount of time the client will
[256]
need to review work and provide feedback, dependencies,
[260]
and deadlines.
[262]
Never leave any of these items unanswered.
[264]
If you're responsible for creating the project plan,
[267]
that means you must be sure that all factors have
[270]
been considered.
[271]
If you don't, the project will definitely
[273]
hit a bump in the road, and every finger
[275]
will be pointed at you.
[277]
For instance, if you have not fully
[279]
explored the decision making process,
[281]
there's a great chance you'll encounter the good old swoop
[283]
and poop during the process.
[285]
If you don't know what that is, it's
[287]
when a stakeholder you weren't aware of
[289]
swoops into the project at the 11th hour
[291]
and poops on the work, and then puts you back to square one.
[295]
It's a budget and timeline nightmare
[297]
that will become a reality if you don't
[299]
practice your due diligence.
[302]
Just remember, you can get as much information as possible,
[305]
and details can change.
[307]
Do your best to document the information you have,
[310]
so you can account for it in your plan.
[312]
This was just a brief excerpt from Team Gantt's
[315]
Guide to Project Planning written by project
[317]
management consultant, Brett Harnett.
[319]
Brett focuses on solving issues that
[321]
are important to organizations who
[322]
want to produce quality digital projects in harmony.
[326]
Click the link in the description
[327]
to download the full guide for free,
[329]
so you can plan your projects more efficiently than ever.
[332]
And if you like this video and want to see more,
[334]
don't forget to click the Like button
[336]
and subscribe to our channel.
[337]
Thanks.
[338]
See you next time.