Change
This core concept refers to how elicitation results are transformed into requirements and designs in order to define change.
Let's look at an example to bring this concept around change to life.
Let's say you have just finished running a series of requirements elicitation workshops for an initiative to change a company's current manual payroll calculation procedures into an automated solution. Let's call this initiative the payroll calculation automation initiative.
You are now ready to start transforming your elicitation results into requirements and designs, such as process models, requirements documents, and potentially, user stories for the software development components of the initiative.
This example illustrates how the core ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access