Requirements Elicitation & Management: 5 Habits Of Effective Business Analysts

Requirements Elicitation & Management: 5 Habits Of Effective Business Analysts

Business Analysts play a pertinent role in determining what functionality a system should or should not have. If you can ask these questions of every requirement, the implemented solution will have a higher possibility of acceptance:

Read More

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 inseparably intertwined with the reason why we write requirements in the first place: so that they can be read, understood, and implemented.

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

Why Do Business Analysts Miss Software Requirements?

Why Do Business Analysts Miss Software Requirements?

A project that ends with a deluge of change requests once operations have started can only signify one thingmissed requirements or unmet expectations. Requirements may be missed for many reasons on business projects. This article explores the reasons why requirements can end up as missed and some best practices to keep in mind for successful software implementation. 

Read More

A Guide To Avoiding Five Typical Pitfalls of Requirements Management

A Guide To Avoiding Five Typical Pitfalls of Requirements Management

Requirements development and management can falter at various points in a project, causing you to build your software on a faulty foundation of requirements. Prototyping can help a Business Analysis team avoid some of the most common mistakes in requirements development and management. Guest Post By Cassandra Naji.

Read More

The Link Between Requirements Traceability and Defect Reporting

The Link Between Requirements Traceability and Defect Reporting

Software requirements and the decisions made relating to them, carry through from the point of conception until the product is working in the live environment. One of the key activities that need to be completed during software projects is assigning priorities to requirements. 

Read More

The Thin Line Between Business Rules & Requirements

The Thin Line Between Business Rules & Requirements

Requirements elicitation sessions typically start with the question, “How do things work?”. By gaining an understanding of what works and what the business rules are, analysts are better positioned to identify the business rules from which requirements may be drawn.

Read More

3 Quick Tips for Requirements Sign-off

3 Quick Tips for Requirements Sign-off

When sign-offs are sought without political undertones and with the right intentions, there are certainly benefits to be had. The sign-off process should be approached as an opportunity for discovery that allows stakeholders to ask questions and get clarification on their areas of concern. A huge benefit of obtaining sign-off on requirements is that it indicates stakeholders are aware of, and are committed to seeing the solution live and in action.

Read More

Effective Requirements Review Sessions: Before, During & After

Effective Requirements Review Sessions: Before, During & After

Requirements Review Sessions or Structured Walkthroughs are designed to communicate, check and confirm requirements with stakeholders. During these sessions, participants are expected to ask and respond to questions, proffer suggestions and provide comments on the solution that is about to be implemented. To maximize the limited time you have with stakeholders, follow these key steps to ensure you get it right the first time.

Read More

5 Common Requirements Mistakes to Avoid

5 Common Requirements Mistakes to Avoid

This post was inspired by Donald Firesmith’s piece on Requirements Mistakes where he discussed the common mistakes that occur in requirements engineering. Keeping these mistakes in mind can help business analysts (regardless of their domain) develop improved requirements management processes that ensure the delivery of high quality requirements.

Read More

How to Discover Missing Requirements

How to Discover Missing Requirements

Non-functional requirements are easy to overlook. This is most likely because stakeholders often assume that these requirements are given and go without saying. Missing requirements are harder to spot during requirements evaluation than poorly specified requirements and are usually detected further down the line when the system is in the testing phase or has already been deployed to thousands of users. They become even more expensive to fix if they are architecturally significant. For example, It is often difficult to include performance, safety and security features to an existing architecture - Donald Firesmith, Software Engineering Institute, U.S.A.

Read More

Proof of Concept: Benefits & Risks of Prototyping in Business Analysis

Proof of Concept: Benefits & Risks of Prototyping in Business Analysis

I once worked on a project that involved a series of discussions and consultations on whether to build or buy software. After extensive analysis, the decision was made to build the system in-house. To get started however, we had to prove that it could be done. We did this through a proof of concept (POC).

Read More

Why Non-Functional Requirements Matter

Why Non-Functional Requirements Matter

I’d always thought that if the ICT Department delivered a system that satisfied all the functional requirements of users, one could call it a successful system. I thought that if the system worked exactly the way stakeholders said they wanted it to work, everyone could call it a day. You can imagine my reaction when I came across an article that challenged this view. 

Read More