In my last post I wrote about the Why->What->How product development continuum. In an enterprise/business context perspective the continuum changes slightly...
The business representatives (e.g. business analyst or product owner) identify the product requirements from a business perspective to address the business goal/need (e.g. reduce material ordering time). The technical representatives (e.g. architect, functional analyst) synthesize that information and derive additional requirements, if necessary, before handing the complete requirements set to the implementation/development team. So it becomes very important for the technical team to understand the business context (Why & What) so that when the product is developed, delivered and put into use, it addresses the original business need/goal effectively.
What are your stories/experiences relating to requirements in a business context?
What are your stories/experiences relating to requirements in a business context?
No comments:
Post a Comment