seven-sutras

Seven sutras for Business Analysis

Sutra:  Sutra is a Sanskrit literature which means rule or short instructions prepared for memorization. It is well accepted word around the globe and world of dictionary explains it as “A rule or aphorism in Sanskrit literature or a group of aphoristic doctrinal summaries prepared for memorization”

With the advancement of the technologies and the development of different domains, a job title which developed exponentially and the most prevalent is business analyst. Business analysts are the people who can be the spine of any organization and has the potential to think of the profits during the losses. Business analysts (BA) are like the warriors for any organization who have to keep away the worries throughout the project life-cycle. A business analyst is a renowned and process oriented individual who has to live with certain conditions which sometimes are unacceptable to him but as he is considered as a most important aspect of any project he has to work selflessly with an inspired heart and steady mind to give his best during the odd times. He is the person who has to use his intellect without being egoist and thus he has to show an altruistic commitment to the work and behave like a sage to achieve the best results out of the work.

An individual either develops or possesses habits of a business analyst but there are certain sutras which I think should be followed while performing the routine activities, some of them are listed below:

  • Educate yourself: Education always plays a very vital role in the personal and professional development. It is the most important aspect and it doesn’t matter what the source of learning is. The same formula is applied to business analysts as well. A business analyst should always be in learning mode and it helps him in increasing the intellect and referring the live examples of senior business analysts act as a catalyst in the growth of junior analysts.  There are certain techniques and skills which should be groomed regularly in business analysts. The set of knowledge areas as defined by BABOK is also a necessary field to be learned by business analysts.

Continue reading

UML

UML Reloaded

UML, an acronym to Unified Modelling Language, is defined as the graphical notations of the real system which allows both design and viability of a system. The requirements elicited from business owners are sometime too complex to explain to the stakeholders and thus to summarize those requirements and abstract the essential details UML is widely used. It helps in visualizing the problem and in turn the solutions with better approach and reduction of cost and rework. In short UML is a mean to visualize, specify, construct and document software systems.

Graphical modeling languages have been around in the software industry for a long time. Some articles show that this technique is being used for more than 15 years now. The UML is a relatively open standard, controlled by the Object Management Group (OMG), an open consortium of companies. The OMG was formed to build standards that supported interoperability, specifically the interoperability of object-oriented systems. The OMG is perhaps best known for the CORBA (Common Object Request Broker Architecture) standards. UML is so wide and vast that nobody, not even the creators of the UML, understands or uses all of it. We all use a small subset of the UML.

The UML is a relatively open standard, controlled by the Object Management Group (OMG), an open consortium of companies. The OMG was formed to build standards that supported interoperability, specifically the interoperability of object-oriented systems. The OMG is perhaps best known for the CORBA (Common Object Request Broker Architecture) standards.

Continue reading

Requirements

Requirement – Techniques and Characteristics

Requirement is defined as the most important attribute of any business which must be delivered to provide the value. As per BABOK, a requirement is a condition or capability that must be met or possessed by a solution to satisfy the contract, standard, specification or other formally imposed documents and hence it becomes one of the key objectives of a business analyst to elicit and document correct and unambiguous requirements.

Requirements are broadly classified into different sections and this classification defines the criticality of the requirements. The higher level goals, objectives and needs of an organization are classified under business requirements. The business requirements define the reasons of project initiation and these requirements should hold the validity throughout the project life-cycle. Business runs with the stakeholders and the requirements of these stakeholders should not be ignored. These stakeholder requirements describe the need of the stakeholders and how they interact with the solution. Later comes the functional and non-functional requirements which describe the behaviour and information that the solution should posses including the different environmental conditions in which these solutions should retain its validity.

The term requirement generates a lot of discussion and many debates happen to qualify the list of those requirements that should be added to the final version of the requirement document or not. It’s important for business analysts and owners to work closely to classify the requirements and to avoid the ambiguity. The business analysts and developers can’t accurately judge the completeness or correctness of the requirements whereas the normal users can’t assess technical feasibility and hence it becomes very important to verify the requirements during elicitation.

Continue reading

stakeholder-management1

Stakeholder Analysis and Management

Stakeholders are important to any project and effective management of these involved stakeholders is absolutely crucial to the successful completion of any project. Stakeholders refer to a person, group, organization, member or system that is impacted by the organization’s actions and managing them throughout the life-cycle of the project is highly important. Stakeholder analysis involves the actions taken in analyzing attitudes of the required stakeholders.

Business Analyst being the liaison among different stakeholders plays very vital role in the management of these involved groups and persons. The stakeholder management is directly proportional to the success of the project. The poorly managed stakeholders always act as negative catalysts in the development of the project and this may lead to the project failing. Stakeholder management results in building coalitions and building potential partnerships among different stakeholders and in turn develops valuable trust.

Continue reading