home

Blogs

Data Warehouse / Business Intelligence Requirements Elicitation. Where do You Begin? (Part 4 of 5)

I discussed dimensional modeling in the last post and why I felt this was something the BI BA can own. I also focused on red and blue people (nothing political here). These colors represent the business and IT. When blended they become “Purple People”, a Wayne Eckerson (TDWI) term. I wanted to continue down this path with data cleansing and data quality, and how BAs can assist in this area.

Data Cleansing

Data cleansing attempts to understand the content of the data, establish a standard form, and correct any inaccuracies detected. Data cleansing is done prior to the extract, transform, and loading (ETL) of the data. One of the tasks associated with data cleansing is the removal of obvious duplicates and not so obvious duplicates.

Is the BA a Product Owner or Tester On Agile Projects?

There have been many articles lately about the role of the BA on Agile projects. Some postulate that the BA role is closest to the product owner. After all, it is often suggested, they reside with and represent the business. They are in the best position to be the final voice when defining and prioritizing requirements.

CCBA vs. CBAP

As some of you may already know, the CCBA® has officially been announced and the exam is coming out soon. This is a new IIBA® certification for competent business analysts.

Who is a competent business analyst?

A competent business analyst is one who has invested time to develop their business analysis skills and expertise but has not yet achieved the level of experience required to sit for the CBAP® exam.

This certification is great for developers who have performed business analysis tasks for a minimum amount of time, or quality assurance analysts, or any other professional who has performed some business analysis task in the last 7 years.

Why should you consider this designation?

    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