Product priority

The basics of product prioritisation:

1. Everything should have a number one priority
(it's clearly part of our core proposition)

2. Everything should be done in the next release
(it's because you are not planning and coding properly)

3. The planned release can always be disrupted for the latest big idea
(we just can't wait another 20 days to properly plan, build, test and deliver it)

4. Everyone else's ideas are ridiculous
(i.e. let's not build them)

Basics of post-release analysis:

1. That was my idea first
(it's not my problem you can't remember me suggesting it)

2. What idiot thought of this?
(I hope they've forgotten it was me)