BRG Module 1 Truth 4 and Truth 11

Basically, there are 11 truths but I really like the truth 4 which depicts that there is a lot of difference in between just building the software and solving the business problems.

Truly, the accomplishment of building or developing a software is of no use if we don't know how to use that software to make changes in the business.

For example, in Bell MTS, we develop a new data plans or applications for the customer convenience,  but it is in no use if these technical changes do not satisfy the customer. Ultimately, lack of customer satisfaction will result in loss and the development made in system will be a failure.

However, I think Truth 11 can act as solution to Truth 4. According to data provided in learn, It is the responsibility of Business Analyst to make the changes to way the user thinks about problem.

Basically, after introducing the requirements, the business analyst should let the customers know that how these changes will help them to change their problem and earn profits.

In earlier example, BA can help the customers know about the usage of changes made in system and how can these changes will help them to earn profits.



Comments

Post a Comment

Popular posts from this blog

BRG Module 2

Needs Needs related to lots of things. The range of needs are from basic survival needs satisfied by necessities to cultural and social needs. For the marketing needs, it is a driver of human action which marketers try to identify, emphasize, and satisfy, and around which promotional efforts are organized. Such as business needs, stakeholder needs and product needs. Project Blast off It is a series of activity to start a requirements project. It collects enough information to get a project to launch and ensure this project is viable and measurable. A project blast off may prepare a few hours or several days because it is depending on the size of a projects and uncertainty of a project.
Read more

Non functional requirements

Non functional requirements mean how the product or system is supposed to be in terms of safety, security, usability and many more. They are very useful to make the product attractive or usable. They are used to enhance the quality of the product. These requirements should be properly overlooked or valued otherwise it may lead to failure. Look and feel requirements Look and feel requirements describe the intended spirit, the mood, the style of the product’s appearance. These requirements specify the intention of the appearance, and are not a detailed design of an interface. For example, Fibe TV should meet the designing standards. For this, it is not saying about any technical design nor there is something like its material or specifications. Overall, the statement just says whatever the designing requirements are the Fibe TV should develop some characteristics to meet them. The look and feel includes the following characteristics:       Simple to use...
Read more

BRG Module 3 BUC and The Brown Cow Model

Business Use case involve some process to achieve a business goal or to make the changes to the existing techniques. For example, To ensure the delivered product work properly or not we follow some process to evaluate the procedure. In Bell MTS whenever a new service is introduced, it's performance is tracked. The online surveys are conducted, then customers are asked to provide the relevant feedback and then that feedback is used to implement the changes and assure the delivery of product or service accurately. In this way, the value of product is enhanced and improved. The Trawling for business also involves the Brown Cow Model . In this business analysts evaluate that what we have at present and what changes are required to be made in the future.They also consider the business focus for today as well as future. Their are basically four quadrants, what are the business cases(today and future each) and how the systems to be used( future and present each)
Read more