Agility in my heart (4)-diverse forms and constant nature

Author: sodimethyl
Source: http://blog.csdn.net/sodme
Disclaimer: This article may be reproduced or reproduced without the consent of the author. However, please keep the author, source and declaration information of the first three lines of the article for any reference to this article. Thank you.

Introduction:
In the previous articles, the true content of the word "agile" is constantly repeated. Yes, if you want to talk about these so-called content, no one will oppose it. However, let's extend this question further: How can we understand the relationship between various agile development forms and agile methodologies? How can we apply various agile theories summarized in books to our development practices? These questions may no longer be so easy to answer. In this article, I will explain my understanding of these questions and how to solve them.

Body:

As a matter of fact, when we take software as an "engineering" task, a lot of things begin to become more appealing. It is reasonable to say that software development is a very creative thing, and we should write programs in a daily atmosphere full of imagination and happiness. The opposite is true, we are always suffering from such a demand as no one, no ghosts, no ghosts, constantly changing the design scheme, constantly debugging the code, and even becoming a class of people that are not as good as typists: because the typist only needs to quickly strike, and we still need to keep cutting the wire in the existing solutions and new requirements, the so-called "skills" that make us and our later users suffer are used to achieve new demands and maintain the stability of the existing frameworks.

As demand becomes increasingly uncontrollable and software development becomes increasingly dependent on personal experience, we hope to have a piece of straw to free our suffering it technicians. As a result, the software life cycle, software engineering management, waterfall development model, agile development model, and so on are intertwined with practices and theories, we have invented a new method to continuously adapt to real business development needs. In this sense, the agile development model can be called a milestone in the software development field, because, it restores the development itself to what it should have. It acknowledges the complexity of the reality and pragmatically proposes many specific development methods with guiding significance.

In the Chinese IT translation field, I think agile translation is one of the few good words, the beginning and end of all development methods under this methodology have been precisely expressed, that is, the "agile" development method brings the "agile" product delivery speed, ultimately, it will bring about an "agile" company's development speed.

Whether it is XP, scrum, crystal, add, FDD, DSDM, or RUP, there may be a variety of forms, but its nature has never changed, that is: to make uncontrollable product R & D, it becomes controllable; it turns slow development like snail development into fast; it turns messy and disorderly development into orderly and pleasant.

Our own development framework uses scrum as the main body, but uses XP temporarily at a certain stage or between some colleagues as needed. For example, if we want to make a piece of key code known, known, and mastered by two or more colleagues, we can develop this piece of code, we will encourage you to use XP. After this task is completed, it is restored to an existing method.

When we adopted scrum, we did not mechanically copy its various job settings and staffing settings. Most importantly, we learned its "God": that is, we pay attention to full authorization. At the same time, we emphasize that we pay attention to the results and are only responsible for the results. In addition, the results should be clear, achievable, and traceable, the results are controllable. Developers will understand how important it is to "controllable results" for a project that frequently changes requirements and has demanding release cycle requirements. In this case, if "the results are uncontrollable", there is only one dead end to such a project, and the final outcome of such a team is to be disbanded.

To be honest, if a new team adopts our current practice from the very beginning, it may encounter a lot of obstacles, because in our development method, individual professionals have high requirements. "One-stop-one" is almost the basic requirement of team members. That is to say, no matter what you did, you should be placed in the new task environment under the existing framework, and you should be able to adapt immediately, quickly deliver results in the new environment.

However, not everyone and every team can achieve this. Many teams, especially start-up teams, need to face the problem of low professional quality of team members. If you try to improve the quality through education and tutoring, the effect is relatively slow. Therefore, the best way is to bring the correct methods and good professional habits of doing things to new people through words and deeds, finally, all of them will be trained one by one. Our ultimate goal is to allow everyone in the team to stand alone in one aspect. When we fight with any of them, we can give our back to Him with confidence.

Our own team came along step by step. At the beginning, we were also a group of inexperienced newborn calves, and we were better off than others, A good company background and resources can support us to fail, explore, and improve in such a long period of time. What is better than others is that in this process, we have never been able to retreat or escape, but have never been able to survive. Over the past four years, we have been constantly seeking for ways to keep improving, constantly improving our work every day, and even, our requirements for quality, security, and stability have reached the level of Bt that just arrived. Yes, as long as there are small details that affect security, stability, and quality, we will not make concessions, and we will not be able to pass through them. Let alone the code. This is our foundation and insurmountable.

"Efficiency, efficiency! Quality, quality !", Every time we look at our practice and the theory in books that seem to be "out of touch", these two words will constantly appear in our minds, this has also become the two most important reference coordinates for us to make a correct choice.

There are many people who have no passion for work and no efficiency because their projects have no pressure and their work has no sense of survival pressure. Doing well will not have a huge impact on their future, the amount of work done will not fluctuate the salary of the company this month. They always say that the project has no prospects, and the company has no prospects. They always think, mixed Time to cheat the so-called "accumulated experience of time", and then switch to another bigger company, find a job with a higher salary, so that reciprocating.

In fact, what I want to say is that no matter which company you want to switch to, the one you want to switch to is "bigger, better-looking", what you will eventually get from this company, it is always because of how much value you have contributed to the company, and I believe that the time you have wasted without too much valuable experience is equally worthless for these new companies.

If you want to make yourself more valuable in the future, you should start from now on and make your daily work more efficient, do not always think about how to do things outside of the company during the company's time, do not always think about reading more technical books irrelevant to the current project during work hours, what you need to do most, it is to do what your boss and your boss arrange for you every day! People always have to pay first and then get a return. Do not complain about the poor treatment or the lack of prospects. If you want to find a promising company, you must first grow into a promising guy.

Far away, I wanted to say agile. I even talked about my ideal and life, and sweated! Well, in fact, I want to say that what we are talking about now is not just a way to write code, but also a way to make software, it will be associated with many other effects, and these effects may be something you never thought about before. A journey of a thousand miles begins with a single step. If you want to make yourself more valuable, you can make your daily work more efficient, and truly belong to your "agility ", in fact, when you think about and analyze your own work flow and work environment, you can make a solution that truly fits your actual situation, it is by no means a wide variety of theories mentioned in books.