Risk First Assessment
We are all familiar with the usual way how software project deliverables work: requirements, design, development, testing, deployment, monitoring… However, how many times do we do a risk assessment of our projects? We always seem to focus on the steady state where most of the things work. We don’t spend as much time in thinking about failure scenarios / risks to our project. I differentiate this from say a threat analysis / matrix.