Project WolverineBroadcasting LIVE from the orbiting command centre

Category Archives: Waterfall methodology

Functional Requirements

Posted on by Geoff Munn

The functional requirements should reflect the level of risk and uncertainty of the project. Continue reading

Agile Design

Posted on by Geoff Munn

Agile design isn’t as radically different as some people would have you believe. Continue reading

Acceptance Criteria and Why They're Important

Posted on by Geoff Munn

Acceptance criteria are the oft-overlooked but super-useful part of story card management. Continue reading

Methodology o' the day: Checklist Thinking

Posted on by Geoff Munn

Checklist Thinking is something you’ve probably already done. A decent requirements phase should be enough. Continue reading

Groan, another methodology

Posted on by Geoff Munn

The world does not need another development methodology. Just use the best bits from what we’ve already got, and assemble a great team of people. Continue reading

Breaking the Deliverables Habit

Posted on by Geoff Munn

Drop the deliverables – do less and deliver more. A great client relationship will not require you to produce copious amounts of documentation and endless deliverables. Continue reading

Hybrid Water-Agile-Fall

Posted on by Geoff Munn

Agile isn’t for every part of the project. Continue reading

Are best practices really the best?

Posted on by Geoff Munn

Best practices are fine, as long as they’re appropriate. Continue reading

Use Cases & User Stories

Posted on by Geoff Munn

User stories are better than use cases Continue reading

The lie of the "three levers"

Posted on by Geoff Munn

The lie of the ‘three levers’, and why cost cannot be changed once the project has started. Continue reading

Browse by Topic