Рет қаралды 25,664
One of the most difficult judgment calls that a business analyst has to make is where to draw the line between a business requirement and a functional specification. In this video, I offer you some guidelines to help you make this judgment call on your own project.
--
Community ⯈ bablocks.com/m...
Courses ⯈ bablocks.com/c...
Podcast ⯈ bablocks.com/p...
--
Episode Transcript:
In this video, I want to talk a little bit more about the difference between business requirements and specifications. This is an area where a lot of new business analysts have a lot of difficulties because the challenge there is that there is no standard for what is a business requirement versus what is a specification.
And so for new business analysts there I see that they're constantly always seeking an answer to that question. How do I know what to put in my BRD versus what I should put in my functional specifications or my SRS document?
And the answer really to that is that there is no standard and it is unique to every situation. It is unique to the company that you work for. And at times it's even different.
Depending on the project that you're working on at the same company. But what I'm going to do in this video is I want to give you some guidance on how you can learn to make that judgment call on your own.
So on a project by project basis, you as a business analyst have to be able to make a judgment call on what you should put in your business requirements document versus what you should put in your functional specifications or your software requirements specifications document.
And for a second here. So you should learn how to make that judgment call. That is one of the hallmarks of what an inexperienced business analyst does because. As you become more experienced as a business analyst you start you stop relying on things like templates and on things like standards that might come from the IIBA or they might come from the PMI. You stop relying on those standards because you see how things actually work inside the company that you're working for. And a big part of you being able to be effective in that environment is that you have to learn how to make the judgment call on a case by case basis. So here's a little bit of advice on how to do that. When you're trying to figure out whether something is a requirement or whether it's a specification you have to always consider the level of detail that you're dealing with.
And there are three different levels of detail at which you can document requirements and specifications. The first level is what I like to call the client level. Or you can call the customer level depending on your company. But the client and customer level is the level of detail.
It's the broadest level of detail and it's the primary audience for that is your customer or your client. So if you're working inside a company the person on the business side of the company who's funding the project is the client or they're the customer. That person normally is a senior-level person director V.P. level President. That person is responsible for making sure that the resources are available for your group to be able to produce the solution that you need to produce. So they're the client.
At their level of detail, you're talking very broadly about the BRD - Bullet point level of what it is that the project is going to produce. And so you're BRD could be a simple couple of page document that basically outlines at a very high level what it is that the project's going to deliver that all goes into your BRD document.
The second level of detail is what I like to call the user or the operational level. So the client who's funding the project is not going to be in your requirements meetings, in most cases...
View the Full Transcript: LEARN.BA/busin...
--
#businessanalysis #businessanalyst #brd #functionalspecifications