Why Do Requirements Need to Be Detailed & What Level of Detail Is Enough?

Why Do Requirements Need to Be Detailed & What Level of Detail Is Enough?

As development practices change, so do the reasons why we write requirements and the level of detail we go into with Requirements Specification documents. Even seasoned business analysts have at one point or the other asked themselves, “What level of detail is enough?”. The answer to this seemingly simple question is surprisingly complex and is inseparably intertwined with the reason why we write requirements in the first place: so that they can be read, understood, and implemented.

Read More

Defining The Scope Of Business Analysis With A Context Diagram

Defining The Scope Of Business Analysis With A Context Diagram

The main goal of all business analysts is to uncover unknown risks and requirements during the requirement discovery phase. But as many business analysts will surely attest to, sooner or later, the problem of scope creep inevitably arises, unless one takes concrete steps to prevent it.

Read More

A List Of Free Business Intelligence (BI) Training Courses For Business Analysts

A List Of Free Business Intelligence (BI) Training Courses For Business Analysts

This post comprises a list of free training that business analysts can use to gain the knowledge and experience of what to do when practising business analysis within the context of business intelligence.

Read More

Benefits Of Holding Facilitated Sessions Among Stakeholders

Benefits Of Holding Facilitated Sessions Among Stakeholders

We make hundreds if not thousands of decisions every day. Some more important, others less so. With each decision we make, we shape our future and possibly, come closer to the attainment of our goals. One of the most effective ways to increase productivity and make better choices  during requirements elicitation is by organizing facilitated sessions among stakeholders.

Read More

Importance Of Documentation On Software Projects

Importance Of Documentation On Software Projects

Documentation of software requirements should not be seen as optional, but a necessity. While the level of detail may vary depending on the approach adopted, be it Agile or Waterfall, it’s important to keep in mind why documentation is needed in the first place, before one goes too far in the wrong direction.

Read More

The Link Between Business Analysis & Needs Analysis

The Link Between Business Analysis & Needs Analysis

Needs Analysis is similar to business analysis especially in the sense that it is used to determine the needs of the business, and is centred on understanding the issues and opportunities faced by the business with the objective of finding resolutions, defining approaches to resolving issues and exploiting opportunities. In summary, it’s about:

 

    Read More

    A Beginner's Guide To Requirements Elicitation: What To Do After The Event

    A Beginner's Guide To Requirements Elicitation: What To Do After The Event

    From analysing data and preparing deliverables to supporting stakeholders through other stages of the solution development lifecycle, the role of the BA is certainly key to successful projects. The end of the elicitation event does not signify the end of business analysis activities, but the beginning of the BA’s involvement in other aspects of the project.

    Read More

    5 Cognitive Biases BAs Should Be Aware Of

    5 Cognitive Biases BAs Should Be Aware Of

    As professionals, we typically make decisions based on logic and information that is available to us. For example, Business Analysts typically make decisions on which techniques to apply when solving business problems and assist stakeholders in making decisions on which solutions to adopt. Cognitive biases can lead to bad decisions and errors in judgment and as such, BAs should be aware of them.

    Read More

    Solving Complex Business Problems: An Introduction to Soft Systems Methodology - Part 2

    Solving Complex Business Problems: An Introduction to Soft Systems Methodology - Part 2

    As discussed in the previous article, Solving Complex Business Problems: An Introduction to Soft Systems Methodology, the steps of SSM can be applied in any particular order and the analyst may choose to skip or apply steps depending on what is needed to understand the problem situation. The steps of SSM that will be applied in this article include:

    Read More

    Solving Complex Business Problems: An Introduction to Soft Systems Methodology

    Solving Complex Business Problems: An Introduction to Soft Systems Methodology

    Some business problems are by their nature, complex to handle. Due to their complexity and the non-suitability of traditional problem solving methods, Soft Systems Methodology (SSM) can be used as the methodology for arriving at recommendations for action and positive change. This recommendation for action can range from making minute changes to a process to introducing a new information system.

    Read More

    12 Key Questions To Ask Before Selecting A Requirements Management Software

    12 Key Questions To Ask Before Selecting A Requirements Management Software

    Selecting a Requirements Management Software should be done with as much care as when selecting any other software. You should identify which features are required for your project beforehand and assess if the tools currently available to you do not already meet your needs before hunting for requirements management solutions with all the bells and whistles you don't need. 

    Read More

    Business Analysis: Building Better Stakeholder Relations

    Business Analysis: Building Better Stakeholder Relations

    The Business Analysis: building better stakeholder relations through prototyping article, published on Justinmind blog, discusses 6 tactics that can help Business Analysts create good stakeholder relationships throughout the software development lifecycle. One of them is incorporating excitement requirements to increase stakeholder satisfaction.

    Read More