Category: Business Analysis
General discussion of the business analyst role, key skills and tricks of the trade.
-
From Traceability to Trust: Why Requirements Management Matters
Requirements don’t manage themselves! Management refers to the ongoing coordination, traceability, and adaptation of requirements throughout the solution lifecycle. It’s how we maintain continuity…
-
Validation: Checkpoint, not Chokepoint
Validation is where we ask, “Did we get it right?” – before we build it wrong. Validation is the practice of confirming that documented…
-
Specification: Where Clarity Becomes Commitment
Think of specs as the GPS for delivery—useless if incorrect or unclear, essential when right. Specification is the process of representing business or customer…
-
Analysis: Where Input Becomes Insight
Analysis isn’t about taking what you heard and writing it down. It’s about figuring out what was really meant, what’s missing, and what matters…
-
What does it take to go from fuzzy concept to well-defined solution?
There’s a rhythm to effective solution definition, and it goes something like this: Elicitation. Analysis. Specification. Validation. Management. (EASVM, for short.) It isn’t the…
-
On the Essence of Business Analysis
I recently had the opportunity to talk shop with Dave Saboe, who runs the Mastering Business Analysis website and accompanying podcast. The topic of…
-
The Real Value of Visuals in Solution Delivery – A Reprise
The process of collaborative creation; of drawing and deliberating and rationalizing potential paths together until we reach an agreed upon “best way forward” provides…
-
Interview with Ryland Leyton, author of “The Agile Business Analyst”
Ryland Leyton recently released his book, The Agile Business Analyst: Moving from Waterfall to Agile. Over the years, Ryland has provided training and mentoring…
-
John Dewey on Starting with a Problem to be Solved
By starting with the problem, following up with objectives that articulate the definition of success, and then ensuring that requirements and subsequent solution artifacts…
-
Business analyst, these are the reasons your project will succeed
Let’s face it, lots of software projects continue to fail every year, even after so many advancements in the theory and practice of software…
-
Four Critical Components of a Meeting Invitation
While debates rage as to the effectiveness of meetings in general, and books have been written on meeting organization and management, I’ve found that…
-
Benjamin L. Kovitz on Requirements
“Without requirements, there is no way to validate a program design; that is, no way to logically connect the program to the customer’s desires.” …
-
Business Analysts and Grammar Police
Poor grammar and spelling that cause a requirements model to be inaccurate, or difficult to understand and use, are serious because they negatively affect…
-
Business Analysis Success is . . .
While traditional measures of business analysis performance can be useful, they don’t tell the whole story.
-
The “Obviousness” Danger that Kills Projects
What’s blindingly obvious from one perspective might not be intuitive or “obvious” at all from others.