Initial Requirements: Defining the Product

Alan Cline

Chapter Chapter 7 in Agile Development in the Real World, 2015, pp 119-137 from Springer

Abstract: Abstract The previous chapters explained how the project manager collected initial project information: project charter, mission statement, stakeholder expectations, project abstract, and feature catalog. In this next step of progressive elaboration, the business analyst will drill down another level and collect the initial requirements.

Keywords: Requirement Elicitation; User Story; Business Processing Modeling Notation; Business Analyst; Requirement Defect (search for similar items in EconPapers)
Date: 2015
References: Add references at CitEc
Citations:

There are no downloads for this item, see the EconPapers FAQ for hints about obtaining it.

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:spr:sprchp:978-1-4842-1679-8_7

Ordering information: This item can be ordered from
http://www.springer.com/9781484216798

DOI: 10.1007/978-1-4842-1679-8_7

Access Statistics for this chapter

More chapters in Springer Books from Springer
Bibliographic data for series maintained by Sonal Shukla () and Springer Nature Abstracting and Indexing ().