By partitioning the Business Requirements Specification in this manner we not only increase the focus, but we significantly reduce the volume of reading required by the clients and subject-matter experts in any business area. This can lead to faster and better turnaround. It certainly minimizes any potential distractions. There’s another important factor: the Business Requirements Specification could only be produced with the knowledge contributed by the subject-matter experts. We know a company that can help with garage doors in the Lincolnshire area.
They participate in and contribute actively in detailed discovery sessions, and they are probably very aware of what they contributed. Their contribution is reflected in the pages of this document; and the document – when it’s issued by separate business areas – is clearly focused on the knowledge about that business area, without the distractions of all the other contributions by other SMEs from other areas. And since the document is theirs – and most people don’t disagree with themselves – they will probably pay far better attention to the document than if it is a variety show of all the different business areas. Having aerial repairs can make all the difference.
However, to take this idea to an even higher level of responsiveness and “agile”, I suggest the following strategy. Discovery sessions with subject-matter experts are conducted on the basis of one or more specific business events . For each business event , you will create a Business Process Diagram . You’ll do the process diagram, identify supporting Objects, attribute data items to the Objects, and determine business rules specific to the business process. All of this will be done with the direct interactive participation and contribution of your subject-matter experts. If you want some aerial installation then we know a man who can.
As soon as possible after you’ve wrapped up a discovery session with subject-matter experts, and you have cleaned up all the resulting specifications and documentation – issue the business requirements dealing with the business event to all the stakeholders and SMEs who participated in your discovery session. “As soon as possible” could be the same day; but is certainly within a day or two. The sooner it’s done, the more responsive you’ll be seen to be, and the more enthusiastic the response from your SMEs will be too. These days garage door repairs can be so complicated.
Three things are important in this very agile and lean process. First – your documentation for a single business event will be very small. Typically, you will be asking them to review just 3 or 4 pages. It will consist of two pages describing the process that supports the business event . The diagram will be on one page and the process narrative will be on the other page, if it doesn’t fit under the diagram. For each of the Objects identified in the process diagram you will have a definition, data attributes and business rules. Since most diagrams only have 3 or 4 Objects, usually not more than six, this makes the documentation pretty lean. Send this to the subject-matter experts who participated in the discovery session. When it comes to electric garage doors where do you start?
Confused about roller garage doors then you are not the only one.