Managing Software Requirements: A Use Case Approach, Second Edition
by Dean Leffingwell, Don Widrig
Chapter . Team Skill 2 Summary
In this team skill, we've described three pervasive “syndromes” that increase the challenge of understanding the real needs of users and other stakeholders. The “Yes, But,” “Undiscovered Ruins,” and “User and the Developer” syndromes are metaphors to help us better understand the challenge ahead and to provide a context for the elicitation techniques we developed.
But since teams are rarely given effective requirements specifications for the systems they are going to build, they have to go out and get the information they need to be successful. The term requirements elicitation describes this process, in which the team must play a more active role.
To help the team in this mission, we've described a variety of techniques ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access