Agile Testing (3) based on story Agile Basics

Story based Agile basic knowledge----story writing

Why use story?

Software industry for more than 40 years, demand analysis technology has been very mature, but the MRD-driven process is overwhelmed. Since MRD often takes up a lot of time, MRD reviews take up a lot of time, and after coding is done, the pressure is poured into QA, often on the schedule, or the experience is poor, or there are too many bugs, or the project is postponed.

Using story, Project completion time will be greatly shortened, the time to market is greatly shortened. Main reasons:

A Adopting story mode, the large demand can be disassembled as a small story with independent delivery, the demand is clear, and the demand review time is saved.

B Story is small enough, the design is less difficult, and before the written detailed design and review for "oral communication, documentation as a supplement," The time is also substantial savings.

C The story is small enough, the acceptance standard is more clear, the test design link simplifies, the appraisal link changes to the oral communication, saves the massive design time.

D Story in parallel, not before all the requirements review completed before beginning to set up, detailed set no problem before starting coding and testing, so the demand phase of the bottleneck of the PM, Development Phase Rd bottleneck, testing phase QA bottlenecks are broken.

E. Free Rd from Documents and reviews, and Rd has more time and more willingness to test and write, and fewer bugs.

What is story?

Entire project:

Story

Story includes three parts: User story card, detailed description, acceptance criteria.

(1) User Story card

Three elements: users, tasks and activities, goals

Framework:

As	Xxx
I want to	Xxxxx
To	Xxxx