HI Craigwbrown,
You are doing great help to us.
I guess we can make stakeholder requirements as Business rules with exception as well as assumptions in Business requirement document.
I think we can also list stakeholder with their description,needs and responsibilites in BRD( Business requirement document).
Different stakeholder requirements have different importances, and sometimes they even clash.
I agree. Then PM/BAs should settle and get an agreement among all stakeholders before documenting final business requirement, once there is any conflict, not feasible or out of scope requests from different stakeholders. It seems like stakeholder requirement is something highier and before business requirement. Does this make a little sense? :)
Thanks, - Irene
Exactly Irene.
It's one of the biggest value contributions a BA can make - making sure all voices are considerred in requirements gathering, but then focusing on what is most important for the sponsor and the project.
Thank you, Craig!
I am still reading BABOK v2.0. As a BSA, I believe it is definitely helpful to read through the whole book, although I feel it is more focused on IT Business Analyst (as Adrian defined). Other than business analysis planning, communication, enterprise analysis, elicitation, etc., a more important job for BSAs is to interpret business requirement into technically doable functional or non-functional specifications. In my opinion, a BSA may not need to spend that much time as a BA to communicate with stakeholders, collect business requirement, be involved that much as a PM/BA to plan, monitor or elicit. If my understanding is correct, my questions are:
Thanks,
Irene
Irene wrote ... a more important job for BSAs is to interpret business requirement into technically doable functional or non-functional specifications. In my opinion, a BSA may not need to spend that much time as a BA to communicate with stakeholders, collect business requirement, be involved that much as a PM/BA to plan, monitor or elicit.
... a more important job for BSAs is to interpret business requirement into technically doable functional or non-functional specifications. In my opinion, a BSA may not need to spend that much time as a BA to communicate with stakeholders, collect business requirement, be involved that much as a PM/BA to plan, monitor or elicit.
My view on this is that you lways have to start with the beginning. If nobody else has done this business engagement and planning work, or if it has not been done sufficiently YOU need to take ownership and accountability for it.
Basically - once youy take on a task you are accountable no matter how good or bad the quality of the inputs. So yes - there is greater emphasis on technical specifications - but you also have to manage the business requirements as well.
Whether it is necessary for a BSA to get a CBAP certificate? If not, what is the best suitable certificate for BSA
I don't have a recommendation for this. I think solid work experience and working with the tutelage of a master practitioner is my main advice - and regulrly coming to Modern Analyst forums to both share oyour opinions and ask questions.
Is there any other book/reference similar to BABOK but more specific for BSA to systematically refresh the knowledge?
Yes there are several. Start at my blog here; www.betterprojects.net and follow the links to other BOKs.
brought to you by enabling practitioners & organizations to achieve their goals using: