Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.
Chapter 2: Business Analysis Planning and Monitoring 65 · Sharing Sharing is caring. The idea of sharing a positive risk really means sharing a mutually beneficial opportunity between two organizations or projects, or creating a risk-sharing partnership. When a project team can share the positive risk, ownership of the risk is given to the organization that can best capture the benefits from the identified risk. · Enhancing This risk response seeks to modify the size of the identified opportunity. The goal is to strengthen the cause of the opportunity to ensure that the risk event does happen. Enhancing a project risk looks for solutions, triggers, or other drivers to ensure that the risk does come to fruition so the rewards of the risk can be realized by the performing organization. · Acceptance You know this risk response. Acceptance is the process of simply accepting the risks because no other action is feasible, or because the risks are deemed to be of small probability, impact, or both, and a formal response is not warranted. You can accept both positive and negative risks. There you go. Feel free to drop these risk management terms at parties, social mixers, and family reunions, but I'd save them for risk management meetings if I were you. Choosing the Business Analysis Activities As a business analyst, you know that you probably don't have the time or the need to do every possible business analysis activity for requirements. Management, customers, the project manager, and the project team are eager for you to complete the require- ments gathering so that the project deliverables and benefits can be realized sooner rather than later. The longer you take to complete the requirements activities, the longer it'll be before the project team can deliver the benefits to the customers and the organi- zation. While it's true that the project scoping can't begin until you've gathered the require- ments, it's also true that a rushed requirements process will likely result in project exe- cution errors. It's important for the organization to give the business analyst the proper amount of time to do just the right amount of business analysis. A "proper amount of time" means that the business analyst can complete all of the appropriate business analysis activities so the project will go more smoothly, with less risk and less frustra- tion than if the requirements processes were rushed by management, the project man- ager, and the customer. "Select the requirements activities" means that the business analyst will need to determine what requirements activities are the most appropriate. The business analysis