Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  How to make users prioritise requirements usefully
Previous Previous
 
Next Next
New Post 9/18/2018 10:18 PM
User is offline Kimbo
438 posts
5th Level Poster


Re: How to make users prioritise requirements usefully 

Used to be called functional decomposition back in the old days.

So you have a set of business requirements and you need to work out what functions (user story, use cases, pseudo english, etc), workflow (BPMN, activity diagrams), rules (put them in the user story as acceptance criteria or in the use case as conditions), data (class diagram). I sometimes do a state-transition diagram to help with understanding of states in the workflow.

If you have time you can even mock up some screens and reports. I often use a state-transition diagram to show how the screens (states) and actions (transitions) to move between them.

Kimbo

 

 

 
New Post 9/28/2018 2:15 PM
User is offline Lisa Combest
5 posts
10th Level Poster


Re: How to make users prioritise requirements usefully 

I use the system of Critical To The Product, meaning if the product does not exhibit the feature or function, it will be useless. Important To The Product, meaning that the feature or function lends value to the product and the product would be less desirable or usable without it. Nice to Have In the Product, meaning that the feature or function is a good thing to have and will be extra furnishings on top of the important and critical parts.  Those terms seem to resonate with the customers.  If you drive the prioritization discussion on value, what features and functions provide the greatest value to the users and can that value be stated, it will help you along the way.  I hope that helps you.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  How to make users prioritise requirements usefully

Community Blog - Latest Posts

Ekaterina Barabash
Ekaterina Barabash
I address my thoughts to those who are in IT management for whom the terms such as quality of project implementation development and profitability indicators of the company are important.  And it is also addressed to business analysts whose daily routine is the process of communication with Customer. A little about myself first. The last 8...
1 Responses
Dan Tasker
Dan Tasker
I have long been a believer in the saying “Context is everything.” As a business analyst dealing with business users, understanding the context of the topic of discussion is essential. In thinking about what constitutes quality requirements it occurred to me that there are a number of additional contexts that play a role. Examples inclu...
2 Responses
Alexey Kiselev
Alexey Kiselev
We are writing User Stories to fix the scope and describe - what our application should do when implemented.User Stories are great, because the are: Short, Defining Roles, A great connection of the requirement itself and a business need. User Story declared as a high level definition of the requirement, but it could be used to s...
0 Responses




Latest Articles

Adding Value as an Agile Business Analyst
Dec 09, 2018
0 Comments
As more organizations move toward agility, development and project management teams still struggling to define a common language and standard regardin...
Featured Digital Library Resources 
Copyright 2006-2018 by Modern Analyst Media LLC