Tencent QQ designers talk about how to build a more lightweight development process

Web page Production WEBJX article introduction: Tencent designers talk about agile development.

Tencent has been promoting agile development and is also emphasizing agile development, but you will find that, even so, it will fall into the following scenarios

• An ugly and long seminar
• Looks like there's never enough hands.
• Unrealistic ideas.
• Hanging over the function point
• Endless Preference Settings
• More and more tangled up in details
• Project still postponed

How do we build a more lightweight development process that allows us to deliver results faster and better? As a designer, how to be a part of agile? Here are some tips and ideas that I would like to share with you

1 interface Advance

As a designer, the simplest way to make people understand your idea is to draw it first, not obscure language and structure, after all, not everyone can translate your language into images. and the interface (visual, interactive) design is relatively lightweight, it is simple to modify, the cost is low. But modifying the program is far from the case. Keeping the interface in front gives you a lot of flexibility, at least before you start developing.

Interface in advance another of the most important reason is that for users, the interface is your product, the interface can help you from the user perspective of their products, how to show how to operate, how to feel, is not easy to use. Only when you are faced with a real interface can you answer these questions, and the document profile does not help you solve the actual user experience problem.

No need to focus on details at the beginning of 2

Although people always say that success comes from the details, of course, this is very true. But upfront attention to detail can also make you stop. First set the big frame down, instead of always obsessing over

• What's the best way to write this tip?
• is the text size 16 or 14?
• You're not going to move 1 pixels to the left?
• Here, add a high light.
• To turn 2 pixel strokes into 1 pixels.

You need to focus on the details, but not now. Everything has to be done from big to small. First make him, put the things put up, and then actually to use.

Details are the ones you use to show up slowly, and only in use will you find out what's more interesting. If you have enough time, of course you can do everything, if not, please focus on the most important things first.

3 don't dwell on problems that have not yet become a problem

"What happens when our users use this feature to work with another feature?" ”

If you want to quickly release the version, first solve the present. Don't spend too much time thinking about problems that have not become troublesome. Don't worry, you have a later version.

And you're so sure the user wants to work with another feature? If not, put aside first, and so on when the problem really surfaced, then to quickly resolve.

4 Help Product manager Streamline functionality

It seems that everyone is yigujin with a crossbow, more than anyone else. Competitor's Products If done * * *, we have to do * * *, they have 4 functions, we will do 5. If not, what are you going to compete with?

This is not going to work, because you will find that it is always catching up and never going to lead the day. What to do?

Do less

By doing less to defeat them

The more functions you do, the more complex the interaction between functions, and the higher the cost of the user's learning. And do our users really use those advanced features? Will they be a dime a few, but we're tired of the smart set-up? Try to do less, make your product lighter and more approachable-no one likes to use software that looks stupid to you.

5 function between the less involved

Make a functional point as independent as possible, to ensure faster and more flexible requirements change.

If the function is too much involved, just as you are covered with spider silk, each to make a little change, the other to change, from design, to development, to testing. When you find that the cost of change is too great, you will give up, and still carry the defective function along the way.

Why not start off with as little involvement as possible, so that you can get more comfortable

6 to have their own ideas

Although the interaction design is always in the black and white stage, because there is no absolute right and wrong. But we still need to be firm in our own ideas. Maybe the decisive point of view seems defiant, but it's always better than those "uh ... In fact, this also becomes ... "ambiguity is much better." What is needed in agile development is a quick decision, not a wishy-washy.

————————————————————————————————

Perhaps not all projects are suitable, after all, the initial consideration of the details must consider the cost of late changes. But for a new product, quickly reach the user, let the user to use, verify, feedback, get the data more real and effective. The adjustments made based on these feedbacks are always simpler and more responsive to the needs of the user than their own head.

Agile, not just stand-up morning, iterative summary, theory, documentation, more needed to do is to make it come out.