Project tasks - estimating

22 Mar 2004 - 8:42am
10 years ago
1 reply
585 reads
Narey, Kevin
2004

Hi,

Perhaps it would be helpful to all if we all agreed on a standard task list
that we could all use for estimating on jobs. Obviously each project has
it's variables, but broadly speaking, our tasks are the same. So - here's a
short generic list to be added to with your help, so that we can all use it
as a reference in the future. The user of the list would pick appropriately
from this list.

Assumptions:
a) Web based front end to an application
b) Analysis has been done already without any involvement from an
Interaction Designer
The output from this exercise is a 50+ page document of requirements
c) The role on the project that you are estimating for would be as an
Interaction Designer (or a team of)

Task list: (not in any order)
1. HTML, Javascript, CSS Coding, image manipulation/optimisation
2. Logical naming and labelling of display components
3. Refinement of navigational and functional control elements
4. Design a consistent data display model (grid-based)
5. Refine screen process flow
6. Design/Choose appropriate imagery (icons & photography) and colour scheme
7. Justify and document all design decisions for display elements
8. Logical grouping of contextual elements

It's not a great list but it gives you an idea of what I'm talking about.
The result should be something that a project manager could dump into MS
project. This might turn into "An Interaction Designer does the
following....".

Wadda ya fink?

Kind regards

KN

**********************************************************************
gedas united kingdom limited
Registered in England no. 1371338

This email and any files transmitted with it are confidential
and it may be privileged.

It is intended solely for the use of the individual or entity to
whom it is addressed.

If you have received this in error, please contact the sender
and delete the material immediately.
**********************************************************************

Comments

22 Mar 2004 - 9:11am
Todd Warfel
2003

I think you're on target with the concept, but if you're going to drop
this into Project/FastTrack, then wouldn't you want shorter terms for
items 1-8 that they could select from? Consider that this might also be
used in a Web-based project application, so these options might go into
a dropdown menu or similar.

We use something like:

1. Non-billable (for things like invoicing clients, new biz
development, lunch, etc.)
2. Kick-off Meeting
3. Planning (planning for site visits, field research, testing, etc.)
4. User Research (any kind of UR - surveys, contextual analysis,
content analysis, ethnographic research, interviews)
5. Information Architecture (card sorting, taxonomy development,
sitemap, process/flow diagrams, task analysis grid, conceptual model
development)
6. Interaction Design (wireframes, paper prototype, interactive
prototype)
7. Visual Design (visual comps, imagery, brand/ID development, style
guide)
8. Production (HTML, CSS, JavaScript, Image Processing)
9. Engineering (database development, server-side development)
10. Content (content inventory, copywriting)
11. Usability Testing (testing, heuristic evaluation)
12. Analysis & Reports (content analysis, usability analysis, draft
reports, final reports)
13. Documentation (requirements)
14. Presentation (client presentation)
15. Strategic Consulting (general consulting, vendor evaluation)
16. Training (UX Training, Standards Training)
17. Materials (software licenses, hardware, printing, expenses)
18. Travel (transportation, airfare, hotel, food, entertainment)

Incidentally, the items listed in the brackets "(" ")" are typically
our sub-tasks.

On Mar 22, 2004, at 9:42 AM, Narey, Kevin wrote:

> Task list: (not in any order)
> 1. HTML, Javascript, CSS Coding, image manipulation/optimisation
> 2. Logical naming and labelling of display components
> 3. Refinement of navigational and functional control elements
> 4. Design a consistent data display model (grid-based)
> 5. Refine screen process flow
> 6. Design/Choose appropriate imagery (icons & photography) and colour
> scheme
> 7. Justify and document all design decisions for display elements
> 8. Logical grouping of contextual elements
>
> It's not a great list but it gives you an idea of what I'm talking
> about.
> The result should be something that a project manager could dump into
> MS
> project. This might turn into "An Interaction Designer does the
> following....".
>
> Wadda ya fink?
>
> Kind regards
>
> KN

Cheers!

Todd R. Warfel
User Experience Architect
MessageFirst | making products easier to use
--------------------------------------
Contact Info
voice: (607) 339-9640
email: twarfel at messagefirst.com
web: www.messagefirst.com
aim: twarfel at mac.com
--------------------------------------
In theory, theory and practice are the same.
In practice, they are not.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 3097 bytes
Desc: not available
Url : http://listserver.dreamhost.com/pipermail/discuss-interactiondesigners.com/attachments/20040322/d3b6fc21/attachment.bin

Syndicate content Get the feed