2. PREVIOUS WORKFLOW
Draft Feature Develop
Code
Review Deploy
P
E
Q
Implementation
Planning
E
P
E
Test
E
P
Assume 10 blocks for each team
Use case
Review
3. PREVIOUS WORKFLOW
Draft Feature Develop
Code
Review Deploy
P
E
Q
Implementation
Planning
E
P
E
Test
E
P
Assume 10 blocks for each team
Use case
Review
4. PREVIOUS WORKFLOW
Draft Feature Develop
Code
Review Deploy
P
E
Q
Implementation
Planning
E
P
E
Test
E
P
Assume 10 blocks for each team
Use case
Review
Every miss of target will significantly increase workload
6. WHAT MAKE A “MISS"
• All use cases
• Implementation Plans and Code Review
• All test cases
Engineers misunderstand requirements
“New” use cases after implementation
Engineers come up “new” ways to do tasks
Inevitable code refactoring
BUGS !
7. WHAT WE WANT
Accurate and Direct
Ideal case NEVER exists in real life
Human errors are everywhere
ACCEPT IT
8. INACCURATE and SHORT Review cycle
ACCURATE and SHORT Review cycle
INACCURATE and LONG Review cycle
15. NEW WORKFLOW
MORE SCRUM
Draft
Feature Develop
Code
Review Deploy
P
E
Q
Implementation
Planning
E
P
E
Test
E
P
Use case
Review
Feature
Planning
E
P
Q
Daily Sync-up
16. FEATURE PLANNING
DEFINE ACCEPTANCE CRITERIA
P
E
Q
We want to
let the users set some
variations of a
product
How can we test
a variation is set ? Will
it affect the listing of
products?
We may need to
update our data structure
for this. It takes days
Acceptance
criteria
19. WHENTHETEST CASE IS
BORN
Draft
Feature Develop
Code
Review Deploy
Implementation
Planning Test
Use case
Review
Feature
Planning
Draft Feature Develop
Code
Review Deploy
Implementation
Planning Test
Use case
Review
Original
New
20. Draft Feature Develop
Code
Review Deploy
Implementation
Planning Test
Use case
Review
Original
1. Everyone has his own way to interpret “done”
2. All test cases are drafted just before testing
3. The test cases list is used in too few phases
WHENTHETEST CASE IS
BORN
21. Draft
Feature Develop
Code
Review Deploy
Implementation
Planning Test
Use case
Review
Feature
Planning
New
1. Cases are defined at Day 1
2. All parties can contribute to test cases.
3. Developers can review their works on their own
4. Have a standard way to mark down all the failure scenarios, the
development process can “learn” from failure
WHENTHETEST CASE IS
BORN
22. WHY “LEARN”
Avoid the same errors happen again.
At the same time, increase the test coverage
27. NEW WORKFLOW
MORE SCRUM
Draft
Feature Develop
Code
Review Deploy
P
E
Q
Implementation
Planning
E
P
E
Test
E
P
Use case
Review
Feature
Planning
E
P
Q
Daily Sync-up
28. DAILY SYNC-UP
FAIL FAST
P
E
Q
Demo
The error
message seems not that
good. I would like it to
be….
There is no such a
criteria here. Let’s update it
When the user
login successfully…When
the user login fail…OK, I will
update it.
Learn
Make reviews more accurate
31. QA IS ALWAYSTHE
BOTTLENECK
Inevitably Slow
test steps
=
Growingly High
test coverage
x
Time spent
/
Q Q Q
Q Q Q
Expensive ResourcesWe want it to
be much higher
Tell me. How can it be small ?