Those who need the software must talk to those who build it.

Bad requirements

• Lack of context when writing the requirement document
• No value for the user
• Too much detail
• Users don't know what they want
• No prioritization
• Difficult to estimate delivery times
• Too large requirements
• Too technical requirements
• Poorly defined target user
• Feedback 404 → No feedback
• Poorly acceptance criteria

Maturity of the team

How to measure the maturity of your team

Qualitative

• How long they've been working there
• Are they friends?
• Do they share the vision?

Quantitative

• Speed per sprint
• User history weights