The 3 Amigos (sometimes referred to as a “Specification Workshop”) is a meeting where the Business Analyst presents requirements and test scenarios (collectively called a “feature”) for review by a member of the development team and a member of the quality assurance team.

User stories are probably the most popular agile technique to capture product functionality: Working with user stories is easy. But writing good stories can be hard. The following ten tips help you create good stories.

This new PMI-PBA certification for business analysis, from PMI, might introduce confusion in selecting the right certification to help you achieve your professional goals. This comparison includes application requirements, knowledge required, and your current or desired role.

The structure that use cases provide is far superior to the nearly worthless technique of asking users “What do you want?” or “What are your requirements?” In this article I share my perspectives on when use cases work well, when they don’t, and what to do when use cases aren't a sufficient solution to the requirements problem.

In the world of underlying competencies that contribute to strong business analysis, the soft skill of analytical thinking and problem solving may seem pretty self-explanatory. Clearly, it involves sorting through business problems and information in an informed, methodical way. In order to do this, an analyst must research the problem and then propose intelligent solutions.

Software developers often want to freeze the requirements following some initial requirements work and then proceed with development, unencumbered with those pesky changes. This is the classic waterfall paradigm. It doesn't work well in most situations. It’s far more realistic to define a requirements baseline and then manage changes to that baseline. This article defines the requirements baseline and describes when to create one.

A typical business function might contain several unique events each of which we want to end up as a component of a larger software application. So how do we go from a table containing textual information to a specification which a developer can use?

This article is the last in a trilogy of articles that map the evolution of a proven, practical, and robust methodology that applies decisioning techniques to fundamentally remake commercial software architecture and development.

In the book  Risk Savvy: How to Make Good Decisions, Gerd Gigerenzer describes the two sets of mental tools required for making decisions. When risks are known, good decisions require logic and statistical thinking. But when we are dealing with unknowable risks, good decisions also require intuition and smart rules of thumb.

This column examines the three basic kinds of knowledge workers involved in business processes, and discusses how the distinctions among them are important for engineering smarter business solutions.

This article discusses Stephen King’s creative writing method and provides an example of using it in developing a use case narrative: the main scenario with alternate and exception paths. Yes, that is correct – Stephen King, the prolific writer of contemporary horror, science fiction and fantasy novels.

The UML Class Diagram, sometimes known as the Static Structure Diagram, shows the dependencies and persistent associations between object classes.

A UML Sequence Diagram is used most commonly to show the realization of a use case in terms of interactions between business entities or software objects. This diagram therefore helps with the transition from non-object oriented activity diagrams and use case diagrams to the object-oriented paradigm of modern software development.

Strategic Enterprise Analysis is the study, modeling, and maintenance of the strategic direction of a company. This article is about conducting SEA. Moreover, it is about how a senior business analyst facilitates this executive board effort.

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.