Risk-First Analysis
Part of the 'Estimating' Risk-First Track, looking at an alternative to Scrum's Planning Poker
Part of the 'Estimating' Risk-First Track, looking at an alternative to Scrum's Planning Poker
What is the one thing every project needs to control to be successful?
Why 'Crisis Mode' shouldn't be a mode.
What can you do with the risks on a software project?
Are all tasks in software development just managing risk?