Leadership & Management

Whether you call them Systems Analysts, Business Analysts, Systems Engineers, or Enterprise Architects, it is very encouraging to see this vital function being reintroduced to companies. As far as I am concerned, it was inevitable. I guess companies finally figured out you cannot satisfy your systems problems simply by using better programming tools and techniques.

Each day businesses call upon a business analyst to determine what must be done in order to accomplish a certain task. Each avenue must be explored and analyzed for a project proposal to be implemented. The project scope determines what the course of action may or may not be. Each person involved must answer to another until management is satisfied all has been done to rectify the situation. Everything stays on task. The project as a whole is coming together. Teams are co-ordinating with each other to apply the objective into the code. It is all going according to plan. At the end, it all falls apart. Nothing is as it seems. The project has failed to accomplish what it set out to do. The business analyst is hung out to dry. Every finger points to him or her. In actuality it is not the fault of the analyst.

Author: Tony de Bree

There are times when a company must hire a business analyst. When searching from an outside source there are certain things an employer should determine when hiring the perfect business analyst. Some of these suggestions are common sense. Other items listed may be overlooked in the desperation to find a qualified business analyst.

Author: Tony de Bree

There are times when a business starts to lose money and no-one is sure where the problem is located. Going over facts and figures only points to the bottom line. The bottom line continues to shrink. People start to get desperate. Strategies are planned and implemented to no avail. Tried and true measures are no longer working. It is time to call on the experts. The business analyst needs to be brought in. The problem is finding one who knows the company.

Author: Tony de Bree

The project scope is the core of an individual project. Without a project scope the project will just float. Proper needs assessments and other intricate details will be overlooked. Each project is designed to resolve issues the stakeholders are experiencing in their company. These well meaning individuals will dump data and information charts, lists and figures presumptuously on the desk expecting it to all make sense. The "here's the problem, fix it" attitude can be frustrating. There are numerous feature requirements which must be met. It is unclear as to what to prioritize where. Cost estimates may not be accurate. Delivery dates are tentative. It is enough to make someone through up their hands in desperation and say "I QUIT!". The trained business analyst will just grin and dive in. He or she will know what is needed is a project scope.

Author: Tony de Bree

I was recently helping a friend staff a fairly large project with a team of very experienced, very skilled people. I mentioned that people were really excited about the opportunity. He asked me “Why are they excited? What is it about this project that makes people want to work on it?”

That led us to a discussion about teams of highly skilled people and what motivates them to want to work on a project.

Author: Geri Schneider Winters

* Article used with permission from Wyyzzk, Inc.’s Resources for Business Analysts site at http://www.writingusecases.com This website of reports and tips contains information to help you succeed as a Business Analyst in IT.

This article explores the top nine reasons the author, requirements expert Ellen Gottesdiener, has heard for NOT doing requirements right -- and how to address these reasons in response.  Author: Ellen Gottesdiener

The software industry is exhibiting an increasing interest in requirements engineering — that is, understanding what you intend to build before you’re done building it. Despite the hype of "Internet time," companies across many business domains realize that time spent understanding the business problem is an excellent investme...

The Cornerstone of Business Transformation. The fiercely competitive twenty-first century business environment poses challenges at every turn. Both public and for-profit organizations must be flexible and adaptable to remain competitive. It is through successful projects that organizations manage change, deliver new business solutions, and ultimat...

Each year, organizations across the globe face astronomical project failure rates, often wasting millions of dollars per failed project. This paper examines the roots of project failure and centers in on the elusive, often undefined role of the business analyst. In response to research showing that many organizations have not set concrete requireme...

The talents, competencies and heroics of project managers and technologists alone cannot drive value into the organization. For business needs and goals to be converted into innovative solutions that truly bring wealth to the enterprise, a stronger bridge must be built between the business and the technical communities. Enter the business analyst. ...

This article provides a high level description of the job of the Business Analyst as well as summary answers on questions such as "Why you need a business analyst?", "What are the desired skills for a business analyst?", "How to find business analysts?", etc. Author: Katherine Walsh

Many organizations are scratching their collective heads over how to build and mature a business analysis center of excellence (COE). Where do we start? What does a business analysis center of excellence look like? Who owns it? How does it evolve? This white paper outlines the standard operating practices necessary for a business analysis center o...

In this column, I summarize the 12 worst of the most common requirements engineering problems I have observed over many years working on and with real projects as a requirements engineer, consultant, trainer, and evaluator. I also list the negative consequences of these problems, and most importantly suggest some industry best practices that can he...

Many managers and others who are not professional requirements engineers tend to greatly over-simplify requirements engineering (RE). Based on their observations that requirements specifications primarily contain narrative English textual statements of individual requirements and that all members of the engineering team are reasonably literate, the...