{Agile}, {cmme}, current situation

I have been busy recently and haven't come up for a long time. I am working in Shenzhen, and the company is also a relatively large company in Shenzhen. The company has more than 200 developers and is in the United States. NET has been around for nearly three years. It is said that programmers have been around for three years and five years, that is, they have a monthly salary of 6 K and 8 K. I heard that it would be nice to go over. I have only crossed the first hurdle, and the second one is still working hard... When I was leaving, the Project Manager of the previous company asked me to do basic development for another two years. It would be easy in the future. This is what I do now.

I had nothing to do at home and looked at agile software development. Now, in the Software industry, we often hear the Software Development process: Agile Software Development and cmme (Integrated Software Capability Maturity Model, what are the differences between the software development process, agile software development, and cmme in the company? I will not explain it in detail here, but I will talk about Agile, cmme, and the status quo. If you have any mistakes, you are welcome to make a picture.

Agile Declaration

1Human and interaction over processes and tools

2. software that can work is more important than comprehensive documents

3. Customer cooperation over contract negotiation

4. Respond to changes at any time over compliance

 

Agile:  Human and interaction over processes and tools.

Cmme: Human communication is very important, but CMMS seems to be more biased towards processes and tools.

Status quo: The company pays more attention to communication between employees. As for the process, I can say that CMMI2 may not have the level and management is chaotic. The tool is still used.

 

Agile:  Software that can work is more important than comprehensive documents.

Cmme: Cmme focuses more on documents. It takes a lot of time to write documents, but the project development is more standardized.

Status quo:This company is still very agile. I don't know whether managers follow the agile development process or the pressure from superiors. There are very few documents.

 

Agile:  Customer cooperation is more important than contract negotiation.

Cmme: I believe that cmme should be very similar to agile at this point.

Status quo:This is basically the same for the company. win the contract first and then communicate with the company.

Agile:  Changes are more important than regular changes at any time. 

Cmme: Cmme should pay more attention to its processes, which may lead to a relatively regular situation and lack the ability to adapt to the situation. Status quo:Basically, no one in the company follows the same rule. The demand changes a day and a week, which is totally forced out.

 

Agile Software Development12Principles

1. Our top priority is to deliver valuable software as soon as possible to satisfy our customers.

In the world of agile development, there is a saying: the fewer features contained in the system of initial delivery, the higher the quality of the final delivery system. The more common the delivery, the higher the quality of the final product. We often deliver a system with basic functions in the first few weeks of the project, and then we strive to deliver a function increasing system every two weeks, if the customer thinks that the current function is sufficient, the customer can choose to add these systems to the product, or they can simply choose to check the existing functions and point out the changes they want. In my opinion, cmme should be well designed in the early stage. It completes most of the modules and is delivered to the customer after a good test. Then it is released once. This interval will lengthen over time. The current situation of the company is that the demand is often changed, resulting in frequent release once a month.

2. Even after development, you are welcome to change your requirements.

Cmme: cmme has its own set of processes. The requirements are generally completed almost during the project preparation period, even if the changes are not very large in the future.

Status quo: I agree with the cmme, but the company's model is a bit like agile development. I often modify some requirements a few days before the release, which is exhausting and time-consuming, there is no preparation.

3. You can regularly deliver software that can work. The delivery interval can be from several weeks to several months. The shorter the delivery interval, the better.

Cmme: frequent releases will inevitably lead to chaotic processes. It should not be required by cmme.

Status quo: I agree with cmme. After all, it is not easy to release a version. For example, it is very troublesome for my company to release a project because it is global, so it is often released and tested at the company in the middle of the night. Employees complained after a long time.

4. During the entire project development period, business personnel and developers must work together every day.

Cmme: Same as agility

Status quo: The Company agrees with this point.

5. Provide the necessary environment and support for the motivated personal component projects and trust them to complete their work.

Cmme: As the saying goes, everything is ready. The preparations for cmme are still very adequate.

Status quo: The company is vague, and sometimes it is not considered. I personally prefer good environments and support.

6. Within the team, the most effective way of transmitting information is face-to-face communication.

Cmme: This is also required.

Status quo: communication is a big factor that determines whether a team can successfully complete the project. I guess no company will emphasize this.

7. Working software is the primary progress measurement standard.

Cmme: This is also required. Status quo: In the end, the company aims to realize commercial value, economic benefits, and product success, which is a measure of success.

8. The agile process advocates sustainable development speed.

9 constantly paying attention to excellent skills and good design will enhance agility.

10 simple.

These three points do not need much. They should all be the same idea.

11 The best architecture, requirements, and design come from a self-organizing group.

Cmme: the standard software development process should all have such requirements.

Status quo: there may be several people involved in the content due to personal interests or the distrust of superiors. My company is also.

12 every once in a while, the team will reflect on how they can work more effectively and effectively, and then adjust their behaviors accordingly.

Cmme: similar.

Status quo: timely summary and reflection can identify the location and cause of the problem earlier, and avoid repeated mistakes next time. This is required during the project. Unfortunately, the company lacks such information.

In short: I personally feel that agile software development should pay more attention to people, timeliness, speed, and passion. Cmme: fully prepared, more streamlined, and rigorous. They have their own advantages and disadvantages. What mode is used depends on your superiors. Pai_^