WHY WIREFRAMES ARE COMPULSORY?????

WHAT IS THAT?

A wireframe is basically a visual representation of content layout in a Web / Mobile App design. The wireframe shows the placement of page features, such as Menu, Header, Footer, Contents, Sidebars, Field Information and Navigation. It also specifies the placement of the elements within these content areas.

WHY WE USE THEM?

Tangible

Wireframes are tangible rather than imaginary. All Stakeholders in the software development project can feel the physical existence of the “to be system” at very early stage of the requirement analysis phase.

See what is going – right / wrong

Stakeholders get to know about what is right and what is wrong just by analyzing the visual models, i.e. Wireframes

Clarify your vision

Why is clarifying your vision a good idea?  When you know exactly where you’re headed, you’re way more likely to actually arrive. So the wireframes give you the direction as well as the precise

Just like building blueprints detail every aspect of the finished house, your business blueprint describes exactly how you imagine your business looking once all the building work is done.

Agile

Wireframes help to keep your project scope Agile in every way possible. “Quick feedback and scope understanding” is the Key.

User Stories and ACs

Wireframes help to describe user stories quickly, groom it and make it ready for the sprint with all possible scenarios of acceptance criteria. Hence the definition of done is always up to the mark.

Field Level Changes

Wireframes help to set exact field level expectations of all stakeholders. Hence your system verbiage gets groomed and reduce 11th-hour useless efforts to change it.

Dependencies

Wireframes help Technical Architects, Database Designers to find technical dependencies. It helps to find Functional dependencies while Requirement Gathering phase.

Design

Wireframes help designers to create designs in shorter time. If wires are as per expected user experience, creating and approval on system designs is a less time taking process.

Development

Wireframes help the developer in case of any understand query of the proposed system. This would be an initial reference for them to have a quick resolution.

Layout

Wireframes help to lock down basic system UI layout to be designed and developed. Discussions can be taken place welcomed on the layout in requirement gathering phase rather than development phase to avoid project delay.

Skeleton

Finally, wireframes would work as a skeleton, which would be further enhanced after agreed by all stakeholders.

WHEN SHOULD WE CREATE and PRESENT THEM?

Short Answer – As Soon As Possible

Long Answer – From very first day of initial requirement gathering phase to finalize the requirements and agreed upon mentioned scope.

THINGS TO REMEMBER WHILE WIREFRAMING

• Keep wireframes High level – Don’t put too many details on the wireframes
• Make it Flexible – Make sure that it is easy to adopt and editable
• Stick to a Pattern – Consistency is the Key to wireframing
• Don’t Focus on style – It’s about functionality, not Designs and Graphics
• Use Actual Content – for better understanding and clarity
• Add clarity of every functionality used