Current Articles | Search | Subscribe (RSS)

Entries for the 'Requirements Analysis (BABOK KA)' Category

» FEATURED: Connect the Dots with Requirements Traceability, Part 3 - The Process

(1579 Views) (0 Comments)

Connect the Dots with Requirements Traceability, Part 3 - The Process

The CEO of a major corporation who was present when I described requirements traceability at a seminar asked, “Why wouldn’t you create a requirements traceability matrix for your strategic business systems?” That’s an excellent question. He clearly saw the value of having that kind of data available to the organization for each of its applications....

» FEATURED: 10 Ways Documents and Spreadsheets Sabotage the Business Analyst’s Career

(3710 Views) (1 Comments)

10 Ways Documents and Spreadsheets Sabotage the Business Analyst’s Career

At long last, Business Analysts are stepping into the spotlight... Most BAs, however, still rely on documents and spreadsheets to manually stitch together their requirements. For those BAs, this article points out five ways that documents and spreadsheets are hurting your career and preventing you from joining the growing number of BAs who ar...

» FEATURED: Using the Brainstorming Technique in Business Analysis

(3220 Views) (0 Comments)

Using the Brainstorming Technique in Business Analysis

Multiple stages of a project can benefit from brainstorming, from identifying your stakeholders, to eliciting requirements, to enterprise analysis. In UML for the IT Business Analyst, Howard Podeswa describes brainstorming as useful “during the Initiation phase and whenever the project is ‘stuck’”.

» How Information Affects Micromanagement

(1602 Views) (0 Comments)

Managers should do some soul-searching; do they really need that information or are they interfering with the responsibilities of others? My advice to managers is simple: Delegate responsibility, hold people accountable, and get out of their way.

» FEATURED: Connect the Dots with Requirements Traceability, Part 1

(5229 Views) (2 Comments)

Connect the Dots with Requirements Traceability, Part 1

Simple requirements changes often have far-reaching impacts, necessitating that many parts of the product be modified. It’s hard to find all the system components that might be affected by a requirement modification. Assessing the impact of a proposed change is easier if you have a road map that shows where each requirement or business rule was imp...

» FEATURED: Requirements Reviews - When You Want Another Opinion, Part 2

(2280 Views) (0 Comments)

Requirements Reviews - When You Want Another Opinion, Part 2

Many BAs wait until their requirements specification is complete before they present it to some reviewers. Busy developers, testers, project managers, and users have difficulty finding the time to scrutinize a large document on short notice. It’s far more effective to review an evolving document incrementally. Give reviewers just a few pages at a t...

» FEATURED: The Whole Requirement and Nothing But the Requirement

(4075 Views) (1 Comments)

The Whole Requirement and Nothing But the Requirement

It is wise to use whatever techniques we can to discover the 'real' requirements and business rules before embarking on development. We all seem to know that it is cheaper to fix problems earlier rather than later in an IT project. So why do so many of our projects exhibit the same mistakes?

» FEATURED: Requirements Reviews - When You Want Another Opinion - Part 1

(4202 Views) (2 Comments)

Requirements Reviews - When You Want Another Opinion - Part 1

In my view, the most powerful quality practice available to the software industry today is inspection of requirements documentation. A peer review is an activity in which someone other than the author of a work product examines that product to find defects and improvement opportunities.

» FEATURED: Using Adaptability as a Guide to Navigate the Uneven Terrain of Requirements Elicitation

(2270 Views) (0 Comments)

Using Adaptability as a Guide to Navigate the Uneven Terrain of Requirements Elicitation

Adaptability is a word that is not used enough in the context of business analysis and collecting requirements. Though it is used in the project world, “adaptability” is more synonymous with project methodology or project teams as a whole than it is with requirements elicitation or requirements management. Being adaptive to your surroundings is wha...

» FEATURED: Selecting Appropriate Requirements Views

(5810 Views) (1 Comments)

Selecting Appropriate Requirements Views

There is no single correct way to document specific requirements information. Every BA needs a rich tool kit of techniques at her disposal so that she can choose the most effective requirements view in each situation. In this article I offer some ideas about how to make that choice.

» FEATURED: Six Ways to Avoid Requirements Workshop “Traffic Jams”

(4286 Views) (0 Comments)

Six Ways to Avoid Requirements Workshop “Traffic Jams”

As we travelled around India we were initially amazed at how the traffic flowed. India is a populous country, of course, and they have an ever-increasing number of vehicles. No matter what time of day it was, the traffic seemed heavy. So, how can their constant flow of traffic work?

» FEATURED: Some Alternative Requirements Views

(5020 Views) (0 Comments)

An effective business analyst doesn’t just “write requirements.” Instead, the BA should think about the most appropriate way to represent requirements-related information in a given situation. Besides the traditional default of writing natural language statements, the BA should determine when a picture or some other representation would be valuable...

» FEATURED: Why Create Multiple Requirements Views?

(6420 Views) (2 Comments)

If you create only one view of the requirements, you must believe it. You have no other choice. If you develop multiple views, though, you can compare them to look for disconnects that reveal errors and different interpretations. There’s an old saying, variously attributed to the Swedish Army, the Swiss Army, the Norwegian Boy Scouts, a Scottish pr...

» The Process of Determining Business Requirements

(6922 Views) (2 Comments)

The Process of Determining Business Requirements

Taking time to determine business requirements before launching into a new IT or process-based project is a critical component of good planning and protecting company assets. Clearly defining the current process, the problems that need to be focused on, and working with the people in the organization before beginning your project will allow for a m...

» Book Review: Building Business Capability by Ron Ross and Gladys Lam

(3965 Views) (2 Comments)

Book Review: Building Business Capability by Ron Ross and Gladys Lam

Ron Ross and Gladys Lam have written an important book for the business analyst community. It aims to get business analysts out of the technology ghetto that many of us get stuck in. Regardless of the type of analyst you are, I think it would be worth your time to get your hands on and read this book. I’ll explain why below.

Page 1 of 8

First Previous [1] 2 3 4 5 6 7 8 Next Last

Join the Premier Community for
Business Analysts, Business Process Professionals,
Systems Analysts, Data Analysts, and more…

Business Analyst Articles: Business Analysis & Systems Analysis

Entries for the 'Requirements Analysis (BABOK KA)' Category

Join the Premier Community for Business Analysts, Business Process Professionals, Systems Analysts, Data Analysts, and more…

Business Analyst Articles: Business Analysis & Systems Analysis

Entries for the 'Requirements Analysis (BABOK KA)' Category

Join the Premier Community for
Business Analysts, Business Process Professionals,
Systems Analysts, Data Analysts, and more…