Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Business Requirements Practices
Previous Previous
 
Next Next
New Post 4/4/2017 11: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 5: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 11:25 PM
User is offline Kimbo
433 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

LN Mishra, CBAP
LN Mishra, CBAP
Traceability is one of the lesser understood aspects of business analysis. It is indeed quite hard to maintain good traceability unless automated. This is why BABoK® warns us being theoretical about traceability. In this article, I would like to explain traceability concepts with help of an example. BABoK® definition of traceability: ...
2 Responses
Hitendra 01
Hitendra 01
Most IT jobs have a clear, specific job description and career path. However, the business analyst career path tends to vary, as do the descriptions from job to job. The business analyst career path is best. Because, “There are career tracks that zigzag back and forth between IT and business. Someone might start as a business analyst, and the...
0 Responses
Arash
Arash
What is Data Analytics? To understand the meaning of Predictive Analytics, let’s describe what Data is first. Data is a collection of facts, information, and observations related to a context. The data can be either structured or unstructured, stored in databases, spreadsheets, files, etc. Data analytics is the science of examining the data ...
1 Responses




Latest Articles

Make your work visible
May 22, 2018
0 Comments
When speaking to a business analyst on a busy project, I am often told that ‘at the end of a working day, I feel like I have achieved nothing&rs...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC