馃攳
6 WordPress Productivity Principles - Principle #1: Define the Job in Detail - YouTube
Channel: unknown
[0]
Okay, in this video snippet I'm going to
quickly cover the first principle of
[4]
WordPress Productivity which is to Define
the Job in Detail with a Content-First
[9]
Approach. Now Keane's original principle
was to Define the Job in Detail. I added
[15]
the Content-First approach because I've
found that if you don't take a content
[19]
first approach, then you get bogged way
down.. and the clients not delivering you
[24]
the content, you're waiting to get paid
because the client hasn't given you the
[28]
content so you can't finish the website,
and I'm done with that. The way that I
[32]
approach it keeps that from happening
and I'll share more about that with you
[35]
later. Define the job in detail basically
is the biggest principle of all the
[42]
principles and some of the other
principles kind of feed into this
[45]
principle because this isn't like an
activity that takes place one time. This
[50]
is a constant, iterative process and by
iterative, I mean that you find out some
[55]
things, you back up a few steps, you
change it a little bit, and then you end
[59]
up with a better result.
So by drilling down into more detail
[64]
over time is how you do that. Now this
whole process of defining the job in
[70]
detail generally is about 60 to 70
percent of the project because let's
[75]
face it, you and I both know building a
wordpress website does not take that
[78]
long. Especially if you have all the
pieces and parts all laid out it's
[82]
defining the website, getting all the
content together, getting all that pulled
[86]
together and implement on the website.
That's the problem. So if you spend that
[90]
time that you need to spend on the front
end before you ever build a page or code
[96]
anything or install a plug-in, then
you're gonna be way better off because
[100]
you're gonna have way fewer surprises.
You'll have found all of those before
[105]
you ever start. That's the main thing.
Okay, so you can basically divide
[109]
defining the job in detail into two
sections. In terms of the
[115]
project-related pieces that you need to
define for your client, you need to make
[120]
sure that you define your management
approach in great detail. And I always
[126]
use the 6 Principles of Productivity
Management as part of my
[131]
management approach
because it really gets them to
[133]
understand how important it is to do
this design on the front end, and the
[138]
drilling down into the details on the
front end, so that we don't end up with
[143]
change problems on the back end. I always
include roles and responsibilities and
[148]
you've got to define a scope. You've got
to define what's in scope what's out of
[151]
scope and another thing I do is I define
what's in scope but the clients
[155]
responsibility and I'll talk about why
I do that later. You got your business
[158]
requirements. Now, see what I find a lot
of people doing is they just start
[162]
immediately start jumping in saying, "oh
you need an about me page. You need it
[165]
this page, you need that page." But they
haven't even discussed with the client
[168]
what their business requirements are for
this website. Some websites are just
[173]
meant to establish an online presence.
Other websites are just like a brochure,
[177]
informational. Other websites they want
to sell a product. Other websites
[181]
they want to become a thought leader. So all
of those things have a bearing on how
[186]
many pages, where things are. You know,
some people don't need an about me page
[190]
sometimes about me is fine if there's a
paragraph on the home page and that's
[193]
all they really need. So depending on the
needs of their business. So that's why
[197]
those business requirements are really
important and then of course you've got
[200]
your estimate which you need to define
up front. Then you've got the solution
[204]
related pieces and parts of your
definition which include things like
[208]
your list of deliverables and what are
the acceptance criteria for those
[212]
deliverables? What are the plugins you're
going to use? The products and services
[216]
that the client is going to offer on
their website? The pages and posts. Your
[222]
work breakdown structure. The site map.
All of those are pieces and parts that
[226]
you can use to define the job in detail.
You don't have to use all of them and in
[231]
the Complete WordPress Project
Management Roadmap that I'm developing,
[235]
I'll tell you exactly the ones that have
been successful for me. The other thing
[239]
that's included in the solution related
section of defining the job in detail is
[245]
content. I don't do any development until
all the content is received. Now does
[252]
that mean your project could draw out
forever? Sometimes. But I also use
[256]
something called a Minimum Viable
website that keeps that from happening,
[260]
too and I'll tell you more about that
later on in some
[264]
these videos. So let's recap. Number one,
the define the job in detail is not a
[270]
one-time event that you do at the
beginning and the proposal and then
[272]
you're done with it. It's something that
you have to continue to do because
[275]
things are continually discovered.
However the first 60 to 70 percent of
[281]
the project is nothing but defining the
job in detail and if you take the
[285]
appropriate amount of time and get the
appropriate approvals from your client, I
[290]
promise you you'll have way less
surprises on the back end. Now in the
[294]
Complete WordPress Project Management
Roadmap, I'm going to break these things
[298]
down by phases and activities so you'll
be able to see where to apply this
[303]
principle all the way through the
Roadmap. So, that's principle number one.
[308]
Next we're going to talk about Principle
number 2 - Get the Right Resources
[312]
involved. See you in the next video!
Most Recent Videos:
You can go back to the homepage right here: Homepage