home

The Role of the BA in Creating a Common Vision

by Catherine Brunsting

Lack of predictability in getting a new product or service to market is one of the biggest threats a business can face. This problem is pervasive and many businesses are simply unaware there is a better, more predictable approach to deliver projects.

In her article Ms. Catherine Brunsting addresses how we can bring about predictability into what is delivered and when it is delivered, and how a strong Business Analyst can insure that this happens.

AttachmentSize
The_Role_of_the_BA_in_Creating_a_Common_Vision.pdf199.95 KB

Agreeing on what the business is, not the same as Requirements

Megan,

Me again.

What I have found is that when SME's can't agree on Requirements, it usually means that a group of people that are seemingly doing the same work actually have their own individual ways of doing that work. That means the business and IT have a few options: (1) requiring systems to be flexible in allowing different ways to accomplish the same function, or (2) getting the business to standardize on one way/process for doing the work.

I always recommend (2) get done before getting back to the Requirements definition. The usual outcome is a standard process that also allows for some flexibility, but that flexibility is based on different business scenarios rather than the personal choices of the people doing the work.

I know end-users don't like to hear that their 'requirements' really aren't, and I know the that most don't think about the fact that end-users come and go over time, but the systems will be in use for years or decades longer than the time any one person uses them. Systems do have to be "usable", but that can be accomplished without having to meet the whims of the people who happen to be around when the system is built or purchased.

David Wright
"It is the mark of an educated mind to be able to entertain a thought without accepting it."
- Aristotle

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group