It addresses both the argument for UI-first development and the need for a bridge (in the form of Chief Architect, in our case) between Product Management and Engineering.
Unfortunately, I have searched but have been unable to find out who the author of the cartoon is, so I can't give credit for it. If anyone knows, please submit a comment and I'll add an acknowledgment.
(Click the thumbnail to see the full-sized image.)
(Click the thumbnail to see the full-sized image.)
2 comments:
Loved the post, glad to find out that we're not the only ones with these problems. I'm researching tools that will help us more efficiently create prototypes and requirements documents. Do you have any advice on that?
Thanks for the feedback.
I'm afraid I don't know of any prototyping or requirements documentation tools. Since our application is mature, most of our prototyping can take place directly within our app (by copying and pasting code), and our requirements docs are HTML.
We've been talking about "paper prototyping" for a while, but we haven't tried it yet. Sounds interesting, and it presumably would allow you to get design ideas in front of stakeholders earlier.
Early and frequent "touch points" with your users are more important, in my view, than any specific tool or approach.
Are you using an agile development approach? If so, you should try to find (or start) an agile round table or user group or something in your area, so that you can bounce ideas off each other.
Post a Comment