Articles Blogs Humor TemplatesInterview Questions
Despite significant investments of time and well-intended stakeholder effort, many business process models still end up being not very useful for their intended purposes. Too many do not reflect the business accurately enough to be useful, do not have sufficient key stakeholders’ buy-in for real decision making, or do not include the kinds of process information that the model’s readers are looking for. Some even confuse their readers with complex or incongruous graphical notation.
"You teach best what you most need to learn". I love this quote by Richard Bach and firmly believe in it. It is the teacher or trainer who needs to keep himself or herself updated and learning so that one can give back the best. As BABOK® also has identified, a business analyst needs to have and develop teaching skills as well.
There’s so much buzz and interest about concept models these days, we asked Ron to summarize what they are, who they’re for, and why you need them. Here’s his response, short and readable. He’ll also touches on how you can get started, and where to find more information.
A business event is something that happens, and when it happens it causes a pre-planned response by the business, or as we shall call it here, “the work”. One category of business events are the things that happen inside an adjacent system. The work is made aware that the business event has happened because each happening produces a flow of data to the work. A business event is a significant happening – it is not just a mouse click. It is often a request for a service that your business provides, and the outcome is the provision of the service or product.
Writing functional specifications as a business analyst (BA) in an agile ecosystem is a challenge of a different kind. You no longer have the luxury of time (unlike bigger waterfall projects). You no longer can be sure with a specification version as the final document (because of the iterative philosophy). You are not sure how comprehensive the functional specification should be (Agile manifesto: working software over comprehensive documentation).
brought to you by enabling practitioners & organizations to achieve their goals using: