Slow Down to Go Fast: Lessons Learned Shipping Bing Voice Search on - - PowerPoint PPT Presentation

▶

Sep 01, 2022 384 likes •807 views

Slow Down to Go Fast: Lessons Learned Shipping Bing Voice Search on Xbox James Waletzky Director of Development & QA Practices, Crosslake (formerly Dev Lead @ Microsoft) jamesw@crosslaketech.com Randy Santossio Senior SDET, Microsoft

SLIDE 1

Microsoft

Agile 2012 1

Microsoft

Agile 2012 1

Slow Down to Go Fast: Lessons Learned Shipping Bing Voice Search on Xbox

James Waletzky Director of Development & QA Practices, Crosslake

(formerly Dev Lead @ Microsoft) jamesw@crosslaketech.com

Randy Santossio Senior SDET, Microsoft (Xbox) ransan@microsoft.com

SLIDE 2

Microsoft

Agile 2012 2

Microsoft

Agile 2012 2 J J

Who is this James guy?

http://blogs.msdn.com/b/progressive_development/

SLIDE 3

Microsoft

Agile 2012 3

Microsoft

Agile 2012 3 J J

The little engine that could

SLIDE 4

Microsoft

Agile 2012 4

Microsoft

Agile 2012 4 R R

Who is this Randy guy?

SLIDE 5

Microsoft

Agile 2012 5

Microsoft

Agile 2012 5 R R

From that little Redmond startup…

SLIDE 6

Microsoft

Agile 2012 6

Microsoft

Agile 2012 6 J J

How is your short term memory?

Dory says…

“Please jot down your questions and save them for the end.”

SLIDE 7

Microsoft

Agile 2012 7

Microsoft

Agile 2012 7 J J

How to win the race

SLIDE 8

Microsoft

Agile 2012 8

Microsoft

Agile 2012 8 R R

Agile vs. agile

SLIDE 9

Microsoft

Agile 2012 9

Microsoft

Agile 2012 9 J J

Just Bing it!

SLIDE 10

Microsoft

Agile 2012 10

Microsoft

Agile 2012 10 R R

The internal workings

Controller Input Voice Input (Kinect) Voice to Text Xbox LIVE bing Games Movies TV Music Apps Applications

SLIDE 11

Microsoft

Agile 2012 11

Microsoft

Agile 2012 11 J J

Story time!

SLIDE 12

Microsoft

Agile 2012 12

Microsoft

Agile 2012 12 J J

Once upon a time…

SLIDE 13

Microsoft

Agile 2012 13

Microsoft

Agile 2012 13 R R

They lived in a world where…

SLIDE 14

Microsoft

Agile 2012 14

Microsoft

Agile 2012 14 R R

Boundaries existed

“Before agile, dev and test were enemies; now they are partners”

SLIDE 15

Microsoft

Agile 2012 15

Microsoft

Agile 2012 15 J J

Kick off!

SLIDE 16

Microsoft

Agile 2012 16

Microsoft

Agile 2012 16 J J

Their first task

SLIDE 17

Microsoft

Agile 2012 17

Microsoft

Agile 2012 17 J J

Best buddies?

SLIDE 18

Microsoft

Agile 2012 18

Microsoft

Agile 2012 18 J J

Test/Dev: Best Buddies?

SLIDE 19

Microsoft

Agile 2012 19

Microsoft

Agile 2012 19 R R

The buddies worked together…

Dev:

sends code

review

Team:

reviews code

changes

builds & tests

new code

finds new bugs

Dev:

fixes found

bugs

updates code

review

Team:

signs off on

code

dev checks in

code

SLIDE 20

Microsoft

Agile 2012 20

Microsoft

Agile 2012 20 R R

They huddled every day around this archaic board

SLIDE 21

Microsoft

Agile 2012 21

Microsoft

Agile 2012 21 J J

Did we mention OneNote?

SLIDE 22

Microsoft

Agile 2012 22

Microsoft

Agile 2012 22 R R

Many dependencies, great responsibility

SLIDE 23

Microsoft

Agile 2012 23

Microsoft

Agile 2012 23 R R

We used Milestones “checkpoints”

SLIDE 24

Microsoft

Agile 2012 24

Microsoft

Agile 2012 24 J J

Nobody is perfect

SLIDE 25

Microsoft

Agile 2012 25

Microsoft

Agile 2012 25 R R

“I got your back, Bro”

SLIDE 26

Microsoft

Agile 2012 26

Microsoft

Agile 2012 26 R R

What’s this about “Exit Criteria”?

SLIDE 27

Microsoft

Agile 2012 27

Microsoft

Agile 2012 27 J J

Reality hurts

SLIDE 28

Microsoft

Agile 2012 28

Microsoft

Agile 2012 28 J J

The answer? Begin with the end in mind!

SLIDE 29

Microsoft

Agile 2012 29

Microsoft

Agile 2012 29 J J

It’s the thought that counts

SLIDE 30

Microsoft

Agile 2012 30

Microsoft

Agile 2012 30 R R

Automation happens!

SLIDE 31

Microsoft

Agile 2012 31

Microsoft

Agile 2012 31 R R

…but we didn’t automate everything

SLIDE 32

Microsoft

Agile 2012 32

Microsoft

Agile 2012 32 R R

Why NOT automate everything?

SLIDE 33

Microsoft

Agile 2012 33

Microsoft

Agile 2012 33 J J

We all took responsibility for quality

Quality Ownership

Dev Test PM Design

SLIDE 34

Microsoft

Agile 2012 34

Microsoft

Agile 2012 34 R R

Working in lockstep

SLIDE 35

Microsoft

Agile 2012 35

Microsoft

Agile 2012 35 J J

I Unit Tests!

“Unit Tests make me feel cuddly” “Thinking test-first helped me get the design right the first time” “Is it failing because of a problem in the code,

r because I don’t

understand the code” “Unit tests flagged a real bug in legacy code that I never would have found” “In God we trust. Everything else we unit test” “My unit tests revealed a subtle bug that never would have been found otherwise [except potentially by the customer]”

Real, unsolicited quotes from Xbox developers

SLIDE 36

Microsoft

Agile 2012 36

Microsoft

Agile 2012 36 J J

No unit tests? You’ve got some ‘splaining to do!

SLIDE 37

Microsoft

Agile 2012 37

Microsoft

Agile 2012 37 R R

Bugs still happen

SLIDE 38

Microsoft

Agile 2012 38

Microsoft

Agile 2012 38 J J

Bugs were “bliss” to this team

SLIDE 39

Microsoft

Agile 2012 39

Microsoft

Agile 2012 39 J J

What should YOUR team do?

Start “by the book”, and always follow the principles, but break agile as necessary Form dev/test buddies early Build quality in early – remove the walls Collaborate in person and in writing Create “done” definitions based on tests Automate pragmatically, using coverage to adapt Pay down your technical debt before it is long-term

SLIDE 40

Microsoft

Agile 2012 40

Microsoft

Agile 2012 40

SLIDE 41

Microsoft

Agile 2012 41

Microsoft

Agile 2012 41

James Waletzky Director of Development & QA Practices, Crosslake

(formerly Dev Lead @ Microsoft) jamesw@crosslaketech.com