Abstract
Product Owners, Business Analysts, and Product Managers are primarily concerned with the "what shall we build?" question. They may be considering this in the short term "what shall we build this sprint?" or the long term "what shall we build in five years?"
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
D. L. Parnas and P. C. Clements, “A Rational Design Process: How and Why to Fake It,” IEEE Transactions on Software Engineering 12, no. 2 (1986): 251–57; D. L. Parnas and P. C. Clements, “A Rational Design Process: How and Why to Fake It,” in Software Fundamentals: Collected Papers of David L. Parnas, ed. D. M. and Weiss Hoffman (Addison-Wesley, 2001).
- 2.
C. Jones, Applied Software Measurement (McGraw Hill, 2008).
- 3.
Ibid.
- 4.
Jeff Patton, “Dual Track Development Is Not Duel Track,” Dual Track Development Is Not Duel Track (blog), https://jpattonassociates.com/dual-track-development/.
- 5.
Cagan, Inspired: How to Create Products Customers Love (SVPG Press, 2008).
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2019 Allan Kelly
About this chapter
Cite this chapter
Kelly, A. (2019). Requirements, Discovery, and Demand. In: The Art of Agile Product Ownership. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-5168-3_4
Download citation
DOI: https://doi.org/10.1007/978-1-4842-5168-3_4
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-5167-6
Online ISBN: 978-1-4842-5168-3
eBook Packages: Business and ManagementApress Access BooksBusiness and Management (R0)