This skill goes a long way towards solving problems before they begin.
Tag Archives: requirements
Communicating is hard.
What is said is often not what is meant.
You aren’t gonna need it.
YAGNI. Believe it.
Know the acceptance criteria.
You can’t get there if you don’t know where you are going.
Know the problem.
“A problem well stated is a problem half solved.” –Charles Kettering
Uncover the user’s true intention.
Find out what the really want.
Nothing is permanent.
Expect things to change, for they will.
Find the real requirements.
Most projects suffer delays and rework because the true requirements are rarely fully understood.
Agile Principles #4: Collaborate with business people.
Business people and developers must work together daily throughout the project.
Agile Principles #2: Embrace change.
Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
