Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  emergent design/ emerging requirements (An Agile question)
Previous Previous
 
Next Next
New Post 10/18/2008 5:31 AM
User is offline Guy Beauchamp
257 posts
www.smart-ba.com
5th Level Poster




Re: emergent design/ emerging requirements (An Agile question) 

Craig,

If requirements define what the solution the solution needs to be able to do in order to achieve project objectives, and system specifications define how the solution will work from a systems perspective, then it follows that the system specification must  be directly associated to the requirements that deliver the objectives.

So to answer your question, the secario that is most likely to produce "critical requirement failure" must be the when where the "the systejm specifiaction [is] disassociated from the business objectives".

Logical analysis or trial and error (also known as "evolutionary" or "emergent design") are two methods of solutions definition. Business Analysis should be about analysis (you would think from the name) and not about any techniques that do not involve analysis.

Analysis has a definition ("breaking a complex down in to its component parts in order to examin the inter-relationships between them" paraphrased from Merriam Webster and OED) and activities which don't do this should not be called analysis.

The component parts Business Analysts break projects down to are

  • drivers
  • objectives
  • functional and non-functional requirements
  • scope statements
  • process rules
  • data rules

We have a plethora of methodologies and CASE tools that do this.Too many as we really should only need one methodology for what is one set of components!

"Emergent requirements" and "emergent design" do not take this route - which has advantages and disadvantages - but it is not analysis.

There is a size issue here: to change the size of an input field on a single screen in all liklihood will not benefit from doing analysis on the change - you might as well just do it and see what the users think and change again if needed. At the other extreme a national database of information that supports Identity Card functionality should not be developed using "emergent design" - it is just too problematic and costly (as you alluded too in another post).

Between these 2 extremes there are the range of 'normal' or 'most common' sized projects. At what size does a project no longer become suited to "emergent design"? How would that size be measured?

I don't know - but if in doubt, I would recommend analysis as it is simply more likely for things to go wrong than right and Business Analysis minimises the liklihood of things going wrong.

Guy

 
New Post 10/18/2008 1:11 PM
User is offline David Wright
141 posts
www.iag.biz
7th Level Poster




Re: emergent design/ emerging requirements (An Agile question) 

Guy, nicely said.

As a BA consultant these days, the firm I work for has its own methodology, and it has a slightly different component list of course, but the overall approach/concept is the same.

I believe "asking the business what they want" was mentioned earlier in this discussion. I think we can agree that is the wrong question, as it does not analyze anything, and people can't always think of everything they want... how do you know when you have captured all these "wants"?

A better question that people can answer is "What do you do?" along with "what do you need to do differently?". People can answer that question, and the answers drive our analysis approach.

 

 Guy Beauchamp wrote

Craig,

If requirements define what the solution the solution needs to be able to do in order to achieve project objectives, and system specifications define how the solution will work from a systems perspective, then it follows that the system specification must  be directly associated to the requirements that deliver the objectives.

So to answer your question, the secario that is most likely to produce "critical requirement failure" must be the when where the "the systejm specifiaction [is] disassociated from the business objectives".

Logical analysis or trial and error (also known as "evolutionary" or "emergent design") are two methods of solutions definition. Business Analysis should be about analysis (you would think from the name) and not about any techniques that do not involve analysis.

Analysis has a definition ("breaking a complex down in to its component parts in order to examin the inter-relationships between them" paraphrased from Merriam Webster and OED) and activities which don't do this should not be called analysis.

The component parts Business Analysts break projects down to are

  • drivers
  • objectives
  • functional and non-functional requirements
  • scope statements
  • process rules
  • data rules

We have a plethora of methodologies and CASE tools that do this.Too many as we really should only need one methodology for what is one set of components!

"Emergent requirements" and "emergent design" do not take this route - which has advantages and disadvantages - but it is not analysis.

There is a size issue here: to change the size of an input field on a single screen in all liklihood will not benefit from doing analysis on the change - you might as well just do it and see what the users think and change again if needed. At the other extreme a national database of information that supports Identity Card functionality should not be developed using "emergent design" - it is just too problematic and costly (as you alluded too in another post).

Between these 2 extremes there are the range of 'normal' or 'most common' sized projects. At what size does a project no longer become suited to "emergent design"? How would that size be measured?

I don't know - but if in doubt, I would recommend analysis as it is simply more likely for things to go wrong than right and Business Analysis minimises the liklihood of things going wrong.

Guy


David Wright
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Structured Anal...  emergent design/ emerging requirements (An Agile question)

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC