Ch8 - Team Skill 2 Chapter 8: The Challenge of Requirements...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
1 Team Skill 2 Chapter 8: The Challenge of Requirements Elicitation Due to The "Yes, But" Syndrome The "Undiscovered Ruins" Syndrome The "User and the Developer" Syndrome
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Recall: The Requirements Pyramid
Background image of page 2
3 Recall: Standish’s Survey The most commonly cited factor on challenged projects was “Lack of user input + Incomplete requirements” WHY IS IT DIFFICULT to elicit requirements?
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Barriers to Requirements Elicitation The "Yes, But" Syndrome The "Undiscovered Ruins" Syndrome The "User and the Developer" Syndrome
Background image of page 4
The "Yes, But" Syndrome For whatever reason, we always see two immediate, distinct, and separate reactions when the users see the system implementation for the first time. 1. "Wow, this is so cool; we can really use this, what a neat job" and so on. 2. "Yes, but, hmmmmm, now that I see it, what about this . .. ? Wouldn't it be nice if . . . ? Whatever happened to . . . ?“
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 10

Ch8 - Team Skill 2 Chapter 8: The Challenge of Requirements...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online