Software Development Management: Looking into the problem

When I first graduated, I was proud of myself. See everything has its own set of ideas, always feel that there is a place to dislike. Remember once to the customer there, the other it asked some software in the process design problems, I will manage the idea of the big talk back. Don't want their manager to hear, immediately pull me past: "Talk about management is it, come, we talk about management!" ” 。 Although working with the manager has been pleasant, this time he was politely repaired. Afterwards I understood clearly that the words were over the head, this is the biggest education for me.

Then with the increase of work experience, I really understand what is "existence is truth". Entrepreneurs strive to fight, create a thousands of people, or even tens of thousands of people of the factory, naturally has its success in the truth. We self-righteous young people always with some rationale explicit, or some of the rules, staring at some details, big talk about what BPR, 6 Sigma, is really naïve. The real thing to do is to recognize the business and then think about how to improve it. Even if the entrepreneur has a big mind, we should also know our role. Small to a small workshop, large to a large factory, have its endless problems, but also to make its existence bright spot.

In Xiamen, a company in the ERP project start-up meeting, a manager of a management department to correct the consultant's words: "Later, is the matter of our company!" "I was impressed by that remark. from an outsider's point of view, it is clear that the problem can be identified, but it is difficult to get a suitable solution. only by merging themselves into the company and into the team, can we understand the nature of the problem more clearly and have a good response plan. For example, some tools for quality management have been very popular, such as Fishbone diagrams, mind maps, and so on. These tools are not needed if you have a clear understanding of the people on the scene. A bunch of quality management engineers in the office for a half day, may not be as good as a production line engineer to understand the problem. This is the reason that Rice JAL advocated to go to the scene.

These are the first few years I graduated in the ERP software development work experience. The latter is more focused on software, but these experiences have been very useful.

So is the management of software development. The problem is that the market is changing too fast, the product cycle is short, the cycle of the product is shorter, and the management problem is not as prominent as it used to be, because too many more urgent things cover up. It's not a good idea to sell vacation trips to a bunch of people who are struggling to survive. But the problem is still there, but the degree of investment in these issues is limited. Where's the line? The answer can only be found when the team is integrated. Find your own position and push your work in the right way. Whether it is a subtle guide, or a drastic institutionalization drive, as long as the appropriate team on the line. On the contrary, it will bring disaster.

So what is the right way? The first is to locate the stage of the team, to clarify the urgency of management issues. The second is to do a good job of communication, to confirm their understanding and implementation of the way to be recognized.

In short, it is necessary to get out of the problem, but also to look at the problem!

Purely some feelings, no special preparation, inappropriate, Welcome to exchange!

"More C + + idioms" has been translated 17! For a detailed page, please see here:
Https://github.com/HorkyChen/MoreCPlusPlusIdioms

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Software Development Management: Looking into the problem