Tuesday, May 22, 2012

   Quick Links:   Articles     MA Blog     Community Blog     Templates     Books     BA Humor     Events     Jobs     Interview Questions         RSS Feeds

The Community Blog for Business Analysts

Community Highlights



Templates & Aides
Find templates and other useful aides for the business analyst.
ModernAnalyst.com LinkedIn Group
Requirements Template

Use Case Template

BPMN Cheat Sheet
Community Blog

Cascade - Day 5 - Principle #2: Projects change the business, so know the overall business first

Principle #2: Projects change the business, so know the overall business first

A never-ending discussion in IT circles is about how much IT staff need to know about the business that the information systems are supporting. It is high-lighted by every want-ad for an IT job that says previous experience in the employer’s industry is mandatory.

Is detailed industry knowledge  and experience absolutely necessary for an IT job?  No.

Can an IT staffer be effective with absolutely no knowledge of their employer’s industry?   No.

As in many situations like this, the ‘Yes’ answer lies somewhere between the two extremes. Like a pendulum, the level of industry knowledge will vary across this spectrum, based on the specific organization, and by the particular IT role; e.g. Analysts need to know more than Programmers, and it justifiably argued that Testers need to know even more than Analysts.

So, some industry knowledge is required. I suggest from experience, however. that several week’s research on an industry is equivalent to several year’s work experience, as much of a person’s experience is rendered out-of-date by industry changes, or is too specific to the company they worked at. This is more true today than ever, as the ubiquitous Web makes information about almost anything available with a text string and few mouse clicks.

As a result, IT needs to know something about the business going into a project, and the willingness to learn more as a project progresses.

The addendum to this discussion, however, is how much does IT need to know about the specific way their employer conducts business when competing in their industry . Again from experience, I suggest that very little or no such knowledge is needed going into a project. The cliché that “a little knowledge is a dangerous thing” applies here. If IT people know too much about the current business, they may be unconsciously constrained when devising new IT solutions by ‘the way things have always been done here.’  In extreme cases, this can lead to an IT staffer having the delusional belief that they know more about the business than the systems users and their management.

Do not fall victim to this belief. IT is about underlying hardware and infrastructure, and the information systems that run on them. The systems’ users and their management --- supported by all the strategies, policies, procedures and rules that define and control the business --- will know the specifics of their business better than IT; their jobs depend on it.

This is not to imply that all business users & management are omniscient, or that the all business’s operate without duplications or errors, or that there are not things the business doesn’t know yet. In fact, effective use of IT can address many such issues in the operation of a business, but IT and IT people do this in support of the business; IT does not define the business.

So, know your business in order to support your business.

 

posted @ Sunday, June 01, 2008 1:20 AM by David Wright

Previous Page | Next Page

RATING

COMMENTS

Only registered users may post comments.
  
Blog Information

» What is the Community Blog and what are the Benefits of Contributing?

» Review our Blog Posting Guidelines.

» I am looking for the original Modern Analyst blog posts.



Do you twitter?: If you want short updates on what's going on in the BA world and at ModernAnalyst.com, simply follow us on Twitter: http://twitter.com/ModernAnalyst



MODERN ANALYST BLOG - LATEST POSTS
BA ABCs: “C” is for Class Diagram BA ABCs: “C” is for Class Diagram
Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article ... Read More...

Thoughts on the Agile Extension of the BABOK
Today was the last day people could provide feedback to the IIBA’s Agile Extension of the BABOK. The most recent draft of the document was published i... Read More...

10 Things I Wish Someone Had Told Me When I Was Starting Out As A BA
I am no longer a Webinar virgin. Thanks to the good folks at the IIBA, this week I had my first Webinar experience as an interviewee as part of the II... Read More...


ModernAnalyst.com LinkedIn Group ModernAnalyst.com on LinkedIn: connect with fellow business analysts in order to develop and expand your professional network.
Learn More...

Browse ALL Books in the Store

 

Privacy Statement  |  Terms Of Use
Copyright 2006-2011 by Modern Analyst Media LLC