Your SlideShare is downloading. ×
0
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Lifelong Analysis Skills for Explorers and Process Junkies alike!
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Lifelong Analysis Skills for Explorers and Process Junkies alike!

230

Published on

Slides for exploring Framing - 3hr experiential session. …

Slides for exploring Framing - 3hr experiential session.

Given at Let's Test 2013, 20 May, Runö, Sweden

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
230
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Lifelong AnalysisSkillsfor Explorers and Process Junkies alike!Simon Morley@YorkyAbroadThursday, May 23, 13
  • 2. Why did we not find that fault?Why is testing late?How do we find the most importantfeatures to test first?What should we test?Who should test this?Thursday, May 23, 13
  • 3. FICL - My littlehelperF - FramingI - InformationC - ConsensusL - LessonsThursday, May 23, 13
  • 4. What’s framing?Frames draw our attention to certain aspectsleaving other parts out-of-view / attentionFrame:A mental model that guides our understanding of acomplex world by viewing it from a certain (limited)perspective.Thursday, May 23, 13
  • 5. Frame exerciseTalk to your neighbour and discuss whatwould be good quality in this product:Thursday, May 23, 13
  • 6. Thursday, May 23, 13
  • 7. Good quality?Thursday, May 23, 13
  • 8. TransactionalRelationalFocusEmotionFear offailureFilterDistortTime Cost QualityRiskThursday, May 23, 13
  • 9. The exercises will explore different aspectsconnected to framingUse your testing brains (whether test lead,tester, manager, developer, other...)This /might/ mean you don’t have allinformationBut also, be careful not to chase detailsThursday, May 23, 13
  • 10. Root Cause Analysis (Explore Framing)Bug reporting (Framing and Informationgathering)Prio analysis (Framing, Info gathering &Concensus)Risk analysis (Framing, Info gathering &Concensus)Thursday, May 23, 13
  • 11. Exploring FramingProblem:A customer receives a product and somefeature isnt working.The customer considers the non-working partsto be "basic".So a root cause analysis is requested from thecustomer.Thursday, May 23, 13
  • 12. Thursday, May 23, 13
  • 13. Exploring Framing #2Split into 3 groups:Development Team, Project Team,Product Mgmt Team. Each team consider:What mightve gone wrong?Potential reasons for problem?Potential hypotheses/areas toinvestigate?Make notes!Thursday, May 23, 13
  • 14. Dev Team Proj TeamDev TeamDev TeamDev TeamProduct MgmtProj TeamCustomerThursday, May 23, 13
  • 15. A customer receives a feature and some part of thefeature isnt working.The customer considers the non-working parts to be"basic".A root cause analysis is requested from the customer.What mightve gone wrong?Potential reasons for problem?Potential hypotheses/areas to investigate?Task SummaryThursday, May 23, 13
  • 16. De-brief / reflectThursday, May 23, 13
  • 17. Bug Reporting &Advocacy(Whole Group)Thursday, May 23, 13
  • 18. Bug Reporting #1You sit in an integration team.A bug/problem is found in testing - itappears to be blocking testing of a feature.So….What to report, how and in whatdetail?Any different perspectives?Thursday, May 23, 13
  • 19. Thursday, May 23, 13
  • 20. Bug Reporting #2Consider that the problem might block acustomer doing some acceptance testingHow would the perspectives andcontent change?Thursday, May 23, 13
  • 21. De-brief / ReflectThursday, May 23, 13
  • 22. How did the problem change when lookedat from the team vs the customer angle?(Framing)Did the type of problem affect the frame?Good Information in a bug report (Infogathering)What was missing?Thursday, May 23, 13
  • 23. Risk Assessment&Test Priority(Teams)Thursday, May 23, 13
  • 24. Risk Assessment2 Teams: Development & ProjectTask:A new release will contain 1 new and 2modified features.The new feature is a launch-blocker for a customer and the timescale appears“tight”.What aspects should each team think about?Make a risk list with guesstimates of riskassessment.Thursday, May 23, 13
  • 25. NewModModThursday, May 23, 13
  • 26. Test priorityassessment2 groups:Tester(s) & Rest of development team.As a tester you’ve thought of a new approach totroubleshoot a problem you’ve been stuck with(to help the project)E.g.There’s some new logging you can useA developer on the team has got a potential fixfor a problem that was blocking some testing.Which aspects to think about in determiningpriority of the tasks? What perspectives and whatinformation is needed?Thursday, May 23, 13
  • 27. Thursday, May 23, 13
  • 28. De-brief / ReflectThursday, May 23, 13
  • 29. Question re-visitWhy is testing late?Why did you not find that fault?You tested for THAT, didn’t you?Thursday, May 23, 13
  • 30. FICLF- FramingI- Information GatheringC- Coming to concensusL- Lessons/LearningThursday, May 23, 13
  • 31. References /Further ReadingDecision Traps:The Ten Barriers to Decision-Making and How toOvercome Them (1990; Russo, Schoemaker)Winning Decisions: Getting It Right the First (2002; Russo, Schoemaker)Quality Software Management,Vol. 3: Congruent Action (1994;Weinberg)Waltzing With Bears: Managing Risk on Software Projects (2003; DeMarco,Lister)Psychology of Intelligence Analysis (1999; Heuer)Understanding and Managing Risk Attitude (2007; Hilson, Murray-Webster)Thursday, May 23, 13

×