Agile Software management process (Instance) favorites

Address: http://www.infoq.com/articles/agile-kanban-boards

I have refined the original article, reserved some core ideas, and removed the advertisement in Japan.

1. task board

Tasks are the actual tasks at hand.

Paste the tasks, tasks, and completed tasks on the whiteboard with simple tips. Different colors indicate different importance levels.

You can draw horizontal lanes to indicate who should complete the task.

 

2 requirement feature Board

The demand feature is a major functional requirement of the software, which is usually categorized by month.

3 agile development requires dividing software design into three parts: features-> Use Cases-> tasks

Feature: a meaningful function for end users
Use Case: a small plot decomposed by features that can be used for functional testing
Tasks: Use Cases are decomposed into the smallest unit of work that developers need to complete.

4. In the agile process, the time is divided into: release-> iteration-> daily

Release: usually one to six months
Iteration: usually one to four weeks
Daily:

5. We correspond the work and time.

In each release process, we fulfill the requirements.
In each iteration cycle, we implement the case
Every day, we have to complete multiple tasks.

6. Better image, we will combine them:

You need to prepare three blackboards:

Requirement features Blackboard: each column identifies the features to be completed for a release
Case Blackboard: each column identifies the cases that need to be tested during each iteration cycle
Task Blackboard: the task to be done every day