Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Business Proces...  Critique My High Level BA Process
Previous Previous
 
Next Next
New Post 5/16/2012 3:55 PM
User is offline captainsquirril
2 posts
No Ranking


Critique My High Level BA Process 

Hello. I am new to the BA arena. Please can you critique my general steps and confirm if all is correct.

This is just a quick high level example. Please confirm, or disagree - or assist.
OK - this is if the business case and need for change has allready been decided.

  • Step 1. Speak with all related stakeholders and actors of the system. Gather requirements about what they belive the new system/process should do and how it should work. I would do this via elliciation sessions with people in groups, workshops, surveys, job shadowing and 1 to 1 interviews.
    ** PLEASE CAN SOMEONE PROVIDE A STANDARD TEMPLATE I WOULD SAVE THIS FEEDBACK IN **?
     
  • Step 2. I would then analyse the requirements that I had gathered and build up use cases as to what each user would do, how it would work - what it would acheive and set some tests to confirm if we have acheived that use case.
     
  • Step 3. I would then put this into the business requirements document template populating each section.
     
  • Step 4. From this I would then build the functional specification to give to the developers and confirm all suggested work was technically possible?
 
New Post 5/24/2012 4:28 PM
User is offline M Prasad - http://mprasad.com
5 posts
10th Level Poster


Re: Critique My High Level BA Process 
Modified By M Prasad - http://mprasad.com  on 5/25/2012 1:19:22 AM)

 Hi,

You are doing well as a starter. However, you can review very high level points (like tip of iceberg)

1) Before starting with Business analysis activity need to understand client's or company's process in performing BA activity. This would help in understanding the artifacts required to be produced and when more proficiency is acquired , suggestions can be made on best suited business analysis approach. 

2) Need to understand the Business need (example, is the solution is for an new opportunity, problem)

3) Needed to understand the enterprise architecture

4) Requirement elicitation process, where one can use many artifcats including use cases, and techniques like brainstorming, interviewing, survey, etc.

5) Depending on the methodology and process requirements can prioritized and analysed.


Kind regards, M Prasad - www.mprasad.com
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Business Proces...  Critique My High Level BA Process

Community Blog - Latest Posts

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC