Team Skill 2: Understanding User and Stakeholder Needs



The Standish Group survey [1994] cited "lack of user input" as the most common factor in challenged projects. Although 13 percent of the respondents picked that cause as the primary root cause, an additional 12 percent of the respondents picked "incomplete requirements and specifications." From this data, it's apparent that, for over one-quarter of all challenged projects, a lack of understanding of the users' (and most likely other stakeholders') real requirements was a serious problem that interfered with the success of the project.

The most commonly cited factor on challenged projects was "lack of user input." [Standish Group 1994]

Unless we imagine that users worldwide are going to suddenly wake up one day and start doing a better job of both understanding and communicating their requirements, it's obvious that our development teams are going to have to take the initiative. In other words, our teams need to develop the necessary skills to elicit these requirements.


In Team Skill 1, we described the skills that will help you understand the problem being solved . In Team Skill 2, we provide a number of techniques the development team can use to gather and to understand the real needs of prospective users and other stakeholders. In so doing, we'll also start to gain an understanding of the potential requirements for a system that we will develop to address these needs. While we do this, we will be focusing primarily on stakeholder needs, which live at the top of the requirements pyramid.

The techniques we look at range from simple, inexpensive, and straightforward techniques, such as interviewing, to more expensive and quite technical techniques. Although no one technique is perfect in every case, exposure to a variety of techniques will provide the team with a rich set of skills to choose from. For each specific project, the team can then pick from the available techniques and apply the experience and knowledge gained from the elicitation effort on prior projects. In this way, the team will develop a set of skills that are unique and well suited to the environment and that can actively contribute to improved outcomes .


Chapter 8 The Challenge of Requirements Elicitation


Chapter 9 The Features of a Product or System


Chapter 10 Interviewing


Chapter 11 The Requirements Workshop


Chapter 12 Brainstorming and Idea Reduction


Chapter 13 Storyboarding


Managing Software Requirements[c] A Use Case Approach
Managing Software Requirements[c] A Use Case Approach
ISBN: 032112247X
Year: 2003
Pages: 257 © 2008-2017.
If you may any questions please contact us: