by Ryan Walker •

Web project process

Brain Dump

Using notecards or google wave, high-level brain dump of stories:

  • roles
  • action/tasks

When complete, organize content and transfer to digital doc, toss cards.

Modeling & User Stories

Develop “Ubiquitous language” — Words that work for both the code implementation and conversations with the customer. This language is also important for the screens, which need sentences + verbs (not typical programmer screens, which have lots of function, but no explanation.)

Add a few sentences to describe each story—just enough information to serve as a token for a conversation that will take place closer to implementation.

Release Stories

Select some stories for the initial release, err on the side of fewer stories.

Iteration Stories

Select just enough stories to result in working software that we can interact with in a meaningful way (maybe 2-3).

UI-First Development

Screens

  • Which screens - REST conventions can do a lot of work - what is the logical name of the noun-verb combination?
  • What’s on them - design from the inside out. Just the content without the outer frame of navigation. What matters to the user of the screen. What are they trying to do? Put in words what things they are trying to do on the screen, including the various paths they may take. (Don’t just assume the page should be a standard REST-template form.)
  • Be completely rational, “don’t make me think” - when I see the screen, I instantly know what to do with it, it’s easy to complete the task.
  • Least effective difference - give things visual priority, doing just enough to create the hierarchy

Flows

Think with actions, every action has 3 screens…

  • How you get to it
  • How do you do it
  • What happens afterwards - how do i know it worked. What do i want to do next?

HTML & Coding

Hopefully you know how to do this :)

Filed under Process Project Management Software Development Web Design