Scribd
Upload
68 views1 page

Large Project Gantt Chart

The Gantt chart breaks a project into smaller tasks, showing when each task begins and how long it takes. It lists tasks in chronological order in the left column and uses timeline columns to indicate the weeks each task will take place. An example Gantt chart shows tasks for a project team from forming to their first design review on October 9, with some tasks spanning multiple weeks. The document provides categories of tasks that could be included in a Gantt chart, such as information gathering, problem definition, divergence, transition, convergence, and prototyping.

Uploaded by

Muhammad Yousaf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
68 views1 page

Large Project Gantt Chart

The Gantt chart breaks a project into smaller tasks, showing when each task begins and how long it takes. It lists tasks in chronological order in the left column and uses timeline columns to indicate the weeks each task will take place. An example Gantt chart shows tasks for a project team from forming to their first design review on October 9, with some tasks spanning multiple weeks. The document provides categories of tasks that could be included in a Gantt chart, such as information gathering, problem definition, divergence, transition, convergence, and prototyping.

Uploaded by

Muhammad Yousaf
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

ME450: GANTT CHART HANDOUT

The basic purpose of a Gantt Chart is to break a large project into a series of smaller tasks in an organized way. The chart shows when
each task should begin and how long it should take. The left-most column lists each of the tasks in chronological order according to
their start time. The remaining columns show the timeline (often shown in weeks, but use whatever units are convenient for your
project). For each row, a task is listed and a line in drawn through the timeline for the weeks during which that task will be addressed.

At right is a simple example of what a Gantt Chart Tasks 9/6 9/11 9/13 9/18 9/20 9/25 9/27 10/2 10/4 10/9
looks like. In this chart, a rough outline of what Form project team
task are to be accomplished up to the first design Information gathering
review on October 9. This is not given to show Purchase reverse engr’g product
you how you should organize your own teams Describe user experience
time so much as to provide a sample Gantt Chart Initial QFD / problem definition
for illustrative purposes. Notice the example uses Concept generation
the class lecture periods instead of weeks in order Functional decomp. analysis
to organize the timeline. Also notice how some Create Pugh Chart
tasks take longer than others, so some weeks have Perform reverse engineering
more than one associated task. For example, on Summarize info gathering results
the time period beginning September 18th, the Finalize Design Review #1 report
team will be continuing the information gathering Create Gantt Chart
started a week prior and begin shopping around Team Roles worksheet
for a product for the reverse engineering exercise Prepare DR1 presentation
on October 2. Design Review #1

So what kinds of tasks should you include in your own Gantt Chart? That is completely up to your project. Some teams will perform
many of the same tasks, but the time spent on them will vary greatly. Some projects focus on creating a new idea with little
prototyping time while the converse is true of others. It is up to your team to decide how best to break your project into more concrete
steps. To help you get started though, here is a list of categories that will help you determine if you’ve walked through the entire
design process for the Gantt Chart you will be providing in your first Design Review report.
Information Gathering: user interviews, expert interview, personal experience, patent search, market research, reverse engineering, …
Problem Definition: problem statement, characteristics of problem, characteristics of solution, …
Divergence: brainstorming, morphological analysis, functional decomposition, …
Transition: Pugh chart, QFD, sketch models, user feedback, …
Convergence: analysis, detailed configuration, optimization, user feedback, …
Prototyping: build rough prototype, test rough prototype, plan the build, collect materials, start machining, physical testing, user testing, …
Documentation: proposal, progress report, final report, presentations, …
ME450 – Fall 2002 – 1 of 1

You might also like