Business analysis planning is the activity that shapes everything else on a project. Get it right and your stakeholders trust your process. Get it wrong and you spend the rest of the engagement catching up. This guide walks you through the practical steps, the common traps, and what a good plan actually looks like in the real world.
The requirements elicitation questions you ask will make or break your analysis. This article shows you how to plan your questions by stakeholder level, avoid the most common questioning mistakes, and use a real worked example to get better results from every session.
If you are working on a waterfall project right now, you need a clear picture of what you are expected to produce, in what order, and what goes inside each document. This article walks through the five core business analyst deliverables in waterfall: the BA approach plan, business requirements specification, business case, functional specification, and non-functional specification. Each section tells you what belongs in the document and why, drawn from real project experience.
Getting your business analysis documentation right means knowing what to produce, for whom, and why it matters to them. This article walks you through how to make every document count, from early scoping through to detailed specifications. Draw on 25 years of real BA practice to turn your documentation into a genuine project asset.
If you are actively building your BA knowledge and want free resources that are actually worth your time, this list cuts straight to the ones I have found most useful across years of practice. From free business analysis ebooks to archived webinars and structured video courses, there is enough here to keep you learning for months. I have included context on what each resource actually covers so you can pick what fits where you are right now.
When your business case needs to compare multiple implementation options, gut feel is not enough. This article walks you through how to build solution assessment criteria, assign weighted scores, and use a decision matrix to produce a defensible recommendation. Includes a worked example with a real point of friction from project practice.
Requirements prioritisation is the work that determines whether your project delivers real value or burns time on the wrong things. This guide covers five practical techniques, including MoSCoW, dot voting, and buy a feature, with honest advice on weighting criteria and managing stakeholder conflict. Read it when you have a list of requirements in front of you and need to structure a prioritisation conversation.
When your backlog is overloaded and every stakeholder thinks their requirement is the most important, you need a structured way to make defensible decisions fast. This article walks through the most effective requirements prioritisation techniques I have used across 25 years of BA practice, including a worked example where the process nearly came unstuck. Use it to get your prioritisation done today.
Choosing between Agile and Waterfall methodologies is one of the most consequential decisions you will make at the start of a project. Get it wrong and you will spend months fighting the method instead of delivering value. This guide cuts through the bias and gives you a practical framework for making the right call.
When you are sitting in front of a problem on a live project, what you need is a clear approach and the right technique for the situation. This article walks through real business analyst problem solving examples, covers the most useful tools, and includes a concrete worked scenario where the straightforward answer turned out to be the wrong one.
If you are trying to stay current in business analysis, the right blogs and websites can do a lot of the heavy lifting for you. This is my curated list of business analysis blogs and communities I have found genuinely useful across 25 years of BA practice. Each entry includes an honest note on what it actually offers and who it suits best.