Shulou(Shulou.com)06/03 Report--

2.1 preview of jelly

Jelly: Super General, I did a preview when I heard that you were going to talk about MSF, but there are too many nouns in MSF. I really have a big head. Can you explain these two sentences: "one of the basic principles of MSF is to learn all the experience." This principle has been fully applied to the key milestones in the MSF process model, where we are willing to learn what is needed for the successful application of this key concept. The proven practice of being willing to learn this concept through post-milestone review is reflected in the project. In large and complex projects, Microsoft recommends using objective external service providers to ensure a fault-free environment and maximize learning. "

A Chao: the tongue twister you got from × ×?

Jelly: the official Chinese website of MSDN.

Sure enough, A Chao found this passage online (as shown in figure 2-1).

Figure 2-1

He read it twice with jelly and finally sighed.

A Chao: originally, MSF is quite simple and clear, but it is very mysterious and obscure.

Erzhu: is it intentional to be so obscure in order to slow down our progress and hinder the development of the software industry in our country?

Dasuan: I've heard MSF lectures before, and I think this thing seems to be useful for big enterprises. And MSF is easy to be used to cheat, I believe, a group of mediocre people, under the banner of MSF or mediocre people, but the red flag fluttering, can fool customers.

Lili: I read on the Internet that there are three big tricks in IT enterprises. Brother Da Shuan seems to have said the second one:

● programmers use UML to cheat

● Project Manager uses Process to cheat

The boss of ● uses corporate culture to cheat.

The fly next door poked over his head.

Xiaofei: jelly, I almost fainted when I heard you were previewing.

A Chao: how do you think we should study?

Xiaofei: it's not easy to get out of school. I don't seem to be very interested in "learning" now. I forget something when I hear it. I just need to learn it now.

Jelly: it seems that you often learn pop songs, and you remember those lyrics very well.

Xiaofei: if it is singing and dancing, that would be impressive. Unfortunately, MSF doesn't seem to be able to sing and dance. Can you learn MSF in × ×? * and MSF are three-word English abbreviations, which should be compatible.

A Chao: jelly, you don't have to preview. I'll make a vernacular MSF. You'll understand it as soon as you hear it. In order to make everyone remember deeply, every basic principle of MSF is represented by a pop song, Xiaofei, what do you think?

Xiaofei: good! If you can speak MSF with class feelings, I can sing it passionately.

Chao, OK, then listen up.

MSF, or Microsoft Solution Framework, is the method recommended by Microsoft to make software.

A brief history of MSF: around 1994, Microsoft launched the Microsoft solution framework Microsoft Solution Framework (MSF) after summarizing the development experience and lessons of its own product team, as well as the business experience of Microsoft Consulting Services. MSF at that time was just a loose collection of these experiences and lessons. Over the next few years, MSF further absorbed the experience of various Microsoft departments and Microsoft partners in practical projects. In 2002, with the release of Visual Studio .net, Microsoft released a series of white papers on MSF 3.0, and large-scale training for MSF 3.0 began to be held in China. At that time, there was a national lecture tour of "Architect 2000", which was attended by many IT enterprises.

In 2006, MSF 4.0 was released with Visual Studio Team Foundation 2005. It adds a lot of agile development content, and clearly describes the typical process of team collaboration and its application in the new team collaboration software package VSTS.

In 2008, with the release of Visual Studio Team Foundation 2008, MSF 4.2 has some changes in text and expression, but the spirit is very consistent with MSF 4.0.

Jelly: what year did 2.0 come out?

A Chao: do we need to care?

Lili: jelly is afraid that you will get this question in the exam.

A Chao: we can ignore the details of the evolution of MSF, to remember that all patterns are not immutable, the key is to grasp the reasons for the change.

2.2 basic principles of MSF

MSF has eight basic principles, all of which I translated into Chinese and added my understanding. Let's discuss it separately:

(1) promote information sharing and communication (Foster open communications)

(2) working for a common vision (Work toward a shared vision)

(3) full authorization and trust (Empower team members)

(4) perform their respective duties and be jointly responsible for the project (Establish clear accountability and shared responsibility)

(5) attach importance to business value (Focus on delivering business value)

(6) stay agile and anticipate change (Stay agile, expect change)

(7) Investment quality (Invest in quality)

(8) learn all the experience (Learn from all experiences)

2.2.1 promote information sharing and communication

The first principle, in vernacular terms, is that all information should be kept and made public, that the discussion should include all the roles involved, that it should be made public, and that everyone should be informed. Of course, necessary protection measures should be taken for information involving technical secrets, security, and so on.

Erzhu: we used to be "the boss let you know, you will know, do not ask." Doesn't it look easier to control?

A Chao: in the past, when two or three buddies were messing with the software together, everyone knew the bottom and didn't seem to realize the importance of "communication", but with the increase of project complexity and team size, it would be impossible without information sharing and communication.

Erzhu: if there is something, I am not sure whether to inform a certain aspect of the personnel, what should I do?

A Chao: in this case, I'd rather communicate too much.

Xiaofei: isn't that annoying? I have to keep telling people that I have just done something, and there seems to be a lot of things on the Internet about "if you change a text error in a document, you should send an email to tell the world"....

A Chao: yes, people can't be tired to death by the rules. It's best to let these notices be passed on naturally to people who care about these things as events occur. For example, in TFS, you can set an Alert so that TFS automatically informs you of your concerns. In addition, in TFS, all information related to the project is saved. For example: all work items and their history; all source code modification records.

One question that TFS users often ask is: why can't I delete work items in TFS?

The answer is simple: the first principle of MSF: all information is kept and made public. TFS records are like cash flow records in a bank account and cannot be deleted.

Some people have made some stupid mistakes (such as a very low-level Bug), and TFS has recorded them all. From a personal point of view, some people will say, "I know I have made a mistake and have corrected it, so it is better to delete the original record." isn't this conducive to building a harmonious team?

A Chao: harmonious "Harmony" is a "word" and a "all" word, which means that everyone can speak and everything should be recorded. The notes can be left behind, which can be analyzed after doing things, and learned for later colleagues, or colleagues in other projects. If deleted, it would be a violation of principle 8, "learn all experiences". If history is a confused account, some events have been deleted, or can not be mentioned, where is the harmony?! If our company wants to establish a culture of "things but not people", there seems to be an old saying that people's mistakes are compared to solar eclipses.

Jelly: "the fault of a gentleman is like the eclipse of the sun and the moon: when it is over, everyone sees it; what's more, everyone admires it." And, "who has no fault? it is a great thing to change what is wrong."

We used to have a lot of things about the project in the belly of several leaders, and the most open thing is to list some problems in Excel files or MS Project files, but there is no historical record either.

A Chao: if you can't see all the information, then the progress of the project and all kinds of problems in the project can't be made known to everyone in time, so the other principles in MSF can't be implemented. Without open information, there can be no "delegation", or "establishing clear responsibilities and shared responsibilities" and "staying agile and anticipating change". This is why "promoting information sharing and communication" is the first basic principle.

MSF team model and MSF process model are also based on the principle of "information sharing and communication".

Xiaofei: for this principle, I would like to recommend Yu Chengqing's "Please Open the window"--

If you fall in love, you can easily guess the result.

Who needs to communicate with sincerity?

……

2.2.2 working for a common vision

A Chao: "working for a common vision", how do you understand this sentence?

Miscellaneous said: this is the so-called one heart and one mind. If a brother is of one heart, his advantage will break the gold. Of course we are of the same mind, we are all buddies, and we are all here for the prosperity of the company.

A Chao: OK, but it mentions a "common vision". What is this?

Miscellaneous said: that is, we are going to send it in the future!

A Chao: Fa is sure. Please note that this "common vision" refers to the vision of the product. We make a product, whether it is application software, industry software, or general software, to be clear about the goal of the project.

(1) this goal must be clear and unambiguous.

(2) this goal cannot be achieved at present, but must be achieved through hard work.

(3) this goal is not vague, it should guide the work of project members on a daily basis. When you come to work every day, if you find that what you are doing is not helpful to the vision of the project, you should bring it up with your boss.

Lili: some of our projects don't seem to have such a goal, or the boss doesn't know what we're going to do.

A Chao: well, it's obvious that the leaders of these projects failed, and it's not surprising that these projects didn't achieve the expected goals in the end, because we don't even know what the expected goals are.

Can you give me an example?

A Chao: for example, there was a sports news website in our village. At that time, its vision was--

"the Mountain removal Sports Network provides real-time and accurate sports news, forums and a network of sporting goods shopping, so that sports enthusiasts can share a fair, healthy and safe communication environment."

At first, I did a good job, and I often patronized and visited, but then it seemed that the quality of the news and forums had declined, and there was nothing below on the shopping webpage. After several revisions, the headlines were often made through the grapevine about sports stars, the legendary size of BWH with their legendary girlfriends, and the news that the middle and upper echelons of Hequ village competed for a certain drink. I've always wanted to ask who is the editor.

(hands up) I am the editor-in-chief of the mountain moving sports network. at first, what I do every day is consistent with our initial vision, and my popularity is also good, and then we go up to whatever we think can attract the eyeball. it slowly turned into four dislikeness, and the reputation was ruined. Our internal vision has been changed to--

"the mountain-moving sports network needs to attract attention and advertising until a buyer is found."

Big Shuan: Daniel, when did you change your vision? I wasn't aware of that?

This is to ask A Chao.

A Chao: there is nothing wrong with such a vision, but don't forget that we are talking about a "common vision", that is, team leaders should make all members agree on the vision of the project and strive for it. If some people are still fighting for Vision 1.0, but the other half are working for Vision 2.0, something will go wrong.

If there is no "common vision", even if the team releases the product, different members will have different views on whether the project is successful and how it will develop in the future, because their vision (frame of reference) is different.

Xiaofei: by the way, what about the drinks contested by the middle and upper echelons in Hequ village?

Don't mention it. They used the goods to cover the advertising fee, and the boxes of drinks left in the office were later carried back by my father to feed the pigs.

A Chao: in addition, at the critical moment of the project, it is too late for us to unify our thinking and yearn for the vision.

I think of the performance of the national football team in a certain World Cup. In the middle of the qualifying match, the leader of the Football Association asked all the players to take an oath to the national flag. I thought it was very funny. If everyone usually has the same goal, taking this oath is just a formality. If everyone usually does not have such a goal, suddenly taking an oath will not suddenly make the players more patriotic and better on their feet.

A Heng: another example shows that the vision is also closely related to the actual work. When Dasong Bowen was engaged in "devil training" in the Chinese women's volleyball team, if everyone's vision was not a world champion, why bother? Practice casually every day, wash up early and go to bed.

A Chao: yes, if the goal of our company is to play with the website as an amateur, why bother to learn MSF?

Xiaofei: is the vision determined by the leader, or is it formed from the bottom up?

A Chao: it is usually put forward by "people with foresight" and then discussed openly. In the process of discussion, misunderstandings can be eliminated and consensus can be forged. This is the key to a project and the main goal to be achieved in the first phase of the project.

Erzhu: is this the so-called "unified thinking", or another common saying "brainwashing"? Isn't it said that brainwashing is not popular abroad?

A Chao: you can look at it this way, but let's talk about another basic principle, which requires your brain to be original.

Xiaofei: brainwashing back to brainwashing. I want to use this song to express my feelings after brainwashing.

The record in the sparkling red star

Turn into a dialogue at this time.

Hippopotamia

……

2.2.3 full authorization and trust

The key to this point is the word "authorization". What does it mean by "Empower" in English?

Empower has two meanings: one is to give someone power and authority (Give authority to somebody:to give somebody power or authority); the other is to give someone more confidence and self-esteem (Inspire somebody with confidence:to give somebody a sense of confidence or self-esteem).

In an efficient team, all members should be fully empowered and have the right to complete their tasks in accordance with their own commitments within their own purview, at the same time, they also fully trust other colleagues to fulfill their commitments. Similarly, the team's customers (both internal and external) believe that the team can deliver on its promises and plan accordingly.

Erzhu: this seems to be very dangerous!

A Chao: what should I do then? In the way of "command"?!

Fully authorized management is one of the core concepts of MSF. The MSF team model is based on the following two principles:

(1) Equal cooperation-- the relationship between members and teams is equal cooperation.

(2) fully delegate to the team and members.

This is why the MSF team model is a mesh, not a hierarchy.

What's the advantage of doing this? There are two advantages:

(1) the authorized person will take responsibility for the project and expect colleagues to be equally responsible for the project.

(2) MSF advocates bottom-up planning, in which everyone has full power to estimate and decide how long their task will take, rather than the time assigned by their superiors, which means that the person who really does it will complete the task according to his own estimate. What is the result of this? Everyone will support the plan and schedule of the project, because this schedule is worked out by everyone from the bottom up!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.