Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  Use of technically agnostic language when creating requirements
Previous Previous
Next Next
New Post 8/16/2013 6:11 AM
User is offline jayphil
1 posts
No Ranking

Use of technically agnostic language when creating requirements 


1st time user but been a BA for 15 years and have been using Agile Scrum & Kanban for over 5. Ive been having some blue sky thinking sessions lately to try and understand the process by which developers consume requirements and design (even in their heads) soltions. By understanding some of their processes, I hope to both improve (and simplify) this key part of my role but also to spur on developers to think differently - naybe a little more broadly - about how we can innovate by effectively utilising a different way of thinking.

When communicating with the team I wholly favour F2F conversations over boring documents but all too often see that my descriptions - even if I try and build variety into my approach - seem to foster almost immediate or automatic "go to" service components e.g. relational database, nested tables when I talk about what we want data to do for us, etc   

I was wondering if anyone has (or could point me to any reference) documents, discussions or know of advocates of ways of trying to remain technically agnostic - and as such try to prevent these "go to" solutions - when describing the what, how and why. I'm not naive and realise changing some key words probably wont break any new ground but was trying to understand perhaps more of the science of thinking at a more elementary level to try out some new ways of imparting knowledge. 

Well, until I master that Vulcan mind meld that is...

New Post 8/21/2013 6:41 AM
User is offline y.meerbergen
3 posts
No Ranking

Re: Use of technically agnostic language when creating requirements 

 Hi Jayphil,

I had a bit of the same problem. As I'm not from a technical background, I just used to say "I trust you about what you said, but I need to describe it in a way a business user can understand. Can you retry with user wording?".

It usually (after a bit if rework, admittedly) allowed to have a "natural language" solution, with the added value that the developer could understand ths solution in technical terms when the requirements came his way.

Just my 0.02€



Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Use of technically agnostic language when creating requirements

Community Blog - Latest Posts

If you're looking to visualize, analyze, and share data insights with ease, Power BI might be the solution you need. In this article, we'll cover what Power BI is, why it's important, and how to get started with it. What is Power BI? Power BI is a business analytics service provided by Microsoft that helps users visualize and anal...
How to Write Business Analyst Resume
Business analysts must have an up-to-date, visually appealing resume to be able to stand out from the competition. A strong business analyst resume should accurately reflect your skills, experience and qualifications while also highlighting your accomplishments and successes. We will provide invaluable advice on how to build a strong, effective bus...
Are you testing your product in the most effective way?
Today covid-19 pandemic has completely flipped the business model. Various conventional Business models like banking and health had to adopt the digital era. Even the school and colleges have to create various applications so that they can provide online learning for their students. All these statements justify the modern business model as complete...



Copyright 2006-2023 by Modern Analyst Media LLC