The Beijing-Mai Agile team decrypts a

The Beijing-Mai team has been transforming agile from 2014 under the guidance of an agile instructor, and the team has evolved into a benchmark within the department, and the product has risen to the strategic level of the department.

Beijing-Mai team Agile Video -( in the video below, you will see how our team is doing agile practice!) )

Objective

In the early days of the team, the team is far from the team so many people, only 4 research and development to do a "chicken" product. Why is said to be chicken, not no one use, but a lot of competition , to the user generated value does not highlight.

The original development rhythm is one, two months to release a version, you need to know this rhythm, in the present feeding frenzy, but also fast fish eat slow fish era, is already fatal. At the same time, competition is very strong, how to survive in the fierce competition?

The life-saving straw of the death march

The market is unknown and the team is a small team. How we spend the least cost to verify that our assumptions are correct, how we do the products directly to the user pain point! We do not have sufficient time, money and manpower to develop a chatty product and then put it on the market for verification! If the product positioning fails (no one uses your product), the team and the product will face the destruction!

So, we get acquainted with agility! We have made changes that have opened the way to agile transformation. In the face of change, the future is unknown, so we define this path of agile transformation as the death March, and agility is the last straw.

The transition to agility today is very successful, whether it's a product or a team. And what has been the change that agile has brought to us along the way? Why have we succeeded? During this time, we conducted too many internal agile training and agile engineering practices.

In simple terms, agile changes:

1. Small-run: Minor release, shortened from December to 1, 2 weeks, which involves the product requirements of the fine-grained split, quickly seize the market, with the lowest cost in the market for the product hypothesis validation. This is in the race with the competition, the effect is significant , the distance is bigger!

2. Team passion: For efficient communication, face-to-face discussion, code Review to ensure the quality of the codes. And at work, through kanban to achieve transparency, self-claim, timely feedback, the most important thing is to let the leader from the attention of idle people to focus on the idle task , which makes the team passionate and creative.

3. Extreme feedback and Deployment pipeline: the introduction of a large number of effective agile practices, including continuous integration, automated deployment, static code analysis, monitoring alarms and so on, these have greatly freed up the team resources, reducing the ineffective tools. We are a single branch of development, the team any one person to submit a line of code, will be compiled to build, automated testing, static code analysis, finally automated deployment, problems, accurate positioning of rapid feedback.

There are too many story content to share with you! Please also pay attention to the continuous update, there will be more explosive material, I hope that the team is doing agile transformation, or the start-up in the product testing in the water team to help.

—————————— This article is published synchronously in ZHANGSR My personal blog ——————————

The Beijing-Mai Agile team decrypts a