• Once the requirements document is approved and signed-off, assist the team with the next step – System Design and Test Script/Test Case development work.
     • Be prepared to answer questions regarding the requirements.
• Take the role as liaison between the user community and the technical team.
     • The BA is the communication broker between the users and the IT team. As an ambassador of business and functional knowledge, you must be able to convey the business requirements clearly to both the Developers and the Quality Assurance Analyst.
• Participate in Change Management Board Meetings.
     • Document and track all the changes taking place.
• Participate in User Acceptance Testing (UAT).
     • In many cases, BAs don’t get involved in UAT sessions. However, from my experience, BAs must be prepared to play an important role in UAT to address the user testing phase.

Remember, Business Analysts do not merely document business requirements.  They also serve as liaisons and communication brokers between the technical team and the user community. Doing things right from the beginning will reduce the likelihood of making wrong steps during project development.

We wish luck to all the Business Analysts out there. Thanks for taking the time to read our blog entries.

• Gathering Business Requirements
     • During your first meeting with business users, gather the High-Level Requirements.
     • Always keep your discussions within scope of the project.
     • If any requirements are out of scope, document them for future enhancements.
     • Diligent users seeking to do their jobs right typically want everything. But remember not all the requirements are critical to business – some could be just ‘nice to have.’ Negotiate with business users and other stakeholders to identify the requirements that will add the most value to the business.
     • If you receive conflicting requirements from different business users, call a meeting to address the gaps. Get the users to justify and prioritize the requirements based on importance and criticality to business.
     • Never offer technical solutions for current issues on the spot, but rather document all issues and take them to your technical team for discussion. Then come up with solutions that can be shared with the business users.
     • Document all the points and send them to the business users after the meeting. This will ensure that the points are correctly conceived, and, if any are wrongly captured, that the business users will have the opportunity to correct them.

• Leading Joint Application Development (JAD) sessions
     • Realize that it will be next to impossible to get developers and other team members, as well as other stakeholders, together all at once to sit in a room and brainstorm about system design.
     • Be willing and able to play the lead role in administering, managing and facilitating JAD sessions.

• Documenting the Business Requirements
     • When you develop the business requirements document, spell out the details clearly, without any ambiguity or vague points. Use simple words to describe the requirements.
     • Present the requirements with diagrams, flow charts or pictures. Remember, “a picture is worth 1,000 words!”
     • For effectiveness, use Use Case or UML diagrams to present the details.
     • Use MS Visio to present the workflow models or business processes clearly.
     • Provide both ‘AS-IS’ and ‘TO-BE’ models, so that business users can compare and understand the differences.

In our next blog entry, we will wrap up this series with some tips for the agile Business Analyst during the stages that follow the documentation of business requirements.