model your threats
There is a huge overlap between good software design and secure systems, you can enable both by thinking about threats early and including threat modelling as part of your design process.
(how) does your system behave
Forget for a moment test cases, code coverage, functional specs ... if someone asked you to describe the behaviour of your system (or a part of the system), could you describe it in a few minutes?
tearing down walls
A developer creating code and throwing it over the wall. Satisfied his code is great, the developer moves onto another story card, task or project, that developer has put this code far out of their mind - it's someone else's problem now.
what if it was your data
As consumers, we are guardians (or not) of our own data - so why as engineers and designers, can we be so negligent in the safeguarding of others. What if you could mitigate the potential threats to a system and unnecessary or unauthorized exposure of data before even knowing what they are?
healthy squads are happy squads
Squad health should be looked at as just as important as the health of your code or pipelines and the Garage Method provides a framework for helping to measure and track the health of your squads. Healthy squads are typically far more engaged, collaborative, innovative and productive.