ad

Development Team Efficiency

I have written an article called " Overtime and Efficiency ", conceptually speaking about some of my understanding of "efficiency", but that article tends to be conceptualized. For some students who have not experienced such an environment, It may feel too abstract. I have long wanted to write a more specific, executable article that echoes the article " Overtime and Efficiency " and puts me in the " advocating engineer culture" of QCon two years ago in Hangzhou. The view of a powerful small team (Techno's Club) will be strengthened.

But I have encountered some troubles in my way of thinking - I always talk about the background of my experience, not from the background of other people's experience . It's like, I said a lot in the cool shell (for example: full-time QA , Code Review is very important , programming age , entrepreneurial , Rework ...), there are many people who think it is impossible or even ideal, actually I Those things that are said are really there, and I have experienced them. As a result, different experiences, different environments, and different visions have caused – some people don’t understand what I said, and I can’t understand what they say.

So, during the past time, I had the opportunity to find some people to communicate and observe some things around me, and try to follow and understand what I can't understand. I feel almost the same now, so I wrote this article. (But the more I understand each other, the more I insist on my point of view, so this article may still appear in chickens and ducks, it doesn't matter)

This article does not discuss any business efficiency issues, only the efficiency issues in software development or software engineering. Although the efficiency problems in products and business are fundamental, but because this article is not hateful, I don't want to talk about it together, so please forgive me for talking about the development team here, and later reopening an article devoted to products and business.

I will list a few typical development methods below - "lock" in software development , baton software development , nanny software development , WatchDog software development , and fault-driven software development .