When I hear the term "emergent requirements" I wonder if many speaking that word have any units of measure for the concept.
- How stable are the requirements as a start?
- How are these requirement elicited?
- Can the "new" requirements be connected to the capabilities, mission, vision?
- Have those items changed as well? Do we have a new mission, vision, or set of capabilities that drive new requirements?
- Is there some way to manage these emerging requirements to assure they are still connected to the business model for the famous "business value" measurement?
I don't seem to hear how this is exactly done in the agile development process. I know well how Scrum works, but it assumes that the "owner" has all these processes in place. That sounds like a really big assumption for me.
Can anyone provide guidance on where to look for these processes? How to connect the emerging business requirements with the ability to respond to those requirements?
