Sign in to confirm you’re not a bot
This helps protect our community. Learn more
These chapters are auto-generated

80:20 Rules! Building Software Smarter

0:00

On the 80:20 rule

3:23

Pareto Principle Productivity

4:58

Joseph Juran

6:16

Pareto sweet spots

8:28

What is Pareto analysis?

9:22

What is a Pareto diagram?

9:54

Mystery Cartoon - anime

10:17

Mystery Cartoon- laptop cover

11:11

Characters in Peanuts

12:30

The Peanuts Pareto

14:02

On living by the 80:20 rule

15:44

Agile Methods

16:26

Bug Clusters?

18:01

Bug Clusters!

19:00

Pareto analysis of defects

21:05

Example : Project W

21:26

Defect density implications

26:02

Identifying defect sweet spots

26:58

Finding deeper defects 2

27:46

Finding deeper defects 3

29:33

Build Smarter: Tip 1

30:07

Reactive versus proactive testing

30:16

Risk identification 2

30:58

Software usage

33:17

Risk based testing

36:57

Build Smarter: Tip 3

37:59

The largest room

38:06

Improving software development

38:18

Defect based improvement

39:06

Orthogonal Defect Classification

39:42

ODC preventing defects, Project X

40:37

Build Smarter: Tip 4

43:17

Test Reporting

43:25

Exploratory testing by novices

47:22

The 80:20 rule in exploratory testing

48:54

The power of exploratory testing

49:38

Build Smarter: Trick 2

50:04

Build Smarter tips

50:16

What's on the tree?

50:52

A last example

51:55

Last Words

53:25
80:20 rules! - Building software smarter
87Likes
46,990Views
2008Oct 13
Google Tech Talks October 8, 2008 ABSTRACT Ever notice that you seem to spend 80% of your time on 20% of your tasks? Or that 80% of the decisions in a meeting seem to occur in 20% of the meeting time? Welcome to the world of the 80:20 rule. When we design, build and test software, we have to determine where to start and what we should do next. The 80:20 rule helps provide an answer to these questions, while helping to increase our productivity and effectiveness. As well as being an agile principle, it's a common thread in other disciplines, and there's a special variation that applies to software defects. We'll explore the different ways testers and developers are using the 80:20 rule. This rule could be a secret ingredient to help you build software smarter! Speaker: Erik Petersen Erik Petersen has been involved in custom software development since the 1980s, now focusing on testing and quality. He has presented at more than twenty Australian and international conferences, winning several awards. He mixes industry experience with powerful ideas and a passion for quality, and has influenced the work habits of hundreds of testers and developers across the world. Erik's been heavily involved in the Exploratory Testing community since before he even knew what it was called, proposing the idea of paired ET independently of Kaner and Bach in 2001. He is pushing forward with research on ET and other agile methods. He has reviewed many agile and testing books, and accidentally named the Master Test Report In the IEEE 829 Test Documentation 2008 standard. Check out Erik's link site at www.testingspot.net

Follow along using the transcript.

Google TechTalks

348K subscribers