What role does Business Analyst in implementation?

[rinku2]

Greetings,

I would be a playing a role of Business Analyst , please give your invaluable inputs ( start to finish of a project).

Best,

Satz..

[bernyalvarado · Accepted solution]

Hi Satish,

Through years I have seen many flavors of what a business analyst does, but in general, here goes some two key items that in my personal opinion a business analyst should do (or could do ).

a) Processes and Requirements: A business analyst should understand in depth the customer drivers, business processes and requirement. The business analyst has an in-depth functional understanding of how the system (ServiceNow or any external system...) works. The business analyst defines what the system should do so that the customer requirements are satisfied on the best possible way. The business analyst should also be in a position to provide guidance/coaching to the customer when there's opportunities to eliminate "waste" (LEAN concept) from the processes.

b) Validation: The business analyst validates that the solution developed is according to what was requested and that in fact meets the customer requirements.

Thanks,

Berny

[bernyalvarado]

Hi satish Annelli, was the above helpful? Do you have any further questions about the role of a BA?

Thanks,

Berny

[rinku2]

Good Day and Thank you Berny, it helped.

But wanted to share...

The way we work is gather requirements new requests / like for like, take signoff, pass on to dev and then to test, when doing the show and tell with the owners, scope gets changed...( we are following Sprints), if the changes are minor, we try fixing ,if major we de- scope them.

This has an impact to my Velocity /burndown

Any suggesstions...

[bernyalvarado]

Hi Satish,

It sounds like you're following a Kanban type of project. As in any other software development project, It's expected for things to change... that's the main objective of Agile Development; to quickly adapt and mitigate changes as these arise. My advice will be the following:

a) make sure that when you take the requests these have a clearly documented description of what it entails and a very clear and detailed acceptance criteria. This is something that should be signed off by your customer/end-user before making it to your backlog

b) don't wait until the story development is completed to have a review with your customer/end-user. Quick validation messages with some screenshots are always helpful.

c) when a change arises for a story that was successfully developed & tested according to the specification my advise will be to write a new story/card in your backlog for the change and appropriately prioritize it among the rest of the work pending to be done. Doing so will have a positive effect on always working on which is the most critical first and will eventually drive your team/customers on written detailed and atomic enough use cases which will improve the velocity of your team to deliver value to the business.

Thanks,

Berny