Shulou(Shulou.com)06/02 Report--

Introduction: now whenever I bring a R & D team directly or indirectly, I will give you a training in agile ideas and practices (Note: software direction, complex hardware development process is recommended to use IPD ideas). As a senior programmer with nearly 10 years of experience in development and coding, as a manager and a fairly successful entrepreneur, I have always had a first intention.

I hope that all R & D personnel can dare and will express themselves, so that more people can know themselves.

I hope that all R & D personnel not only write code mechanically, but also have insight into the market and users, so that their output can adapt to the needs of users and the market. This is not a sense of achievement.

It is hoped that all R & D personnel will no longer be trapped in the narrow direction of the workplace, but more likely to transform products, markets and management.

I think the practice of agile development has brought me these: the benefits of work, inner release, transformation opportunities and the most important self-confidence, so I would like to share these with you.

Agile development thought

Everyone can literally understand that Agile stands for "fast"

Boss Dilbert's understanding: there is no plan or documentation, just start writing code.

The understanding of many people in the industry: iterative development.

The above understanding can not be regarded as wrong, but it is the blind people's understanding of the image. Let's first take a look at several common development modes:

Plan-driven waterfall development

Gradual improvement of iterative development

Risk-driven spiral development

Value-driven agile development

In addition to the waterfall development often used in outsourced projects, it seems to many people that the remaining three development methods should be agile development. in fact, there is a word game, the attribute of "*". Agile development is driven by user values (users' needs), which is the standard of distinguishment. this emphasis on the core reminds us of what we need to pay most attention to. As for the significance of user value, it goes without saying-what's the point if what we make is not what the user needs? In fact, in the process of agile development, there are not only spiral development thinking, but also iterative development process, and even the stage of planned development.

Agile Manifesto-values

The reason why many "conservative forces" oppose agile development is that Agile does not pay attention to planning, documentation, and so on. The word game here is the word "better than", not without, but the difference between the choice and focus. The summary is as follows:

"the self-organizing team works closely with customers to respond to changes through a highly iterative, incremental software development process, and deliver valuable software that has been coded and tested at the end of each iteration."

conquer over

"after determining the contract with the customer, develop and follow a complete activity-based plan at the initial stage, transfer knowledge through the completion of a large number of documents and finally deliver the requirements under the guidance of heavy processes and tools."

12 Agile principles of Agile Development

1. Our top priority is to satisfy our customers through early and continuous delivery of valuable software.

Note: customer expectation management

2. Even in the later stages of development, you are welcome to change the requirements. Agile processes use change to create a competitive advantage for customers.

Note: you are welcome to change the requirements, but it does not mean that you can change them at any time. Make sure that the requirements do not change within a planning node.

3. Deliver working software regularly at intervals ranging from a few weeks to several months. The shorter the delivery interval, the better.

Note: for example, in scrum, the node cycle is often set to 2 to 4 weeks.

4. Business people and developers must work together every day throughout the development of the project.

Note: the R & D staff's understanding of the business can make the product more usable and even have an excellent user experience, the business staff's understanding of the technology will also make it more professional, and it can also deepen the understanding of different teams.

5. Build the project around motivated individuals. Provide them with the environment and support they need, and trust them to get the job done.

Note: for example, brainstorming people for needs and implementation, encourage everyone to speak, such as taking the initiative to get tasks instead of passive distribution, advocating democracy and openness

6. Within the team, the most effective and efficient way to convey information is to talk face to face.

Note: face-to-face conversation is not only efficient, but also conducive to a clear and thorough understanding of each other's intentions and the resolution of conflicts.

7. Working software is the primary measure of progress.

Note: each node should ensure that the software is available, not 99% complete but unavailable

8. Agile processes improve sustainable development speed. Responsible people, developers and users should be able to maintain a long-term and constant development speed.

Note: scrum nodes are like heartbeats that make our planning regular.

9. Paying constant attention to good skills and good design will enhance your agility.

Note: advocate that everyone should have autonomous learning ability and establish a learning organization.

10. Simplicity-the art of maximizing unfinished work-is fundamental.

Note: book Avenue to Jane (Douban), the core idea of UNIX programming art (Douban)

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

Note: decentralization, biological evolution in "out of Control"

12. At regular intervals, the team reflects on how to work more effectively, and then adjusts its behavior accordingly.

Note: "practice-reflection-correction-growth." The positive cycle of

Based on the above principles and keywords, extract several core agile development: "value", "customer", "people", "team".

Scrum of Agile practice

We need to understand a difference, agile development is an idea, let's talk about one of the development processes that carry this idea, Scrum.

The popularity of Scrum can be seen from this statistical chart used by the development process. Scrum itself is not a methodology, it is just a framework, it only defines a high-level management process, as shown in the following figure

It does not involve specific development methods or effective communication skills of personnel. These uncovered areas need to be complemented by other theories and skills to ensure the success of the project.

You can see that the implementation process of Scrum is based on the 12 principles of agile development ideas. In turn, the implementation of the process can also deepen people's understanding of agile principles.

The values of Scrum

Core values: commitment, focus, openness, respect and courage

Principles advocated: self-management, emergence mechanisms, visibility and evaluation / adaptation cycles

Refining the main points of Scrum

Backlog-- clarifies business value and sets up user stories

Task estimation-fine, controllable and accurate

Meetings-focused, efficient, open

Goal-clear and achievable

Book recommendations for Agile Development

Scrum and XP in gunpowder smoke

"45 habits of efficient programmers"

Tool recommendation for Agile Development

Jira & & confluence Project Management, wiki knowledge Base

Redmine requirements, prototypes, collaboration

Jenkins continuous integration

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.