An epic is where we start to go into detail. We try to map out the scenario, a set of steps to be found within one process, or perhaps a use case where we might have standard and alternate flows. This will be content where some additional analysis might be required, looking at impact, dependencies and the costs and benefits of the value we are generating with our solution. A sound epic structure also helps us in establishing transparency, when you think about it. Let’s try to map this out.
What will very often also change once you start modifying processes willy nillly like we’re doing in this exercise? The business rules could very well change, and most likely will. Now what do the results look like? Now you have come up with a process that is unique for that particular actor, based upon some modified constraints you have put together with revised business rules. Now, can that possibly be a delighter for your customer? Possibly.
Can standard requirements look different, depending on the market you’re trying to serve? You betcha. A great differentiator would be how requirements are seen in developing and developed countries. What. You’re saying there is no such thing as such a divide, and you can find both in different regions and even countries in the world. Guess things are more fragmented than we would like to admit.