Microsoft team: Tips for Success (2)

Original article: http://www.blogjava.net/leeguannan/category/29681.html

Rule 6:

Watch the ratio

"The basic principle is that the ratio of developers to warranty personnel should not exceed." This is the suggestion made by the author, and the ratio of Sun is changed to or even, it can be seen that the product protection personnel are more important than the developers in the project!

"In fact, we are responsible for the completion of the software on schedule. When the progress lags behind, the first thing we should look at is the Quality Assurance personnel: Is there enough people? Are you fully authorized? Are you sure you want to participate in the design? Can I work well with developers on schedule? Can I give a warning immediately when a problem occurs? Do the Product Warranty personnel and developers share the same philosophy? Isn't it just getting too close to developers ?"

"A sound software development team must comply with the above-mentioned proportion principle. The average number of developers supported by each person is no more than two ." Can this be done? At least in our company, it's basically hard!

Rule 7:

Use feature teams use special supervision team

With the full authorization and responsibility of tasks (I d e n t I t y), people have control and influence, and more importantly, they can integrate themselves with tasks.

Building consensus (c o n s e n s u s) is the atmosphere of the special supervision group.

Equality of status (B A L A N C E) because each Member of the special supervision group has different backgrounds, expertise, different job roles, and different ideas, no one is superior to anyone, so everyone is equal.

The Authority is from knowledge, not from position.

In an ideal project, there are basically two roles: creators (C r e a t o r) and promoters (f ac I l I t a t o r ). Creators are professionals, such as development programs, marketing, software warranty and document writing, and promoters are responsible for building team consensus and maintaining the best development environment.

Rule 8:

Use Program Managers Project Manager's Responsibilities

The project manager is part of the software development team and is responsible:
• Lead everyone to define a successful product.
• Guides everyone to inject deep expectations and beliefs into products.
• Lead the team to realize the ideal and become a foreseeable product.

The project manager should have a technical background and be very specialized in two aspects: first, he is familiar with the technologies used by the development products, and second, he must have the technical leadership ability to build the software. The project manager must be good at deception, drive, encouragement, and require his team to make the best software and demonstrate the best performance. He knows the input and output details of each item in the software production process, he must understand how to define products and maintain sound technologies in the best way. Finally, the project manager must be a team spokesman for the media, customers, and the entire organization.

The project manager is the core character of software development.

Do you want to know about this team? Check their software and vice versa.

Team spirit:

1. A group of people work together to gather their brains and create a smart property together.

2. personal creativity is a magical thing derived from the potential of human mind, which is enriched by emotion and bound by technology.

3. A group of people contribute their creativity wholeheartedly and combine them into great strength. The creativity of the combination is more complicated because of the interaction and agitation of the group.

4. In such a complex situation, the leader becomes like a symphony command of interpersonal interaction, assisting and guiding various subtle interpersonal communication.

5. When communication and interaction in a group are correct and healthy, the power of the group can be fully combined, and the effect of adding and multiplying will be produced to offset the mutual exclusion. Smooth communication enables full communication of ideas in the team.

6. The quality of team work is more important than the time schedule, and the greatness of the work requires a special enhancement to the "Team Spirit" to be achieved. "Team Spirit" can be regarded as the average value of the spirit of individual members, while the personal spirit (p s y c h e) is the internal force that enables him to feel, think, and deduce.

7. If the "Team Spirit" is ignored, only mediocre results will be produced.

Rule 9:

Be an authority, not an authority figure requires authority, not hegemony

The purpose of authority is to make every team member have their own professional authority and the professional confidence of the team. This is the true authority of managers.

Competition

Innovation is everywhere and never stops!

If you cannot grasp the pulse of the times from time to time, if you are idle in responding to rapid and drastic changes around you, especially the actions of competitors, if you cannot continuously create new technologies, you will always stay ahead, then others will immediately take advantage of it, replace you and become the winner in the market, capture the hearts of customers and their purse.

After you confirm your situation, you should first consider taking the standard footwork.

Standard footwork:

Rule 10:

Alone? A market without a competitor ain't no competitor? Not necessarily a good thing

(Note: Anyone has enemies !)

Rule 11:

Dead Beat? Break out of a feature shoot-out competitors keep up? Introduce innovative features (Note: Try to suppress your enemies !)

Rule 12:

Behind? Ship more often with new stuffs behind competitors? Increase investment and release new versions faster (Note: Please feel down and regain your territory !)

Rule 13:

Ahead? Don't ever look back ahead of competitors? Don't look back (Note: Challenge yourself and defeat yourself !)

Introducing new products on time and frequently is the biggest rule in the software development industry.

Rule 14:

Take the oxygen Gen along to keep it fresh

The pace of rapid changes is the norm of the information society. You must move forward quickly; otherwise, it will fall behind.

Customer

Try your best to make customers fall in love with your products!

Rule 15:

Enrapture the customer surprise the customer

The customer's lowest hope is that you can understand the painful experience he has experienced.

Rule 16:

Find the sweet spot to find the target

Rule 17:

It's a relationship, not a sale to establish relationships with customers, rather than selling products

Rule 18:

Cycle of cycle rapidly acceleration product launch