
Sector | Software company, name withheld |
Scope | 18 developers |
Programme | WL-320 Secure code |
Duration | 2 days |
Result | 9 issues fixed in the next sprint |
Written for the client's leadership. The client's name and staff names are removed from this copy.
A software company's payments team shipped fast and reviewed fast. Security review meant a checklist at the end, and the checklist was always green.
Lena Sorensen ran WL-320 Secure code at their office for two days, with Owen Hartley and Nadia Brennan on the other two benches: eight seats or fewer to each instructor. Day one, the team broke a sample app. Day two, they fixed it in review.
In the sprint after the course the team found nine issues in their own code with the same review habits, and fixed them before release.
From the programme record. 18 developers on three benches.
When | Step | By | Outcome |
Week 1 | Stack and review process read | Lena Sorensen | Done |
Day 1 | Break the sample app: inputs, sessions, secrets | Lena Sorensen | 18 seats |
Day 2 | Fix it in review, pairs swap fixes | Lena Sorensen | 18 of 18 |
Sprint 1 | Same review habits on the team's own code | Client | 9 found |
After the programme | |||
Sprint 1 | All nine fixed before release | Client | Closed |
Sprint 2 | Review checklist rewritten by the team | Client | Done |
Issue | Priority | Status |
Card token written to a debug log | High | Fixed |
Session kept after password change | High | Fixed |
API key in a test config | Medium | Fixed |

Developers | 18 |
Instructors | 3 |
Issues fixed | 9 |
The checklist was always green. Two days later the team could tell me why it should not have been.
A second reader on every payments change
No secrets in test configs
WL-320 for every new developer