This article promotes a new approach to requirements management that reduces project complexity and improves communication between business and IT. This new approach can be used on its own, or as a supplement or precursor to existing approaches. Critical features of the approach are: detachment of business requirements from individual projects; and the production of testable requirements that can be shown to be complete, consistent, and correct prior to use within the SDLC.
 

We present a requirements framework and methodology that may be different from what you are doing. Its three prominent characteristics are a framework, a new model, and visualization. The framework ensures completeness of all requirements. The new model is the Decision Model, transforming important business thinking into a tangible and manageable business requirement. The visualization simulates user scenarios, alleviating the need for abstract specifications or models.
 

Today’s business systems aren’t agile – even when agile software methods are used to develop them. Companies need business agility, and in most cases we simply aren’t delivering it. 

Here’s an example from recent experience. I visited a very large health care organization and had conversations there with a variety of people.

Great teams, like all great organizations, are those that make a distinctive impact and deliver superior performance over a long period of time. For a project, performance is typically measured in terms of on time, under budget, with full scope of features, meeting quality specifications, and delivering the business benefit that was expected. Project teams do not need to be big to be great...big does not equal great. But all too often contemporary project teams are too large, too dispersed, too diverse, and just plain too complex to manage using typical project management techniques alone. So how can we be successful when a project demands complex teams? Success in the 21st century demands that we acquire new competencies to form, manage, and use large, diverse teams as a competitive advantage.

The purpose of companies creating Business Analyst positions is to improve IT quality and efficiency while reducing project failures. When I first started as an Analyst, coming previously from the position of Software QA and having an education in technical writing (think documentation), I thought I was the perfect mix for the position. I quickly learned that having a job where I prove my worth through project success can be stressful.

The Business Architecture has slowly emerged as a new and creative way to deliver value to enterprises that have undertaken this strategic initiative... However, many are rightly questioning the necessity of the Business Architecture, while trying to understand its purpose and realize its value. After all, most enterprises do not have a formal Business Architecture and many do not have plans to develop one.

Learn all about the ISEB diploma in Business Analysis offered by the British Computer Society (BCS). It offers an industry recognized qualification without mandating a set duration of prior business analysis work experience.

Until business analysts really begin to understand the difference between rules of the business (business rules), and choices about system design, we’ll keep falling to the same requirements and legacy traps as always. In my previous column I looked closely at the meaning of business rule. Now let’s probe the two fundamental categories of business rules: behavioral and definitional.

Smooth stakeholder participation is integral to the success of any project. Sometimes stakeholders hold information that is essential to thorough requirements discovery, so it is important that they be forthcoming. Other stakeholders must sign off on requirements as being final in order for a project to move forward, so it is important that they be decisive and willing to let go the discovery stage of a project.

 This article considers the unique complexities of large, long-duration, high-cost projects that pose challenges to project success, and offers both old and new management strategies to handle the complexities... The complexities of large projects require that particular attention be directed to planning the project, developing and delivering the solution, selecting team members, and sustaining a high-performing team over the long haul.

Although you can do ‘standard’ requirements gathering for Service Oriented Architecture (SOA) projects, there is now an evolving a set of analysis techniques, methods and approaches that purport to be better suited to information gathering and design specification. I will call these generically Service Oriented Analysis.

Through development and beyond we hope not to have show stoppers, anticipate builds and releases on time, expect teams to portray efficiency, want our customers to be happy, and hope that boss coming to work and singing melody. Sounds like a perfect five-course scrum, isn’t it?

Today the term Business Analyst is synonymous with a career in the IT industry but the most successful and valuable analysts are those who understand the 'business' rather than those who understand IT. So what exactly is a Business Analyst? What is the Business Analyst’s role? What is the best background for this job? What skill set is required? What type of person is the best fit? What training is required and available?

If you ask Business Analysts what they think about ‘Agile’, you’re likely to get a mixed bag of answers... With so many different ideas on what Agile is and how Agile impacts the Business Analysis profession, we decided to talk with leading experts in the Agile field and get their opinions on the subject.

For business analysts, understanding decision logic from the perspective of business people is key. For that you need business rules. But when can a rule be considered a business rule, and when not? This article presents five pragmatic tests for knowing when you have identified a true business rule.