Skip to main content

Initial Requirements: Defining the Product

  • Chapter
  • 3792 Accesses

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.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   34.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   44.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    If the detailed use case reflects design choices, they are called design cases.

  2. 2.

    The word objects are used here in the object-oriented sense of analysis, design, and programming.

  3. 3.

    “In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in Systems Modeling Language (SysML) or as contractual statements.” See http://en.wikipedia.org/wiki/Use_case , June 24, 2014.

  4. 4.

    Although the standard was defined in 1998, it was reviewed and reaffirmed in 2009.

  5. 5.

    Bad estimates may also mean that the team doesn’t have enough experience, or enough experience in that domain yet. Breaking the use case down into user stories also helps to estimate because the scope is smaller. See Chapter 9 for more on estimating an iteration’s scope.

  6. 6.

    There are tools that easily convert spreadsheet lists like the RTM into online electronic “3×5 cards” that allow the team to work in whatever format they prefer.

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2015 Alan Cline

About this chapter

Cite this chapter

Cline, A. (2015). Initial Requirements: Defining the Product. In: Agile Development in the Real World. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-1679-8_7

Download citation

Publish with us

Policies and ethics