Saturday, June 23, 2012

The Agile Management Project Cycle For Wireframes

Youre going to start a new web project. Thrilling. You have a great idea, or maybe a big assignment, and have to work it through the initial ideas to the final launch. From wireframe to done. How to get there?

Justinmind Prototyper is a software suite done to help you along these steps. Its meant to organize and facilitate communication between several professionals involved in any site or application development.

Justinmind Agile Methodology for Software and App Development

At Justinmind, we suggest a Methodology based on Agile, with four main steps:

Functional Requirements Capture, in which users research, discuss and decide what is the requirements, what should be done and create a document where it should be explicated. Low Fidelity Prototyping, in which professionals create a wireframe of the project, which describes hows it going to be, what are the links, the content and the basic layout. How its going to work, all the steps, phases and r equirements? With text? A simple wireframe that shows where things will be? High Fidelity Prototyping, in which users simulate the final product with an easy drag and drop application creator. Sometimes, you need to show relations. What kind of information a box shows when a button gets clicked, and how that colour changes when the mouse goes over. All this must be in the final product, so it has to be planned, specified and coded. So, you have to put this kind of information on the final project. In this case, a lo-fi wireframe is not enough. These wireframes work just as a map of the web, but for a bigger site, youll need to show the relations. So, the ideal solution is a high-fidelity screen mockup. A file that works just as if it was the real website, reacting and interacting with the user. That cannot be done with a simple drawing tool, neither with paper. Validation, in which the simulation is tested with real users, project managers, and client/co-workers. Then its all documented and registered to allow the final developers (coders, designers, etc) to build it exactly as it was approved.

This four-iteration cycle should last for approximately a month, from scratch to fully functional project, with a team working full time. The prototyping phase normally takes 10-15 days on average for a project with 80 screens.

If you liked this article, follow our blog's feed or follow us on twitter.





No comments:

Post a Comment