If requirements management practices were songs entering a popularity contest, requirements validation would hardly be a favorite contender. It's easy to understand why: validation is usually a tedious, time consuming task, and, as with nearly every quality control activity, it is supposed to reveal defects, going against our natural desire of being right, not making mistakes, and singing in tune.

Agile development practices introduced, adopted and extended the XP-originated "User Story" as the primary currency for expressing application requirements within the agile enterprise. The just-in-time application of the user story simplified software development and eliminated the prior waterfall like practices of overly burdensome and overly constraining requirements specifications for agile teams.

However, as powerful as this innovative concept is, the user story by itself does not provide an adequate, nor sufficiently lean, construct for reasoning about investment, system-level requirements and acceptance testing across the larger software enterprises project team, program and portfolio organizational levels. In this whitepaper, we describe a Lean and Scalable Agile Enterprise Requirements Information Model that scales to the full needs of the largest software enterprise, while still providing a quintessentially lean and agile subset for the agile project teams that do most of the work.

Most analysts are introduced to SOA in one of three ways; two of which are potentially painful and one of which is actually useful. I’ll let you decide which you would prefer.

The path to requirements elicitation is something that analysts are rarely taught. Everyone knows that it involves interviews and research, but within most organizations, exactly how the interviews and research should be conducted is nebulous.

Babies and Business Analysts go through four stages, as they open their eyes and see. 

In Stage 1, with eyes closed, BAs are blind to their organization’s mess.

In Stage 2, as their eyes begin to open, BAs see in black and white: a single process step, template or isolated requirement.

In Stage 3, the mobile movement of the outside world attracts and delights them: industries, methodologies, collaborations and emerging trends.

In Stage 4, they strengthen their muscles: the analytical and creative skills used to facilitate organizational futures and protect their parent enterprise in this new economic climate.

In the twenty-first century, business processes have become more complex; i.e., more interconnected, interdependent, and interrelated than ever before. Businesses today are rejecting traditional organizational structures to create complex communities comprised of alliances with strategic suppliers, outsourcing vendors, networks of customers, and partnerships with key political groups, regulatory entities, and even competitors.

A couple of months ago, I was driving along a well-traveled road here in town when my headlights fell upon a large pool of standing water. The little boy in me still loves splashing in puddles, whether on foot or in my car. I smiled at the thought of creating a huge spray. Unfortunately, the harmless puddle of standing water was actually a large pothole. What I thought was going to be a fun splash turned into a blown tire and bent rim. As business analysts, we encounter these water-filled potholes all too often.

In the last article I covered the term Service to death. In this one I want to go through a number of other SOA Three Letter Acronyms and terms that you may come across and for which you would like to be able to nod knowingly.

Many business analysts' find themselves in their role quite by coincidence but once there either decide this is a role they love or hate. There are certain requirements (if you'll pardon the cliche) or competencies you must display to be successful in this profession. We will first explore the foundational knowledge and skills needed in the early part of a business analysts' career and then what is required to progress.

A lot of people think that coming up with solutions to business problems is the hardest part about being a business analyst – particularly when working with a client who knows more about the business than you ever will. Don’t believe it, after all you’ve already made considerable progress in understanding the problem – and your understanding is based on level-headed analysis rather than a potentially emotional interpretation by your client.

Now it’s time to look for solutions – to be creative and think outside the square. In this paper we’ll offer a few tips and techniques for getting the creative juices flowing. We’ll show you that anyone can be creative and that solutions can come from the most unexpected places – you don’t have to be a subject matter expert to come up with valid, workable solutions to business problems.

Like all professions, business analysis has its golden rules – rules that are fundamental to the design of successful business systems. They might seem like common sense but it’s surprising how often we forget them and get ourselves into hot water.

Where application development is concerned, the ability to produce great code is just one small component of overall success. Just as essential is the ability for the developers to clearly grasp the business requirement – and deliver against an accurate functional specification.

Nick McKenzie, technical director at nVisionIT, notes that the process for the creation of an application is not always clearly understood. “From the business owner, to the user, to the developer, there are different perspectives and different expectations at play. As requirements pass through this chain, inconsistencies or assumptions can be introduced which can derail this process.”
 

Agile is here, and it's coming soon to an organization near you-if it's not already there. As a business analyst, are you ready to make the transition to this value-centered development approach? How will your role change? What will you do differently? What will you actually do as part of an agile team? What agile analysis practices might you adapt if you're working on a traditional (waterfall-style) project?

In short, how can you make yourself more valuable to your agile team and organization using your business analysis skills and abilities?
 

Understanding why BA CoPs fail is an essential part of strategic planning. If you can identify the gaps in your own organization, you will be in a much better position to put a plan in place to "Mind the Gap."  This article will look at 10 common reasons why BA CoPs fail.
 

Business analysis is an important aspect of agile software development projects, but the agile approach is significantly different than the traditional, serial approach of yesteryear. Because the agile approach to business analysis is different the approach to requirements specification is also different, for many traditionalists this will prove to be a significant cultural shock to them at first. In this article I briefly overview how business analysis activities fit into an agile approach, question some of the dogma around documentation within the traditional community, summarize some of the evidence showing that agile approaches are more effective in practice than traditional approaches, and end with strategies for specifying requirements on an agile project.