Learn Critical Business Analysis Tools

29 April 2019 - 02 May 2019 (07:00 PM to 09:30 PM)

Critical BA Tools

29 April 2019 - 02 May 2019 (7.00pm to 9.30pm)


You will learn BA Tools and will be given access to our Attlasian Account and you will be able to practice for up to 1 month absolutely free. You will have access to Jira, Confluence and Balsamiq

Jira / Confluence tutorials

JIRA is a proprietary issue tracking tool, developed by Atlassian. The functionalities it provides makes it well suited to the iterative nature of the Agile epopular it is with Agile BA's. It’s the second most widely used requirements tool second only to Excel Originally a bug/issue tracking tool, it evolved into a project management tool with functions that allows teams to easily manage their issues throughout the entire life-cycle of a project. It is highly customizable, and can be tailored to fit any workflow you need. It is primarily used in software development as a way to manage and track development efforts. It supports any agile methodology, be it scrum, kanban, or your own unique flavor. From agile boards and backlogs to burndown charts and reports, you can plan, track, and manage all your agile software development projects from a single tool. A major benefit also, is the fact that it provides single source of truth and transparency as information on progress is readily available through the information radiators.


Confluence is a team collaboration and content management tool within the Atlassian product suit, it gives you the power to create anything and everything, from meeting notes, project plans, product requirements, technical specification, project artifacts and more. It also provides blogging functionalities and Includes multimedia and dynamic content. Connect people and ideas in one place, with transparency, openness and provide feedback in real-time as team discuss stumbling blocks and resolve problems. A major benefit also, is the fact that it provides single source of truth and platform for collaboration to its users, with regards to version control, updates, alerts, tasks assignment and information purposes. You can toggle easily between Confluence and Jira, as well as create and link issues or reference documents and artifacts.

Visio/Draw tutorials

As a BA the analysis of business processes typically includes the mapping of processes and sub-processes down to activity level. A typical business process model is a model of one or more business processes, and defines the ways in which operations are carried out to accomplish the intended objectives of an organization. The model is a great and effective way of capturing and translating information elicited from users in a visual form - both of the current As–as process and the propose To-be desired state, taking into account roles, responsibilities and standards . The process of modeling also throws up some possible omissions during requirements gathering. Modeling are different types and notations and there are various process mapping software out there that can be used to captures the flow of activities in visual forms – they include but not limited to:

  • Visio
  • Balsamiq
  • Sartdraw
  • Gliffy

With these tools formal functional specifications can be used to build prototypes that demonstrate how a proposed website for example will look as well as ease of navigation – thereby allowing users to try out development ideas rather than trying to decipher a functional written specification. Prototyping can also be used effectively by end users to describe and prove the need for requirements that developers may not have considered. Wireframes and mockups are commonly used in web and mobile developments.

The Benefits of Prototyping

• Obtain feedback from users in the formative stages of your project • If following a requirements specification compare the prototype for accuracy against the spec • Insight into the accuracy of initial project estimates eg whether deadlines and milestones can be successfully met • Prototyping can also avoid the great expense and difficulty of changing a finished software product