If this were an issue I had, I would probably still write at least some user stories. You can write user stories quickly, and your client should be able to sign off on them just as quickly. If they can’t, then clearly the documentation they gave you isn’t adequate for you to successfully build the project. Better to learn that up front.

I would also prototype as appropriate. The problem with the ‘frozen’ design you’ve been handed is how to handle unforeseen issues. What happens when a slight change to the design could result in huge development savings for the customer? How about when you uncover needed functionality that was missed in the flat development phase?

The bottom line in your scenario is that the ‘shared’ aspect of shared understanding is missing. Spending some time writing user stories and/or prototyping key concepts will give your client important feedback about how you are interpreting the design documents you were given. They can correct you if you’re wrong.

The step of creating technical specs to me comes after the user stories and prototypes. Once everyone understands what you’re trying to do, then have engineers find the best solution and adequately document tasks so that the work can be parceled out.

Hope this helps.

Wondering if you can chime in on the following situation: We are working with a client who has engaged a creative agency. The client and the creative agency worked together to produce designs that were subsequently signed-off on.

As the technical agency (responsible for the technical aspects of making those designs “come-alive”), do we now go through the process of creating user stories? From my experience, user stories typically drive wireframes and design efforts. In this case, we are being handed completed designs. So what’s the best way of creating technical specs from these designs (for front-end/creative and back-end engineers)? What’s the best way to ensure that technical development activities fulfill what’s laid out in the designs?

One approach I am considering is to have the designs annotated with interaction specifics, data sources/attributes, etc, so that the Development and QA team have a visual (rather than the typical flat user story) reference.

Would love your thoughts.

Andrew