Who Decides The Project Requirements - Business Analysis

I am sure that most of us would agree that “Every Project Has Requirements”. Every time a new software application is being developed explicitly or implicitly there is always a ‘Business Analyst’ (BA) from the project team who performs the role of requirements gathering for every software project. While some requirements are crucial to the application others are considered to be gold-plated luxuries.

How do we determine that the approach being adopted to gather the requirements is accepted as a good practice? What makes an individual a successful BA who not only understands the business problems but also models a solution which can be effectively leveraged through the use of technology?

How can one be assured that a BA is given the power of execution to get the things delivered with a benchmark of quality and within the defined timeframes? Let’s touch base upon some of the key pointers which are essential and indispensable for business analysis.

Who Gather’s Project Requirements

Determining the project requirements is vital in developing successful software as they form a baseline between the IT team, the customers and the stakeholders on what features will be delivered in the new system. One needs to identify at the beginning of the project who would be taking the ownership for capturing the project requirements.

Today, many software developers do perform the role of a BA. The technical discussion coupled with absence of soft skills and business acumen not only dilutes the interest levels of the customer but can also witness a total disconnect. It would be best in the interest of all the stakeholders that the individual who is going to perform of the role of a BA master’s the basics of interviewing techniques for gathering project requirements coupled with a formal training or exposure in business analysis.

Requirements Gathering at Customer Site

Before going to the customer’s site and to facilitate smooth requirements gathering it would be advisable if the BA reviews any existing project reference material or supporting project documents. The documents would help a BA get the pulse of not only the current systems and processes but also identify the drawbacks or deficiencies in the existing systems. A BA should also be cognizant of the various stakeholders associated with the project coupled with their roles and responsibilities and interview the stakeholders accordingly to get more information.

Requirements Specifications, Tools and Templates

Business Analyst (BA) should communicate to the customer in the early stages of the project the standard templates and requirement management tools they would adhere to in order to document the requirements specifications. A Business Analyst (BA) analyses, documents, manages and presents the project requirements for review and approval to the client in a most comprehensible manner. Best approach would be to adhere to a standard template for documenting the software requirements. Most organizations make effective use of the SRS template described in the IEEE Standard 830-1998.

For projects large in size and complexity it is appropriate to make use of requirements management tool in documenting project requirements, versioning requirements, managing requirements change, tracking the requirements and reusing the requirements wherever possible. Some examples of requirement management tools are: Requisite Pro, Caliber-RM, Telelogic.
Managing Requirements Change

Should there be any queries or concerns towards any aspect of the planned project activity it is appropriate that one defines a clear process in identifying the key points of contact in the project engagement with proper escalation mechanism. The steering committee identified is responsible to advise on strategic direction, oversee planning and implementation, resolve open issues to manage requirements change. Proper protocols must be set to establish a process through which requirements changes are reviewed, analyzed and resolved. New changes must be mapped to the project objective. If the requirement does not map it either means the requirements are missing or they fall out of scope.

Industry Certifications

The International Institute of Business Analysis (IIBA) is an independent non-profit professional association serving today the growing field of Business Analysis. The IIBA has created the Certified Business Analysis Professional certification (CBAP) which would not only strengthens one’s conceptual base but would also leverage one’s existing career opportunities in today’s world of emerging and competitive markets. The Business Analysis Body of Knowledge (BABOK) also gives the necessary knowledge of the skills necessary to be an effective Business Analyst.