Ready Board Column Access conditions
- Demand completed Delivery
- All issues in the demand delivery process have been resolved
- The bug produced by the current iteration requirement must be placed in the column
- Bugs left over from previous iterations
Job description
- Overview of requirements Implementation Design
- Bug Confirmation
- Task splitting
- Task workload estimation (per hour)
- Scenario scale estimation (in the story point: Fibonacci sequence)
Development Board column in progress-access conditions
- Ready column working content completed
In progress-work content
- Coding implementation of requirements and bugs
- Interlock Test (dev self)
- Configuration files and script updates
Completion-access conditions
- "In progress" column work completed
- The code has been pushed to the test branch
- Configuration files and scripts submitted
- Published test environment
Test Board column in progress-access conditions
- Requirements are in the "Development Complete column"
- Requirement corresponding test case completed and passed use case review
In progress-work content
- Use case execution
- Bug Acceptance (the bug that is generated by the current iteration requirement is closed directly)
Completion-access conditions
- Demand-related use cases are running
- Demand-related bugs have been fixed
Conditions for acceptance of board listing
- The requirement is already in the Test complete column
Job description
- Product owner in test environment acceptance
- The product owner makes a demand presentation to the relevant stakeholder (optional).
List of board access conditions to be published
- Requirements or bugs have been accepted by
Job description
- Develop and organize release checklist
- Checklist of test and collation acceptance results
- Product Finishing Function List
- Test Environment Sealing Plate regression
Quasi-conditions
- Requirements and bugs have been released formally
- On-line regression test passed
- Master Branch has been pushed
TFS Kanban Rules
