Requirements Capture, Prototype, Design, Build, Release, Evaluate - repeat
Through an iterative process of Requirements Capture, Prototyping and User Testing involving all levels of the business, a successful product begins.
The Process:
Requirements Capture
Requirements Capture is an essential tool for any project. Understanding the Business, Users and Functional Requirements helps ensure the product is fully adopted by its users, leading to business success.
Prototype
Site maps, Wireframes and Prototypes are used to explore different scenarios and possibilities. They help in the discovery of the optimal layout, structure and functionality of a product.
Design
Treatments bring Mood boards and Wireframes together to give an idea of what a product should look and feel like.
Build
I believe in the Agile development process. Iterative and incremental in nature, it allows solutions to adapt and evolve in a rapid and flexible way through collaboration and interaction. The Agile Manifesto.
Evaluate
What was excellent yesterday may not be so good today. Users change, the environment changes and the competition changes so in order to stay competitive a product needs to adapt and improve.
Once a product has gone live it should continue to improve through Useability studies, customer feedback and studying analytics. From this analysis a new set of requirements can be captured and prototypes can be built. The process continues to the next, better release.
Entity Relationship Diagrams (ERDs)
Entity Relationship Diagrams or ERDs can be very useful for describing a process flow or user journey through a task.
