Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Business Requirements Practices
Previous Previous
 
Next Next
New Post 4/4/2017 10:22 PM
User is offline KevinG
1 posts
No Ranking


Business Requirements Practices 

Hey guys, 

Looking to get your opinion on Business Requirements practices. 

What sort of a practice do you use when writing business requirements / functional requirement documents? Do you use Volere? Or do you use something else? 

Give your opinion as I am interested to know and find out about different practices that I may not have used/heard of and what the wider audience uses :) 

 
New Post 4/28/2017 4:54 AM
User is offline Tom McIntire
2 posts
No Ranking


Re: Business Requirements Practices 

We typically use a form of Lean Power Workshops to gather the High Level Requirements (HLR). These allow us to define the HLR, justify it, and prioritize it using the MOSCOW method. 

Once this is completed then we input the requirement into an application called JAMA (Great for Requirements, not so much for Test Plans) where we can track the requirement (approvals, change requests, and other modifications). It also provides accountability on the author and end user, which is often lacking and leads to arguments or missed requirements down the road.

 
New Post 5/10/2017 10:25 PM
User is offline Kimbo
456 posts
5th Level Poster


Re: Business Requirements Practices 

Hi Kevin

Generally, as a career contractor, I use what the company is using. Business requirements are text, functions are user stories (used to use use cases), process I use BPMN, etc.

Btw, I started on a Volere project and left after a week cause Volere didn't offer enough structure to define functionality and was to open to interpretation. Could see a disaster about to happen - it did too I heard.

Kimbo

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Business Requirements Practices

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