A Conversation
A conversation about software development using Risk-First vocabulary.
A conversation about software development using Risk-First vocabulary.
What is the one thing every project needs to control to be successful?
To work out what to do next, consider the upside and downside risks you're addressing, and also what risks you introduce.
Why do we even have processes in software development?
Some suggestions for improving estimating in software projects, by considering risk.
Are all tasks in software development just managing risk?
Part of the 'Estimating' Risk-First Track, looking at an alternative to Scrum's Planning Poker
A quick primer to help parse a Risk-First diagram.
Ways to keep track of the risks you face.