One of my favorite tools in business analysis is the premortem. Instead of waiting until the end of a project to find out what went wrong, and learn for the future, we can use this technique to go on an “imaginary time travel” to avert real failures.

This is the tenth in a series that explains the thinking behind the Volere [1] requirements techniques—previous and future articles explore aspects of applying these techniques in your environment. This article illustrates how the requirements travel all the way through an organisation – and beyond - and how everyone is interested in/affected by them but all for different reasons.

Are you a Senior BA who is looking for a new challenge? The Management Consulting BA role may be for you. This role is particularly interesting for BA’s who have adapted best practices to their strengths and are looking for a greater degree of independence and responsibility.

In this article we address the question of How TEM? by providing a deeper look into TEM main constructs and how to do a high level design in TEM. For those who missed the first article we hope that you will still find this article useful and self-contained in such a way that it will be easy to follow and understand.

The “good old workshop”. As a business analyst practitioner and trainer I often get asked the question “should we use a workshop?” quickly followed by “how do we run it?”. This article addresses the first question (subsequent articles will look at the second).

An alternative to eliciting use cases and user stories is to identify the external events to which the system must respond. An event is some change or activity that takes place in the user’s environment that stimulates a response from the software system. An event-response table (also called an event table or an event list) itemizes all such events and the behavior the system is expected to exhibit in reaction to each event.

Makes me wonder if the industry really grasps the duties and responsibilities of the BA. The industry talks about such people, but have we standardized a job description? We wrote several such descriptions as part of our “PRIDE” Methodologies for IRM and based on this, let me see if I can establish a standard job description.

BA CoEs, in one form or another, have been around for over two decades. This longevity may very well speak for itself as this is a very long time given today’s appreciation and variety of methodologies, and the technological developments to support them. Much of the discussions around BA CoEs however have remained static. While other disciplines have modified their approach to continue to be of value; allying their tactic to compliment the focal points of a company, the dialogue around business analysis and BA CoEs has remained limited to the subject of process.

This is a complete example of a Business/Systems Analysis Model using UML and including: Use Cases, Activity Diagrams, Context Diagram, and more.

The project sponsor decides to approve or not approve the BRD. But, this is only the position of yes or no. What were the criteria used to form that position? The Risk Tolerance Model helps form the position.

Whether it’s a requirements document for a solution enhancement or a stakeholder analysis for a business case, the information cultivated by the Business Analyst can often have use beyond its initial purpose. How can we make BA work come alive for the entire organization?

The advantages of attaining a certification, such as the CBAP, are difficult to overstate; the benefits are numerous. If you have the necessary experience, the designation is likely within your reach. You can easily form a feasible plan (even using your analyst skills, if you wish) for applying for and achieving the CBAP, and boost the direction of your career today. 

The Event Model is an implementation-independent model understandable by business and technical audiences. It depicts the logic of detecting and deriving a situation of interest from a stream of open-ended event instances. It is a model for event logic that should be easier to create and understand than techniques for event processing in use by organizations today.

As a business analyst you don’t have to put on a disguise to do your job, but you can take lessons from Undercover Boss; ask questions and discover where you can make business processes or systems operate more efficiently, engage and collaborate with your business stakeholders to get needed information from those subject matter experts, and make recommendations to decision-makers to solve business problems that you have discovered along the way.

You can now create an instant app from your schema, and add spreadsheet-like expressions for business logic – a complete system in minutes. In this article, we review a new technology from Espresso Logic that makes your requirements – schemas and logic - into working software, and show an example of building a full application from scratch.