Monitor Solution Design and Planning
As the technical team derives the solution design, the BA must learn enough about the implications of that design to ensure that it supports the requirements well. For example, the BA might:
- Review user classes to ensure that all of the solution functions, uses, and end users have been accounted for.
- Review the developers' functions and feature list for completeness.
- Map the documented requirements (both functional and Quality of Service) onto the elements of the system design to ensure complete coverage.
When the technical team defines its phasing plan (which identifies the order in which requirements will be addressed and functionalities designed and built) for incremental development, the BA must ensure that the plan supports the stakeholders' needs. If the plan calls for features to be delivered in a certain order, the BA should ensure that the planned order and delivery dates would be useful to the business stakeholders. The BA should also ensure that the phasing plan provides opportunities for any needed prototyping or validation during the project.
Tracing the requirements to the design is a good way to ensure complete coverage, and it lays the foundation for maintaining traceability throughout the project. The traceability information must be captured and recorded as the designs are being done, as trying to derive the traceability after the fact is difficult, if not impossible.
Finally, as the solution is being designed and built, the BA may identify business process improvements that are unrelated to the solution but that would be beneficial. This is especially likely where those processes will be affected when the solution is implemented.
Validate the Final Solution
As each deliverable of the project becomes available, the BA must ensure that appropriate validations take place to ensure that those deliverables satisfy the requirements and can be used by the intended end users.
- System testing looks at the final system to determine if the requirements have been satisfied. System integration testing refers to testing the final solution to ensure that it can coexist and integrate with existing systems and databases. Many organizations have an independent testing group whose main responsibility is to prepare for and perform these tests. When that is the case, the BA will usually review the test plans and the test results, and at times, the BA may help with the testing. However, in organizations that don't have testing groups the entire responsibility falls to the BA.
- Operations testing involves testing the final solution to ensure that it can be installed and run without an adverse effect on the other existing systems. If the computer operations group takes responsibility for this testing, then the BA will usually review the test plans and the test results. But if this testing is necessary and no one takes responsibility for it, then the entire responsibility for this testing falls to the BA.
- Acceptance testing ensures that the business need and user's needs have been fully satisfied. If the customer takes responsibility for this testing, then the BA will usually review the test plans and the test results. Otherwise, the entire responsibility for this testing falls to the BA.
Assess Other Solution Options
The BA should collaborate with a variety of people on the project as the solution is being put together. In all cases, expect the experts in each area to be making good choices. The BA's role in the collaboration is merely to serve as the business stakeholders' advocate and assure that their needs will ultimately be met.
Although the technical team takes the lead in evaluating and deciding on the technologies that could be employed to build the solution, the BA should remain involved. This is because every technical choice has the potential to cause limitations in the final solution that will be noticeable to the users. So, the BA must learn enough about the effects of the team's technical choices to ensure that they actually do support satisfying the requirements, and ultimately, the business needs.
When the plan involves purchasing or leasing (as opposed to internally developing) a solution, the BA may take the lead in choosing the solution. But even if someone else has primary responsibility for this, the BA will still remain closely involved. The BA ensures that any RFP (request for proposal) or RFQ (request for quote) accurately translates the requirements. The BA should also verify that the proposals received will fully meet the business need. And, when the solution is finally received, the BA ensures that it is adequately tested to be sure that is actually satisfies the requirements.
Support Implementation of the Solution
In some organizations, an operations team takes the lead in implementation, but often the BA is responsible. In either case, the BA must remain involved to ensure that implementation and any necessary conversion meets the needs of the users.
The BA ensures that any necessary installation planning is done, and that the appropriate technical experts review that plan for correctness. This could be as simple as ensuring there is enough disk space for the new software, or as complex as replacing entire computer systems with new ones.
Conversion is almost always an issue. Since the solution is most likely changing some attribute of the business process, there will probably be data conversion; there may also be other kinds of conversions to be done. Planning for these includes identifying the rules for handling the inevitable problems that will be found.
Finally, the plan to the final cutover to the solution must be well thought out. When should it happen? Will there be downtime involved? If so, how much is acceptable? An important, but often overlooked item is the "backout" plan. If the cutover fails, what must be done so the business can resume working with the old system? If there is significant data conversion or other changes, this can be a difficult problem.
Communicate the Solution Impacts
The responsibility of communicating the impact of the final solutions is assigned to different people in different organizations. In any case, the BA must still remain involved. Before the new solution is implemented, the BA should work with the business stakeholders to ensure that they are ready for it by:
- Ensuring that everyone who needs to know about the implementation has the information they need, when they need it, before implementation
- Setting the expectations of users and other stakeholders about how the change will affect them and the business process
- Making sure that any needed training and help is available to the users in a timely manner
After the implementation is complete, the BA collaborates with the appropriate people to report on the implementation. This reporting provides pertinent information to all the parties who need to know that the implementation took place, and if there were problems. A key item is the business impact that the change had. Since the project was undertaken to improve a business process, the actual impact on the business process is of major concern.
Perform Post-Implementation Review and Assessment
The final validation occurs after rollout of the solution is complete. This activity, also known as "Lessons Learned," is designed to help the organization learn from each project, supporting continuous process improvement.
You need to capture these successes, identify why they happened on this project, and determine what can be done on future projects to make them routine. The parts of this project that worked particularly well represent opportunities for future projects.
By the same token, if there were things on this project that were problematic, they also represent opportunities for improvement. You need to capture these issues, identify why they happened on this project, and determine what can be done on future projects to avoid them.
The Lessons Learned review is one of the most potent mechanisms for organizational learning and continuous improvement, as long as you actually use what you learned in future projects.
Solution assessment includes all the activities that the BA collaborates in to ensure that the technical and other decisions being made by the development team result in meeting the needs of the business and users. These activities include design decisions, phasing for incremental development, maintaining the traceability matrix, choosing technologies, procuring solutions, and ensuring usability.
Jill Liles is the Senior Product Marketing Manager at Global Knowledge http://www.globalknowledge, where she primarily focuses on marketing activities for Cisco training courses. She also coordinates all marketing for Canada. In her spare time she volunteers with her local Susan G. Komen Foundation affiliate and crafts jewelry. This article draws from Global Knowledge's Requirements Development and Management course.
Copyright © Global Knowledge Training LLC. All rights reserved