In the past, most IT products were built following the waterfall methodology, which is based on requirements. The client provides a statement of work with all the requirements. The IT team will work on the architecture, the development, and the requirement implementation. This approach is not flexible and will limit the number of iterations that can be done. Furthermore, you will have to wait several months before you can see and use the product. Business needs, policies, etc., may change, and by the time your product is released, it may not be relevant or may not ...
© Dr. Emmanuelle Savarit 2020
E. SavaritPractical User Researchhttps://doi.org/10.1007/978-1-4842-5596-4_22. Understanding Product Development Phases
Emmanuelle Savarit1
(1)
London, UK
Get Practical User Research: Everything You Need to Know to Integrate User Research to Your Product Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
