Agile Testing (6) based on story Agile Basics

Agile basic knowledge----demand management based on story (III.)

(3) Daily station meeting

The purpose of the station will be three:

(1) Known progress

Progress is known only from the level of user stories and tasks, and there are only two states of task progress: complete or incomplete (percent complete).

(2) A well-known scheme

What work will you do before the next meeting?

(3) Throwing problems

What's blocking your progress? ("No problem" means that you are able to deliver your current tasks and meet the estimated timeframe) if you encounter problems that need to be addressed, you can handle them after the daily meeting.

Necessary prerequisites for achieving a project:

1. Station

2. Agile projects must provide a "security failure" environment in which team members are not penalized for failing to achieve a mission commitment.

You need to be able to safely tell the truth about the status of the task and understand the reality of the project environment. Sometimes our estimates may be bad (just an estimate , it's not a promise, or something that makes some members unable to do the task, the overall environment must allow them to tell the truth, so that team members can adjust their schedules, sort tasks, and adjust the reality of the project.

The main contents of the station will be:

from PM, RD to QA, everyone speaks for:1. What did yesterday, 2. What's the problem, 3. What are you going to do today ? If you want to share the knowledge, you can also share here.

Finally, the moderator summed up, and then according to the actual problems encountered, a small number of offline communication, follow-up, resolution.

The time of the station will be controlled in about 10 minutes as far as possible.

Some tips for opening a station

(a) rotation of the Chair

The rotation of the host can increase the participation of the team members, and if the host temporary things, will not be able to carry out, usually at the end of each station will designate the next station host.

(b) Resolution of issues not in meetings

The meeting only throws the question, solves the problem to place after the station will end, the related person participates. The aim is to avoid wasting everyone's time.

(c) held in the morning

We can get everyone on time and work on time.

It will make everyone more aware of what they are doing today.

Everyone has a different schedule in the evening, a different schedule, and the morning said what was done yesterday is more accurate.

(4) Card wall

With the overall plan for the iteration, it also needs to be refined to manage each story, except for the previous estimate, we use the card wall to manage it.

The card wall is shown in the following illustration:

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/project/

Demand Pool : All new story (typically not evaluated) cards are posted here.

Pending Development : The story cards to be developed are posted here.

demand Pool-> to be developed: explain the completion of communication needs, assessment points, after the completion of the acceptance criteria, mobile

in development : All story cards being developed are posted here

Pending Development-> development: RD will split the task story, and give QA the task implementation ideas, QA agreed to move after.

To be tested: All development completed, story cards waiting for QA test are posted here.

-> to be tested in development: Rd Development completes the story, and completes the single measurement, the integration test compiles, and after the careful self-test, moves.

Test : All QA Testing story cards are posted here.

QA Singnoff: All QA-tested, QA-story cards are posted here.

->qa singn off in test: QA After careful testing, bugs are repaired to verify that story meets the online standards when moving.

verified : All the story cards can be posted on the line after PM acceptance.

QA singn off-> verified: PM in the acceptance of the acceptance of the environment, the need to meet the requirements, move.

Acceleration Zone : All story cards that need to be expedited for resolution are posted here. If the card has a block test bug is urgently needed to repair, and so on.

block Area : All story cards with some problem blocks are placed here.

card : Story card, Task card (story number, estimate points, user story).

role Card :FE, RD, QA name, with different color distinction, write names, respectively, used to paste on the story. Who is doing what, who is busy who idle, how much residual manpower, at a glance.

online time : slightly.

(5) Burning diagram

Use burning charts, plans and changes, as well as a daily schedule at a glance.

The combustion diagram is as follows :

1, the x axis is the time, generally is the iteration cycle each day;

2, Y axis for the workload, according to the project situation, you can use the completed estimate points or completed story points to indicate;

3, at the beginning, to calculate all the work to be done by this iteration (as the y-axis scale, the number of iterations as the x-axis scale), and then, every day standing meeting, understand the work done the night before, and calculate the total amount of work done to date. Draw it on the Y axis, and so on (and connect the y point to the line). If the plan compares (ideally) accurately, the burning line of the last day of the burn chart intersects the total work line;

(6) Summary

The above five, simple and easy to achieve, with very low time cost can make "plan", and ensure the implementation of the plan, and can quickly adapt to change!