Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Validation Missteps Making Us Full Time Firefighters

0 views

Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

Validation Missteps Making Us Full Time Firefighters

  1. 1. Presented to Silicon Valley DVClubJanuary 26th, 2010Allison Goodman, allison.goodman@intel.com
  2. 2. My Background SSD Products that survived the fires to Products were market (some minus consumed by fires a few features) late in development 4 3
  3. 3. What missteps along the wayturn us into firefighters? Insufficient Planning Not Designing for Test Not creating and integrating Feedback Loops Lack of Transparency
  4. 4. Insufficient Planning-Don’t have what you need to testOriginal Test Coverage Not Enough SCOPE Scope Lack of Coverage Undocumented Assumptions Missed Dependencies
  5. 5. If you don’t plan for it…it will surprise you.Every surprise will end up as a fire …As you get closer to trying to ship a product you become a full time firefighter.
  6. 6. Plan! (in writing!) Keep track of the assumptionsTake the time to write it all down-who does what (owners!)-how does a feature really work-what “done” is-checkpoints along the way-success criteria And what everyone really needs
  7. 7. test
  8. 8. Not Designing for Test Very difficult to repeat tests for debug Waste time Getting test to fail againMy Design is Perfect Getting lucky vsNo plan tests- late implementation knowing it works Pass? Fail? Who knows?
  9. 9. If you don’t design for test, you won’t find or replicate issues … they will surprise you.Every surprise will end up as a fire …As you get closer to trying to ship a product you become a full time firefighter.
  10. 10. Design for Testing! Ability to Artificially inject fails Figure out coverageHooks & Bread Crumbs•  here you are (state) W•  ow you got there H•  ow to get back H Define Pass & Fail with Team Partner with Architects & Design, you are helpful!
  11. 11. tests?
  12. 12. Not creating & integrating Feedback Loops- New Market / Customer Requirements Planned Planned Testing Testing Stale Testing Hardware Software Firmware Marketing Working in Silos Implementation != Documentation
  13. 13. If you don’t create and implement feedback loops, you’ll miss issues…they will surprise you.Every surprise will end up as a fire …As you get closer to trying to ship a product you become a full time firefighter.
  14. 14. Create & integrate Feedback Loops New Market Requirements Run Test Planned Testing Additional Is it Effective? Testing Efficient? Adaptable to new requirements/usages Change it!Tight & Ongoing Feedback Hardware Software Firmware Marketing-Problems found on currentproduct-new info about systeminteractions Validation Team-actual implementation changes
  15. 15. Lack of Transparency Schedules run late, validation is squeezed Fewer iterations, narrower coverage, less thorough investigationsTeam telling What you feel ismgmt…or worse really happeningeach other, it’sall fine DONE!
  16. 16. If your team is not transparent, you’ll ignore risks and coverage gaps…escapes will surprise you.Every surprise will end up as a fire …As you get closer to trying to ship a product you become a full time firefighter.
  17. 17. Foster a Transparent Team Tell the real story, Encourage others to do the sameEveryone plays arole… Don’t declare DONE until it is really there…. Don’t punish for calling it out
  18. 18. Stop the Firefighting! Plan Design for Test Create & Integrate Feedback Loops Foster a Transparent Team
  19. 19. Questions??  Allison Goodman  Allison.Goodman@intel.com  Linked In  www.engineeringgal.com

×