SIGIA-L Mail Archives: RE: SIGIA-L: Work hours estimation for I
RE: SIGIA-L: Work hours estimation for IA projects
From: Elizabeth_at_gr8.com
Date: Wed Mar 28 2001 - 19:28:29 EST
Ian,
Here's how I tackled the IA hours estimation problem. It's not foolproof,
and since there's so much variety out there I'm not sure how applicable you
might find it, but it's something:
I divided the IA work into deliverables that aren't functional page
schematics (FPS), and deliverables that are.
For us, "non-FPS" deliverables include: participation in initial
strategy/positioning if applicable; Project Brief; Asset Inventory & Content
Strategy; overall Site Architecture; participation in Functional
Requirements analysis.
These "non-FPS" deliverables are like fixed costs; figure out roughly how
long it takes to do each one. We do use a range, based on the complexity of
the site (for example, doing a site arch for a small site might take 2 hours
but a complex site might take 20). This estimate includes time for meetings
and correspondence, though you could break that out separately if you needed
to.
I'm using "functional page schematics" (FPS) to mean annotated diagrams of
individual pages/screens, that describe content elements, navigation,
interactions, and labelling. Some may call these "wireframes."
These FPS deliverables are like variable costs. First, one must estimate
(read: best guess) the total number that will be required. We usually try
and do a schematic for each unique type of page on the site. A small site
could have 5-10, a rich site might have 50+. Once I've got that number, I
multiply by 2 to 2.5 hours, again depending on complexity of site. Why 2 to
2.5 hours for every single schematic? It's a best guess based on experience.
It has to communicate to the client, the designer, and the programmer. Also,
this is "fully loaded", i.e. includes initial thinking and creation,
presentation to internal team, revision, presentation to client, revisions,
and distribution.
So, IA hours for a project could range from say 25 hours (small site, maybe
just a redesign with adjustments to navigation scheme) to 200+ hours (rich
content, complex functionality, large budget).
Hope this helps!
-Elizabeth
+++
elizabeth b. randolph ||__
director, information architecture ||
tel. 410.837.0070, x129
cell 443.324.1371
erandolph_at_gr8.com
Gr8, LLC
2400 boston street #301
the signature building
baltimore, md 21224
+++
> -----Original Message-----
> From: Ian_BAIN_at_nlb.gov.sg [mailto:Ian_BAIN_at_nlb.gov.sg]
> Sent: Monday, March 19, 2001 8:12 PM
> To: sigia-l_at_asis.org
> Subject: SIGIA-L: Work hours estimation for IA projects
>
> O.K. O.K. ....... I deserved the
> ribbing/consciousness-raising associated
> with "manhours" but to return to my question - has any one
> tried to estimate
> time for the various stages of an IA project - are they all
> so different?
===========================================================================
List archives are available at:
http://www.listquest.com/computers/tier2/computer_misc.html
--------------------------------------------------------------------------
To subscribe or unsubscribe, send mail to majordomo_at_asis.org with the
appropriate command from the list below in the body of the message:
subscribe sigia-l
subscribe sigia-l-digest
unsubscribe sigia-l
unsubscribe sigia-l-digest
This archive was generated by hypermail 2.1.2
: Sun Nov 23 2003 - 22:54:35 EST
|
