Objectives, project deliverables and scope

[Jen]

Here's a place to start:

At AI, I begain my Web Design class by looking at all the steps
involved with designing a web site. We spent time talking about the
discovery phase in which I gave a list of targeted questions for the
client in order to determine a statement of purpose. I stressed how
all the steps in the process then needed to support that statement.

To address the question as to who provides the objectives, I think
that first your students should be provided with a detailed creative
brief which outlines the projects objectives. The second year student
might be better enabled to conduct a mock interview during the
projects discovery stage.

Project objectives should be a clear list of deliverables which help
to describe the Project Scope. Normally Project Scope is more of a
project management issue, but I think it is importiant fot students to
have the tools necessary to avoid scope creep, which happens when
additional project requirements a are added without regard to budget
and timeline.

Here are examples of specific deliverables related to Web Design and
Project Scope:
(I found these examples at http://www.tpdesigns.net)

A good number of documents are created during the web design process.
There is certainly a lot for the competent web designer to document
throughout the discovery, planning, design, integration and delivery
stages of a complex web project. Not all of these documents are of
interest to the client, and over the years I've learned only to
present the minimum number of documents needed to ensure a successful
project. The following are the standard deliverables I ask my clients
to sign off on.

Creative Brief
This is a project definition document. It includes all the
requirements and specifications of the project, including scope,
audience, objective, call to action, and technical specification.

Download Creative Brief Worksheet
http://www.tpdesigns.net/downloads/CreativeBriefWorksheet.doc

Content Outline
The content outline defines every piece of content that will appear on
the website. If it isn't on the content outline, it isn't going to
appear on the website. The content outline is part of the information
architecure, and as such should be organized in a hierarchy that
represents the structure of the website rather than a hierarchy based
on arbitrary categorization of content.

View Sample Content Outline
http://www.tpdesigns.net/tutorials/sample-content-outline.htm

Site Map
The site map represents the structure and navigation of the website
and should closely coincide with the content outline. There should be
a common numbering system in place. Pages are represented by boxes and
links by arrows.

View Sample Sitemap
http://www.tpdesigns.net/tutorials/sample-sitemap.htm

Wireframes
Wireframes are schematic versions of the pages on a website and should
similate the final navigation, although the page layout at this point
in the process is rough. Wireframes can be made into clickable web
pages, allowing the client to preview the navigation of the site in
action. Each wireframe should include all pieces of content that the
final web page will display.
Note: The CS5 version of Fireworks allows the user to create
interactive wireframe prototypes. Really cool feature!

View Sample Wireframe
http://www.tpdesigns.net/tutorials/sample-wireframe.htm

Graphic Design
Mockups/Comps The graphic design mockup is a composite image of how
the final web page will look. Color, layout, typography, and images
are all worked out at this stage for each significantly different page
type on the website. I should make clear that even though the
composite (mockup or comp for short) looks like a web page, it is
still only a single image. It is not a web page, and include no code
at this point in the process.

Note: The CS5 version of Fireworks allows the user to create
interactive wireframe prototypes. Really cool feature!

View Sample Mockup

Development Site/Prototype
During the integration/programming step of the web design process, the
graphic design comps are converted into code (HTML, DHTML, CSS,
scripting, database tables, etc). The site is built and tested on a
domain or subdomain of a development server that has the same
technical specs as the live server will have. When the site is fully
functional on the development server, it is migrated to the live
server. This is the final deliverable of the web design project.

Note: The CS5 version of Fireworks allows the user to create
interactive wireframe prototypes. Really cool feature!


END


Writing a Scope Statement


http://www.brighthub.com/office/project-management/articles/2491.aspx
This article illuminates the necessity of an effective scope statement
and how to write one that will help guide a project to successful
completion. The various sections of a scope statement are discussed,
as well as hints on how to minimize scope creep.

Writing a Scope Statement
Article by Eric Stallsworth (9,740 pts )
Edited & published by Michele McDonough

Read more: http://www.brighthub.com/office/project-management/articles/2491.aspx#ixzz1DanD3CHx

Introduction - Where to Begin
A scope statement is one of the most critical pieces of a project, and
writing one can be a difficult task for a project manager – no matter
what type of project management methodology is being used. But, an
effectively written scope statement can help the rest of the project
flow along with minimal problems. Lets take a look at how to write a
good scope statement, its necessary components, and the pitfalls to
avoid during its creation.
The firsts step on writing a scope statement is filling in the project
name, project charter, and a listing of the project owner, sponsors,
and stakeholders. Next, A project justification will need to be
identified, as well as project requirements, milestones, and
deliverables. Any non-goals - items that fall outside of the scope of
the project - need to be identified here. And finally, cost estimates
need to be provided within the scope statement. This information may
be readily available or it may need to be compiled from various
sources, but the scope statement is where it needs to be documented
all together. This can be a cumbersome task, but it is a necessary
one. As the project progresses, everyone involved knows where they can
look should a question arise.
A scope statement is just one of many free project management forms
and templates available for download at Bright Hub.


Read more: http://www.brighthub.com/office/project-management/articles/2491.aspx#ixzz1Damw2Rhc


http://www.brighthub.com/office/project-management/articles/57950.aspx
Project Scope Examples
Article by Ronda Levine (55,975 pts )
Edited & published by Michele McDonough (176,424 pts ) on Nov 30,
2009
See More About: Software DevelopmentAccounting SoftwareScope Statement

This article gives actual examples of real project scopes for real
projects, then discusses them to determine what should be included in
a scope statement and what should be left out.
Constructing Powerful Scope Statements
A successful project scope statement should be concise and clear.
Anyone reading the statement should have a good idea of what the
project consists of (and what will not be part of the project). This
statement will give a view of the project. It is also important to be
specific in a project scope statement. For example, "The catalog will
feature 100 products" is better than "The catalog will feature many
products" and "The project will be completed over six months" is
preferable to "The project will be completed over a period of time."
The more specific you can be, the better. In order to better
understand ways to construct scope statements, let's look at a few
real-life examples.





Hope this is helpful ;) Please share your thoughts.

Cheers,

Jen

[CCarpenter]

Jen,

This is great. I need to spend some time to digest this info. My
experience with creative briefs is they help a designer focus and not
loose time trying to figure our what to do in problem solving it also
is helpful for the client to no get frustrated in the process as
well.

On Feb 11, 8:57 am, Jen <jennifer.willoug...@us.af.mil> wrote:
> Here's a place to start:
>
> At AI, I begain my Web Design class by looking at all the steps
> involved with designing a web site. We spent time talking about the
> discovery phase in which I gave a list of targeted questions for the
> client in order to determine a statement of purpose.  I stressed how
> all the steps in the process then needed to support that statement.
>
> To address the question as to who provides the objectives, I think
> that first your students should be provided with a detailed creative
> brief which outlines the projects objectives. The second year student
> might be better enabled to conduct a mock interview during the
> projects discovery stage.
>
> Project objectives should be a clear list of deliverables which help
> to describe the Project Scope. Normally Project Scope is more of a
> project management issue, but I think it is importiant fot students to
> have the tools necessary to avoid scope creep, which happens when
> additional project requirements a are added without regard to budget
> and timeline.
>
> Here are examples of specific deliverables related to Web Design and
> Project Scope:

> (I found these examples athttp://www.tpdesigns.net)

>
> A good number of documents are created during the web design process.
> There is certainly a lot for the competent web designer to document
> throughout the discovery, planning, design, integration and delivery
> stages of a complex web project. Not all of these documents are of
> interest to the client, and over the years I've learned only to
> present the minimum number of documents needed to ensure a successful
> project. The following are the standard deliverables I ask my clients
> to sign off on.
>
> Creative Brief
> This is a project definition document. It includes all the
> requirements and specifications of the project, including scope,
> audience, objective, call to action, and technical specification.
>

> Download Creative Brief Worksheethttp://www.tpdesigns.net/downloads/CreativeBriefWorksheet.doc

>
> Content Outline
> The content outline defines every piece of content that will appear on
> the website. If it isn't on the content outline, it isn't going to
> appear on the website. The content outline is part of the information
> architecure, and as such should be organized in a hierarchy that
> represents the structure of the website rather than a hierarchy based
> on arbitrary categorization of content.
>

> View Sample Content Outlinehttp://www.tpdesigns.net/tutorials/sample-content-outline.htm

>
> Site Map
> The site map represents the structure and navigation of the website
> and should closely coincide with the content outline. There should be
> a common numbering system in place. Pages are represented by boxes and
> links by arrows.
>

> View Sample Sitemaphttp://www.tpdesigns.net/tutorials/sample-sitemap.htm

>
> Wireframes
> Wireframes are schematic versions of the pages on a website and should
> similate the final navigation, although the page layout at this point
> in the process is rough. Wireframes can be made into clickable web
> pages, allowing the client to preview the navigation of the site in
> action. Each wireframe should include all pieces of content that the
> final web page will display.
> Note: The CS5 version of Fireworks allows the user to create
> interactive wireframe prototypes.  Really cool feature!
>

> View Sample Wireframehttp://www.tpdesigns.net/tutorials/sample-wireframe.htm

> Read more:http://www.brighthub.com/office/project-management/articles/2491.aspx...

>
> Introduction - Where to Begin
> A scope statement is one of the most critical pieces of a project, and
> writing one can be a difficult task for a project manager – no matter
> what type of project management methodology is being used. But, an
> effectively written scope statement can help the rest of the project
> flow along with minimal problems. Lets take a look at how to write a
> good scope statement, its necessary components, and the pitfalls to
> avoid during its creation.
> The firsts step on writing a scope statement is filling in the project
> name, project charter, and a listing of the project owner, sponsors,
> and stakeholders. Next, A project justification will need to be
> identified, as well as project requirements, milestones, and
> deliverables. Any non-goals - items that fall outside of the scope of
> the project - need to be identified here. And finally, cost estimates
> need to be provided within the scope statement. This information may
> be readily available or it may need to be compiled from various
> sources, but the scope statement is where it needs to be documented
> all together. This can be a cumbersome task, but it is a necessary
> one. As the project progresses, everyone involved knows where they can
> look should a question arise.
> A scope statement is just one of many free project management forms
> and templates available for download at Bright Hub.
>

> Read more:http://www.brighthub.com/office/project-management/articles/2491.aspx...