Non Functional Requirements Checklist for BAs

If you are mid-project and trying to make sure you have covered every quality attribute the system needs to meet, this non functional requirements checklist is built for that task. It covers the six core NFR categories I return to on every engagement, with specific elicitation questions, a ready-to-use template, and guidance on cloud and SaaS scenarios. You can work through it section by section and have a solid NFR set drafted by end of day.

Business Analyst Problem Solving Framework

Business analyst problem solving is less about knowing the right methodology and more about developing a mental framework that keeps you focused on the actual problem rather than the nearest available solution. This article walks through the three areas that make the biggest practical difference: problem identification, elicitation, and audience-focused communication. I have drawn on 25 years of BA practice across government, utilities, and enterprise environments to show what this looks like when it gets complicated.

Business Analyst Interview Questions: Answer With Confidence

If you have a BA interview coming up, this guide gets straight to the preparation work that actually moves the needle. It covers the behavioural and technical questions you are most likely to face, how to structure your answers, and what to ask in return. Built from 25 years of BA practice across government, health, utilities, and enterprise.

Business Analysis Certifications: Which One to Choose

Choosing the right business analysis certification depends far more on your career stage and goals than on which badge looks impressive. This article breaks down the leading providers, their certification levels, and the practical differences between them so you can make a clear, informed decision. Whether you are just starting out or have years of experience, there is a structured path here for you.

How to Communicate Requirements to Stakeholders

Communicating requirements to stakeholders outside your immediate team is one of the most practically demanding parts of BA work. This article covers how to adapt your artefacts, structure your documents, and present requirements in a way that lands with finance, legal, operations, and senior leadership audiences. Real worked example included.

How to Write Non-Functional Requirements

Writing non-functional requirements is one of those tasks that trips up even experienced BAs because the formats most teams default to were designed around user-facing behaviour. This article walks through three practical approaches for capturing system rules, constraints, and non-functionals, with guidance on choosing the right one for each situation. If you have a requirement sitting in front of you right now that does not fit neatly into a user story, this is where to start.

How to Write User Stories and Acceptance Criteria

Writing user stories and acceptance criteria that genuinely guide development and testing is harder than the formats suggest. This article walks through the formats that work, the principles that matter more than format, and a real example where things did not go smoothly. If you have a backlog to refine or a sprint to prepare for, start here.

Stakeholder Engagement: A Practical BA Guide

Stakeholder engagement is one of the most consequential things a business analyst does, and one of the easiest to get wrong. This guide gives you a practical framework for identifying, analysing, and maintaining meaningful stakeholder involvement across the life of a project. Drawn from 25 years of BA practice, it covers the techniques, pitfalls, and friction points that classroom training rarely prepares you for.

Elicitation Techniques: Which to Use and When

Choosing the right elicitation techniques is one of the most consequential decisions you make at the start of any requirements project. This guide walks through all nine core methods, their trade-offs, and how to combine them in practice. Includes a worked example from a real project where the approach had to be rebuilt mid-stream.

Problem Solving Steps for Business Analysts

When you are facing a complex business problem, having a structured set of problem solving steps makes the difference between spinning your wheels and moving forward with confidence. This article walks through the four core steps I use across every type of BA engagement, from government reform to enterprise system replacement. It also covers the most common problems you will hit along the way and how to handle them.

We use cookies in order to give you the best possible experience on our website. By continuing to use this site, you agree to our use of cookies.
Accept