A few years ago I started organizing the requirements in my projects in a very specific way and that approach has greatly simplified my discussions with project stakeholders. My definitions roughly align with IIBA’s definitions in their Business Analysis Body of Knowledge (BABOK), but are more constrained. Under BABOK 3.0… Read more »
A RACI table I created earlier this year as part of the Business Analysis team’s Service Level Agreement. The purpose of the RACI and the SLA is to ensure that the other project team members know what the BA team will deliver for them and why, and what their responsibilities… Read more »
I was asked a few years ago by a project manager to outline the process I follow to gather and communicate requirements for projects. After some thought I came up with an initial version of the diagram below, and over the years have refined it as new techniques such as… Read more »
In late 2009 (just before version 8 was released), I began learning how to use Sparx EA. A different branch in the organization I work for had purchased a few licenses to evaluate using Sparx EA as a Data Modeling tool, they decided to go with a different product, but… Read more »
I work for a very small business analysis team in a very large organization, and was recently asked by a project sponsor to support their request for having a Business Analyst as part of their project. Here’s what I wrote (generalized a bit to anonymize it) Simple answer is time… Read more »