Use Agile for Areas Subject to Regulations?

Tags: agile, business analysis, requirements
Written by Ronald G. Ross on . Posted in Business Analysis, Compliance, Requirements
Tags: agile, business analysis, requirements
“You did a wonderful job!! The material was organized and valuable.”
Janell – Texas State University
“I found the course interesting and will be helpful.
I like the pragmatic reality you discuss, while a rule tool would be great, recognizing many people will use Word/Excel to capture them helps. We can’t jump from crazy to perfect in one leap!
Use of the polls is also great. Helps see how everyone else is doing (we are not alone), and helps us think about our current state.”
Trevor – Investors Group
“A great class that explains the importance of business rules in today’s work place.”
Christopher – McKesson
“We actively use the BRS business-side techniques and train our business analysts in the approach. The techniques bring clarity between our BAs & customers, plus more robust requirements for our development teams. We’ve seen tremendous value.”
Jeanine Bradley – Railinc
“Instructors were very knowledgeable and could clearly explain concepts and convey importance of strategy and architecture.
It was a more comprehensive, holistic approach to the subject than other training. Emphasis on understanding the business prior to technology considerations was reassuring to business stakeholders.”
Bernard – Government of Canada
“Your work has been one of the foundations of my success in our shared passion for data integration. It has had a huge impact on innumerable people!”
Rand Losey – Knowledge Engineers Limited, LLP
“Sessions flow together well and build upon the concepts for the series which makes the learning easy and better retention.
The instructor is knowledgeable and very attentive to the audience given the range of attendees skill and knowledge of the subject at hand. I enjoy her training sessions.”
Deborah – American Family Insurance
David Wright (@dwwright99)
| #
Wild thought – all of the things in the reply’s first sentence become requirements, even user stories: e.g. “As an Administrator, I need to present documentation of decisions to the appropriate regulator, in order to comply with Regulation XYZ”.
I think what this implies is that not all user stories are implemented in software. Agile then become s about more than software, but about overall solution, which some practitioners are trying to push. I don’t know if this is enough to make Agile successful overall for this type of effort, but it has to start working beyond the software in order to have any chance.