Managed by the software team with a buffet

I had a buffet with my colleagues just now, and I talked about a topic about the cafeteria. In order to make money, the buffet boss often tries to reduce the amount of food supplied, for example, using a small plate for expensive food or limiting the amount of meat to only two at a time, in fact, such a self-help restaurant is not profitable. Because the truth is very simple, customers queuing up for food in front of empty dining platforms naturally form a competitive relationship and have to spend more time "competing" for food. On the other hand, customers will obviously be dissatisfied with the self-help restaurant practice, and the best way to vent their dissatisfaction is to "eat the spent money back"-do not hesitate to eat your own food and anger with the restaurant boss!

Smart self-help restaurants pile up a lot of food, and even the most expensive food is also piled up on the menu, and the food will continue to be served before the customer finishes eating. This effect looks luxurious, but the diners do not have a competitive mentality to compete for food and will not feel angry with their stomachs. In fact, they will consume less food.

It may be because I recently acted as a proxy for the scrum master for some time and became sensitive to "management, as a result, the self-help restaurant management methods were applied to the software development team for comparison.

My previous development work was basically a well-known line of national conditions in team management: management is to formulate rules and regulations and then evaluate rewards and punishments. Once I got started, I went to take the exam and got a job with a thick job guide. In fact, the sum of various systems is nothing more than two words-deduction! This should be a routine that many Chinese colleagues are very familiar! In some cases, we can even hear the middle-level leaders reluctantly ask:"(This case/this person) How can I handle the charge ?"

When I met a rhetorical question like a leader, I felt powerless. Because I have no answer like the leaders!

But now, I feel like I can start looking for it and get close to it!

As mentioned above, when you are under competitive pressure, what you can do is to win more benefits for yourself-for example, to snatch food. When you are angry with the company's (fine) system, you may consider finding system vulnerabilities and using them for your own purposes.

You will find that you do not love your work, it is just a way to make money.

You will think that work is "selling lives" for the boss, not your "career ". (Maybe this is also why Chinese people are keen on entrepreneurship. It is purely speculation and basically reliable!)

Isn't the company system that generates your thoughts just as counterproductive as the stingy and harsh marketing techniques of self-help restaurants? If ~~ Without these rules and regulations, there will be free space for employees-just as there will be ample food resources for diners, the situation will be completely different:

It is like a cook who wants others to boast that their dishes are well-prepared and tailor-made. Others boast that their new clothes are beautiful.In fact, everyone has their own pursuits!

What do (qualified) employees consider when external restrictions (such as rules and regulations) on you become smaller or even absent?

Obviously, how can we do our job well!

OneProgramOf course, like a cook or tailorCodeElegant and efficient, and appreciated by users!

 

Looking at this, it is estimated that some people will laugh. Don't come with rules and regulations.ManagementHow do employees do things? Isn't that a mess!

I dare not say anything about other positions, but it is really feasible for the software development team!

Our CTO (once and once again, both of them are Swedes) has never been responsible for our job or how to do things.AlmostNo written rules and regulations have been issued to us, but the three development teams in our company have basically no major problems. The so-called "Chaos" has never happened! (This is almost because there is indeed a written duty system, but only this one)

Sometimes management is such a magic thing!

Well, there is no need to sell off anything. In fact, the magic thing is what we mentioned above: giving the development team free space, they will do things with their own good intentions-the Chinese saying is "well-known etiquette,Clothing, food, and honor and disgrace"-- What diners need to do when they don't need to grab food is to maintain their demeanor and experience food. When programmers don't have administrative pressure, writing better code is probably the most likely target!

 

When you read this, I have to admit that I have quietly changed the concept that our team has many "systems" when doing things. Fortunately, this concept is not too big because none of the "systems" in our development process are developed by our leaders! The developers, executors, and bound persons of these systems are actually everyone in our team.

What are we doing?

This question is not difficult to answer, but it applies the scrum agile development value"The Team regularly reflects on how they can improve their performance and adjust their performance accordingly."

Our team needs a reflection meeting after each development cycle ends (one or two weeks (Retrospective), I prefer to call it a day of regret. At the meeting, all the team members need to reflect on the situation. In this case, apart from the team members who are extremely self-critical, they generally point their points to others. If you have done something unpleasant during this time, you should be careful! (In bad smile)

ReflectiveConclusionWill be summarized to become the team's"System"Paste on the wall. At present, our team's system has already had three A4 Printing Papers hanging on the wall, and there are not many rules. However, no one will complain when executing these rules-because anyone has been involved in the formulation of these rules, and anyone knows why this rule exists. For example, the following are the rules I have just presided over after a confession:

L allocate time about old bugs list. Old unprocessedBugMaintain an evaluation form. L set some UI rules for all teams. (game team do it first)All teams should use the sameUIInterface Design L allocate 20% time off for on-call developer now, and change the value as average in future.Reduced normal workload of on-duty personnel20%. Change the ratio to the average value after a period of time. L whose bugs who fix shocould be faster, if you know whose it is.Who'sBugWho will fix it (if you know who wrote it ). L small defect need to be task/story if that need more than 0.5 hour to fix. Because QA wowould know there is something need to be test with task note.Any defect that exceeds half an hour must be writtenTaskOrStoryBecause of thisQATo know that something needs to be tested. L full integration tests before make a task as "finish ".Complete the test before completing a task. L keep api method clear and simple.APIThe method must be concise. L all stories in backlog need to be estimated. All team members do that on every Thursday.Assessment every ThursdayBacklogAll stories in the story should be evaluated. L no-planed refactor shocould be a task and one test task for it.Unplanned refactoring needs to be used asTaskAnd add a testTask. L pair work with new comer.Work with new team members. L bugs list on A4 paper is better than note paper.InScrumBoardBugUseA4Paper is better than paper. L discuss test cases when design meeting; Discuss bugs after scrum meeting.Test cases need to be discussed during design meetings.BugInScrumAfter the meeting. L ever bug need integration test, one at least. EachBugAt least one integration test is required.

In the above example, we can hardly see that such trivial details can only be called "rules" rather than "Rules and Regulations ". In addition, each team gets its own "rules" for different work content, work nature, and work methods ". So I believe you can forgive me for stealing the concept above!

In fact, the team members create and follow their own rules. Such work efficiency and achievements are far better than the achievements guided by the company's written xxx job guide, especially for creative work like software development! With a relaxed working environment and appropriate professional ethics, a team can be "self-maintained" and gradually improved-this is what I learned from foreign colleagues, the answer to the question "(no fee deduction) How to manage matters/administrators!

However, with this answer, I have to face another embarrassing fact: many Chinese are still really ~~ No professional ethics!

I once saw a group of people in a Q group discussing "what is better for foreign companies and domestic private companies ?" This is an eternal topic. Some people say that foreign companies are so comfortable that they don't need to punch in to and from work. How free is it! Then there was a bunch of supplementary voices, and the private companies in China were not conscientious about cloud. In the meantime, I intercept a word to the point that foreign companies are not a single specification, and there are strict requirements for punching and not punching. Don't forget that the logging machine was invented by foreigners! As a result, I was scolded by a group of people and ridiculed by people I don't know. "You are a big bull. Why don't you get me to work at HP ?"

In the eyes of these people, it is really just a job, a way to make a living, not a career!

In the eyes of this group of people, the only consideration is the level of treatment, whether the work is easy, rather than improving their own capabilities, broaden their horizons!

When a cook doesn't expect customers to boast their dishes well, is it still a cook?

In the face of such a group of practitioners who do not have the program or even do not have the normal logic ~~~~~~ The puzzling question still has no answer:"(This case/this person) How can I handle the charge ?"

 

00:11:29