Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  How to organize Features and Business Rules for further discussions?
Previous Previous
 
Next Next
New Post 12/1/2015 7:05 AM
Unresolved
User is offline opposer
1 posts
No Ranking


How to organize Features and Business Rules for further discussions? 
Hi everybody. 
Here is my task.
The company, where yesterday was my first day, is developing a software, and it's partially complete. I'm first analyst here, and before hiring me theydiscussed all the requirements orally and didn't store them, so there is no any project documentation. So they gave me a task to organize all the features that are already released - into knowledge base, so they could discuss and add new functionality being able to see all that is done before. They want to prevent features conflicts also. 
So we had a workshop with teamlead and project manager, I extracted tons of facts about the software - about its features and business rules, which they conform to. I've organized user features into hierarchy and business rules among them  My idea is to organize the user features and business rules into one mindmap, so they could see them all when discussing new features.

Are there any better ways to organize this knowledge base? I wanted to organize features into a fishbone diagram, but how can I add business rules into it? Mark business rules somehow? Or are there any better ways to organize business rules and features?
 
New Post 12/10/2015 11:10 AM
User is offline Chris Adams
307 posts
5th Level Poster






Re: How to organize Features and Business Rules for further discussions? 

It sounds like you have pretty good handle on the features and business rules given where you started.  My main piece of advice is to map the features and business rules back to a requirement.  All features originate from a need.  Feature conflicts arise when a feature conflicts with a requirement or when it isn't the best way to satisfy that requirement.  

This process doesn't have to be too fancy or complex. I would take a somewhat agile approach to start. Create 1-3 sentence user stories representing each requirement.  Then map each feature to one or more user stories. And of course features can also have sub-features (your fishbone diagram).  I've written about a common method for creating user stories in our interview questions.

Using this technique, you capture the requirement in 1-3 sentences and then you document the acceptance tests on the back of the "card".  The back of the card is also a great place to capture specific business rules too!  Of course, here I'm discussing physical index cards for the sake of an example, but you can represent all of this in a database with fields for each or in a word document. 

The main takeaway...map to requirements.  Hope this helps.


Chris Adams
Core Member – ModernAnalyst.com
LinkedIn Profile
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  How to organize Features and Business Rules for further discussions?

Community Blog - Latest Posts

EA Learning
EA Learning
I recently walked into a large shopping centre on a mission to buy a christening present for a friends son. I was very clear on what I wanted I just needed to find it… I was on my lunch break so I need to get the job done as I had a meeting that I needed to attend back in the office straight after lunch! I am not a frequent shopper and to b...
0 Responses
BusinessAnalysisHub
BusinessAnalysisHub
Have you woken up in the middle of night thinking how am I going to steer my team, give them the direction that they need but at the same time not constraint in what they want to build/deliver. I recently went through one of these night- I have joined an interesting project where we have very tight timescale to deliver a tech product to operational...
0 Responses
Peter
Peter
If you are building a reusable Security Product tool to specifically address Security Technical Implementation Guide (STIG)  Findings, should the requirements be considered Non Functional Requirements or Functional Requirements? For example if there are a number of STIGs such as: The minimum password length shall be 15 characters ...
1 Responses


Upcoming Live Webinars



Latest Articles

The Elevator Speech... for the BA
Nov 12, 2017
2 Comments
A BA walks into an elevator, is joined by an executive, and suddenly the executive asks the BA, “So, what are you working on these days?” ...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC