Wire frame (wireframe), or not?

There is a saying "a picture wins thousand words", but the agile world has not remembered this sentence. At least, many designers in agile teams think so. In some teams, designers must create small design increments that do not necessarily produce the best results. For other teams, "wireframe" is the product of a bureaucratic system that hinders the efficient advancement of development efforts.

Booshtukka mentions that in the current situation, it is difficult to blame designers for agile Bufen. Agile processes want designers to deliver their designs in small increments. Creativity therefore faces difficulties.

It doesn't make sense: the idea itself is a whole. If someone wants you to draw a house, do it at 1.1. First, draw the chimney, then the window, then draw the mountain as the background, and then the main entrance. You're going to have to go crazy, and when you're drawing the next one, you have to change the previous part to make sure the whole thing is normal.

Sam launches a similar discussion at the Agile Usability Forum to understand the relevance and importance of wireframe. William Pietri responded to Sam, noting that it was largely up to teams and individuals to decide whether they needed a wireframe and how much detail should be achieved. He thought:

I do not think there is a unified answer to these questions. What we're looking for is the intersection of personal differences, team differences, and minimal waste. For me, the only way to achieve this is by constantly fine-tuning the specific process to see how to minimize the adverse effects while still producing excellent work results.

Gene Arch and http://www.aliyun.com/zixun/aggregation/13830.html ">paul Spencer mentions: According to their experience, wireframe has its intrinsic value, and in many cases, It can help them anticipate difficult situations. For them, their designers work with the product owner to design the highest priority content for the next sprint.

Pat Cheugn quotes the article "HTML wireframe and prototype: All proceeds, no pain", he says: For designers, you should use wireframe. In his view, the advantages of wireframe are more evident in the agile world.

Producing HTML wireframe and prototyping does make the development team as close to the final product as possible. It helps to filter bad ideas and let good ideas emerge ... In particular, the online box can show the user flow and page flow ...

The biggest benefit comes from: wireframe can give you the green light to tell everyone that everything is ready and you can begin to implement back-end coding. From paper to computer without switching, or from the PSD file to the HTML, many CSS styles have been defined and implemented quickly, because the HTML wireframe is always defined in a range of ways.

Sascha Brossmann responded to a similar discussion and said that the most important reason for user experience design activities in an agile environment is to get a clearer picture of the world and keep it up to date before it begins to develop. He added: It would also be helpful if the wireframe could be created before the development of an iteration. Yoni added:

I have found that interactive prototypes (with varying degrees of fidelity) are the most effective deliverables in the agile environment, including other environments. Providing such an artificial output is more familiar to developers, and there is no need for more explanations and hands-on guidance after delivery, and the gap between communication is reduced.

William presents an interesting way to verify the needs and meaning of the wireframe for the team. He believes that there is always a difference between the developer and the designer's understanding of the wireframe. This can be helpful if the designer can show the meaning of the outlet box.

To convince developers of the value of your approach, try a variety of ways in some user stories and talk about what's going on in the review session. If you can find something they don't see, try to show them.

Jérôme Gravel-niquet complements the way their team thinks it works. He thought:

from the basic description of the user story, we quickly created the wireframe. When the wireframe is complete, we show the end user in the interview and collect feedback and adjust the wireframe based on feedback. When we have a solid backing (user and Board review) and full of confidence, we will design the interface immediately. With these things, we create documents that explain different interactions and functions (in wiki way). As a user experience designer who specializes in integration, I also try to integrate the interface and its related interactions before the developer begins the user story.

Therefore, everyone agrees with the meaning of the wireframe. It helps to achieve better results within the team and with stakeholders. The key is to do just good work and ensure that the process is lightweight. It is also important to ensure the high quality of the wireframe because, in Alex Jones's view, the rough wireframe corresponds to the Comic Sans font of the user experience.

View English Original: wireframes or No wireframes

Source: Http://www.infoq.com/cn/news/2010/06/agile-wireframes