Udad User Story driven Agile development – a transcript of the presentation

Agile has been widely recognized in the software industry today, but most agile methods are specific methods or practices that have been summed up to address a particular problem, and there has been a lack of a system that can link the entire development process. User story-driven agile development (user Stories Driving agile Development–udad) is a methodology and practice that will provide the most effective approach in every process of software development so that teams wishing to adopt agile can have a holistic methodology as a guide.

If you have a lack of understanding of agile, you can read the following documents:

About Agile Development

udad has been used in several widely recognized methods and tools:

• user story map
• visual boot
• scrum
• kanban
• continuous integration
• Exploratory testing
• Automated deployment

In addition, the above approach also provides support for teams and methods, and in the current version Microsoft Team Foundation Server is used as the software lifecycle management platform.

Full version ppt download

A re-understanding of the software development process

Compared with the production process that has been standardized in traditional industrial production, the process of "manufacturing" of software that most people understand is actually equivalent to the "design" process of manufacturing prototype cars. This is why it is fundamentally wrong to manage the software development process that has been in the design phase using the method of managing standardized automotive assembly lines (waterfall mode).

To make the "creation" process of software development reliable (manageable), we have to solve the 3 dimensions of the content-practice-quality problem, which must be under the premise of unclear objectives and M.F.B. s delivery.

The process management methodology for Agile development is based on the use of change to adapt to change, allowing us to improve the likelihood of project success in the face of "complex" projects.

What is a user story

The user story is a requirement management approach that is presented as agile, which is both a description of the requirements and a base point to assist the team in understanding the requirements and managing the follow-up development process.

We must keep in mind that user stories are not written, but are used for discussion, memory and tracking. The human brain is never good at remembering a lot of complicated information, but we can still remember a lot of scenes. Using a visual approach to discuss requirements and helping team members build a unified understanding of their needs through a structured approach is at the heart of the user story.

In addition to assisting us in the design and planning of our needs, we also use user stories as a clue to follow the whole process in the development process, to organize all the follow-up processes, the way the team members are written, the tools used, and the feedback from the end user.

3– Design and planning process

In the design process, we mainly solve the process of how to generate demand, this part of the content can refer to the following articles:

User story-driven agile development –1. Planning Chapter

There are 2 main tools used here:

Impact Map: Please refer to the following articles

• Power of Seeing – (II) Impact map
• Impact Mapping Influence Map reading and exercise experience

User Story Map: Please refer to the following articles

• The first experience of user story Mapping
• 8 Steps to create a user story Mapping

4– Planning Process

In the process of project operation, Agile's mature scrum and kanban approach is the best choice for the team, and as a result of the good foundation of the previous planning process, the subsequent running of scrum and Kanban has a good starting point. Solves the problem of how the team who first approached these process methods did not know how to get started.

A detailed description of this process can be found in the following:

User story-driven agile development –2. Create a backlog

For scrum and Kanban methods please refer to:

• Analyzing the five core practices of lean product development – Kanban approach
• Scrum Master face questions – 22 Scrum basics you must know
• This mistake, every ScrumMaster has committed

5– Iterative development process

In the development process, the interaction of various roles will become more and more complex, we need to have a visual method to let different roles clearly know what they are doing with other people's relationship, here Kanban is the best way. The above lists some of the key features of the electronic Kanban in TFS, but there is always an advantage between the electronic tool and the physical tool, and it is recommended that the team use it as appropriate.

Coding flow in the development process is a critical process that affects developer efficiency, and the above lists a coding flow that uses feature branch combined with pull request and CI.

Refer to the following document for this process:

Continuous delivery – Continuous integration, automated release and automated testing

6– continuous delivery and feedback process

With a continuous integration as a foundation, we can continue to build the release pipeline. The ability to deploy applications quickly and stably is an important competency indicator for a team's devops practice and an important means of significantly shortening mttr. At the same time, with the help of exploratory testing tools, we can bring the user/business people and the development team together to form a quick feedback mechanism.

Refer to the following documentation for this process:

Quickly fix production problems

Summarize

At this point, Udad completed a closed loop of software development.

Please follow the public number "Devopshub" For more information on DevOps integration

?

Udad User Story driven Agile development – a transcript of the presentation