There is much to be said about offering bells and whistles, but in the world of Requirements Prototyping there’s no point until you have a solid foundation on which to build.
So, focus on getting the basics right, keeping it simple to start with and only add detail once the foundations are good.
Solid advice for a successful design.
Though it’s often overlooked, one of the best things about using Prototyping techniques is its responsiveness to change – no long-winded change approvals process; no complex recompilation; lower technological barriers to implementation.
All of these things mean that when the customer decides that page A should look a bit less like page B and a bit more like page D, the obstacles in your way are few and you can deliver that change with a very quick turnaround. If you’d skipped prototyping and straight to the build phase, such change would be long-winded and slow to implement.
Responsiveness keeps people happy, and happy customers are repeat customers!
You are currently browsing the Prototypically Speaking - The Software and Requirements Prototyping Blog blog archives for September, 2009.
