Categories
Reaction

Reaction: Ensuring quality for a peculiar piece of software

Sketchnotes and thoughts on “Ensuring quality for a peculiar piece of software” by Joep Schuurkes

I watched an interesting talk by Joep Schuurkes where he explained how his team have built in quality for a software that doesn’t fit the model for your typical web/mobile app. There’s no prod environment or a MVP that can be delivered. The product itself is used very infrequently and is used in air gapped environments.

Some of this ran true with my experiences in the video security industry and curiously some of their practices were the same:

  • Use cases were something we used a lot in the past and I hated them! In fact my first post was on this topic. That said, I understood his argument about documenting the behaviour vs old stories.
  • Thin vertical slices was a practice that I’ve been used to adopting for a while, as is ending up as thin-ish vertical-ish.
  • Working in public would be new to me… my brain got terrified about security implications!
  • Zero bug policy is something we’ve tried and failed at. I really like the concept and would love to really put it to the test.
    • Our usual failing was “must fix… but we can fix it later when working on X”.
    • We failed to get buy in from above on this, making it hard to justify a bug as “won’t fix” because we won’t fix it now.
    • I really liked his line about done being done and good enough.

Leave a Reply

Your email address will not be published. Required fields are marked *