Scrum Gathering 2012 Shanghai_敏捷测试与质量管理分会场演讲话题:getting to done by testing at the same time as coding(李平  王珂)
Upcoming SlideShare
Loading in...5
×
 

Scrum Gathering 2012 Shanghai_敏捷测试与质量管理分会场演讲话题:getting to done by testing at the same time as coding(李平 王珂)

on

  • 672 views

李平(Jessica), 王珂(James), CSM, PMP, 资深测试/开发专家。 ...

李平(Jessica), 王珂(James), CSM, PMP, 资深测试/开发专家。

计算机硕士, 现任SunGard产品开发经理, 并担任团队的Scrum Master,曾从事信息安全,化工,金融领域软件开发,具有丰富的敏捷导入经验,带领团队成功完成了敏捷转型,是敏捷思想和实践的积极推广者。

话题介绍:
对一个新团队来说,听到“It’s done, BUT there’s still some testing to complete”已不足为奇。为了确保在一个sprint中真正完成所有用户故事,开发和测试必须 ”并行” 进行,打破常规。一起来关注SunGard团队是如何实现神奇转变的吧。

Statistics

Views

Total Views
672
Views on SlideShare
604
Embed Views
68

Actions

Likes
0
Downloads
27
Comments
0

1 Embed 68

http://scrumgathering.cn 68

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Scrum Gathering 2012 Shanghai_敏捷测试与质量管理分会场演讲话题:getting to done by testing at the same time as coding(李平  王珂) Scrum Gathering 2012 Shanghai_敏捷测试与质量管理分会场演讲话题:getting to done by testing at the same time as coding(李平 王珂) Presentation Transcript

  • Getting to done by testing at the same time as coding 李平 王珂
  • GAIN GLOBAL VISIBILITY OF FOSTER CASH & RISK CONNECTIVITY UNLOCK HIDDEN CASHDRIVEEFFICIENCIES &PRODUCTIVITY AVANTGARD GETTING TO DONE BY TESTING AT THE SAME TIME AS CODING 李平(Jessica);王珂(James) Manager of Product Development (Scrum Master) SunGard
  • BACKGROUNDTeam & Projects SunGard Treasury Product Team
  • CHALLENGESNot delivering on schedule  Testing not finished  Testers 1 or 2 sprints behind devs  Low automation coverage  Regression not being run regularly
  • DEFINITION OF DONEWhat’s DONE? Done means released.
  • DEFINITION OF DONEFinish complete story What do you think from different perspective?
  • CHANGES THE WAY PEOPLE WORKChanging from working as individuals to working as a team Developers Testers Team
  • WORK AS A TEAMProper story size Work with PO to break down stories into proper size.
  • TEST AUTOMATIONWriting tests before a screen exists• Automate as much as possible.• Test tool to choose• What to do beforehand
  • TEST AUTOMATIONSCREEN DESIGN
  • TEST AUTOMATION-EXAMPLEExample: Object ID
  • AUTOMATION TESTINGAutomate all the stories One Example, pervious our testing is like this …
  • AUTOMATION TESTINGAutomation script strategy One Example, currently our testing is like this …
  • UT/ITFind issue ASAP What to test? How it should work? When to finish?
  • UNIT TESTING PROCESS/ EXAMPLEOnce failed, take action immediately Example:
  • RESULTDeliver functionality on a regular schedule Percentage Stories Done 120% 100% 80% Example: 60% 40% 20% 0% Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
  • RESULT-DONE ORDERImproved done order based on story prority Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Example:
  • CONTINUOUS INTEGRATIONContinuous Delivery Process Every code change leads to a potential release. It’s a continual process.
  • CONTINUOUS INTEGRATIONUse of VMs for testing environments • Team daily build/testing • Regression Testing • IT/UT
  • WORKING AS A TEAMProcess to ensure all work fine • Don’t comment out failing tests! • You broke it you fix it!
  • CONTINUOUS IMPROVEMENTMore practices Continuous Improvement.