Category: Requirements
Business Analysts, Be Kind to your Stakeholders!
I can remember at times being frustrated at the lack of involvement in requirements validation on the part of some of my business stakeholders. It bothered me that we were doing this work for them, and they didn’t seem to want to take the time to give us the feedback we needed. Then it struck [...]
“Requirements as Inventory” Metaphor
Think of requirements as inventory or as component materials in a storage bin with a shelf life and a carrying cost. Inventory isn’t free. You have to pay someone to produce (model and document) requirements. You need a supply of good, current (fresh) requirements to produce a quality product.
A Requirements Model (Graphic)
There is no perfect, fits-all template or set of documents which will be effective across all companies or even for all of a given company’s projects. The business analyst should work with internal and external stakeholders to determine which communicative tools will best serve for each project effort and model requirements accordingly.
Seven Steps and a Nice Little Process Template
I recently read Barbara Carkenord’s book, Seven Steps to Mastering Business Analysis…
Don’t Forget the Constraints!
In addition to eliciting and specifying the requirements, an important part of the analyst’s value-add lies in helping business stakeholders and delivery teams identify and understand the constraints that will apply for the solution.
Begin with what you HAVE to do
The simple fact is, you can’t know all the details upfront. You can and should, however, be able to work with your stakeholders to identify the broader range of necessary capabilities and constraints, or “placeholders for conversations”.
Recent Comments