scrum gathering 2012 shanghai_敏捷测试与质量管理分会场演讲话题:getting to done by...
DESCRIPTION
李平(Jessica), 王珂(James), CSM, PMP, 资深测试/开发专家。 计算机硕士, 现任SunGard产品开发经理, 并担任团队的Scrum Master,曾从事信息安全,化工,金融领域软件开发,具有丰富的敏捷导入经验,带领团队成功完成了敏捷转型,是敏捷思想和实践的积极推广者。 话题介绍: 对一个新团队来说,听到“It’s done, BUT there’s still some testing to complete”已不足为奇。为了确保在一个sprint中真正完成所有用户故事,开发和测试必须 ”并行” 进行,打破常规。一起来关注SunGard团队是如何实现神奇转变的吧。TRANSCRIPT
Getting to done by testing at the same time as coding
李平 王珂
AVANTGARD
DRIVE
EFFICIENCIES &
PRODUCTIVITY
UNLOCK
HIDDEN CASH
GAIN GLOBAL
VISIBILITY OF
CASH & RISK
FOSTER
CONNECTIVITY
GETTING TO DONE BY TESTING AT THE
SAME TIME AS CODING
李平(Jessica);王珂(James)
Manager of Product Development (Scrum Master)
SunGard
BACKGROUND
Team & Projects
SunGard
Treasury Product
Team
CHALLENGES
Not delivering on schedule
Testing not finished
Testers 1 or 2 sprints behind devs
Low automation coverage
Regression not being run regularly
DEFINITION OF DONE
What’s DONE?
Done means released.
DEFINITION OF DONE
Finish complete story
What do you think
from different
perspective?
CHANGES THE WAY PEOPLE WORK
Changing from working as individuals to working as a team
Developers
Testers
Team
WORK AS A TEAM
Proper story size
Work with PO to break
down stories into
proper size.
TEST AUTOMATION
Writing tests before a screen exists
• Automate as much as possible.
• Test tool to choose
• What to do beforehand
TEST AUTOMATION
SCREEN DESIGN
TEST AUTOMATION-EXAMPLE
Example: Object ID
AUTOMATION TESTING
Automate all the stories
One Example, pervious our testing
is like this …
AUTOMATION TESTING
Automation script strategy
One Example, currently our testing
is like this …
UT/IT
Find issue ASAP
What to test?
How it should work?
When to finish?
UNIT TESTING PROCESS/ EXAMPLE
Once failed, take action immediately
Example:
RESULT
Deliver functionality on a regular schedule
Example:
0%
20%
40%
60%
80%
100%
120%
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
Percentage Stories Done
RESULT-DONE ORDER
Improved done order based on story prority
Example:
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
CONTINUOUS INTEGRATION
Continuous Delivery Process
Every code change leads to
a potential release.
It’s a continual process.
CONTINUOUS INTEGRATION
Use of VMs for testing environments
• Team daily build/testing
• Regression Testing
• IT/UT
WORKING AS A TEAM
Process to ensure all work fine
• Don’t comment out
failing tests!
• You broke it you fix it!
CONTINUOUS IMPROVEMENT
More practices
Continuous Improvement.