Requirements that you didn't know were there
summary
Hidden requirements turn on stakeholders not topics: analytics show users getting stuck but product owners ignore numbers until presented as cost savings; a manager asks for exact ROI so the scope shrinks. A project has 12 subprojects and about 100 people so a cardboard map of relationships helps. A documentation team cut from three to two forces scope choices. An Apple-style redesign of a clunky help system reduces one owner’s resistance, while a detailed financial breakdown sometimes succeeds and sometimes gets blocked by inter-personal rivalry.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:38One Word That Describes Your Customers Attitude to Your Work
- 22:04Personality Types
- 26:30Contact Us
related talks
29mDriving clarity in ambiguous projects
43mThis Is a Requirement. — "And what does it do?" — "It lights up blue!"
29mUnreasonable Estimates and Improbable Goals
38mFrom Conversation to Software
51mDependencies: Can your agile teams handle them? and if not.. how
41mEliminate waste..are we doing it all wrong?
30mTechnical scoping like a pro to build the right thing & be a superhero- Chandeep Khosa - PHP UK 2022
38mThe Human Element in Development