Tag: Business Analysis

  • Unlocking Success: Understanding the Different Types of Business Requirements

    Unlocking Success: Understanding the Different Types of Business Requirements

    Introduction

    When it comes to business analysis, requirements play a crucial role in defining the success of a project. They serve as the foundation for designing and developing the desired outcome. The International Institute of Business Analysis (IIBA) has identified various types of requirements that are essential for a project’s success. In this blog post, we will explore these different types of requirements and how they are modeled.

    Functional Requirements

    Functional requirements describe what the system or product must do to meet the needs of its users. These requirements specify the features, capabilities, and functionalities that are expected from the solution. They are typically documented using techniques such as use cases, user stories, or activity diagrams.

    For example, if you are developing a mobile banking application, functional requirements might include features like account balance inquiries, fund transfers, and bill payments. These requirements are crucial for ensuring that the solution meets the expectations of its users and delivers the intended functionality.

    Non-Functional Requirements

    While functional requirements focus on what the system does, non-functional requirements focus on how the system performs. These requirements outline the quality attributes and constraints of the solution, such as performance, security, reliability, and user experience.

    Non-functional requirements are often critical for the success of a project, as they define the overall user satisfaction and system performance. They are typically documented using techniques like quality attribute scenarios, performance benchmarks, or usability studies.

    Business Requirements

    Business requirements define the needs and objectives of the organization. They provide a high-level view of the desired outcomes and help align the project with the overall business strategy. Business requirements are often captured through interviews with key stakeholders, surveys, or workshops.

    For example, if a retail company wants to expand its operations to online sales, some of the business requirements might include increasing revenue, reaching a wider customer base, and improving customer satisfaction. By clearly defining these requirements, the project team can ensure that the solution supports the business goals.

    Conclusion

    Understanding and effectively managing requirements is essential for the success of any project. By recognizing the different types of requirements, such as functional, non-functional, and business requirements, project teams can develop solutions that meet the needs of the users and align with the overall business objectives. So, whether you are embarking on a new project or looking to enhance an existing one, make sure to give the due importance to requirements and their modeling for unlocking the path to success.

    Please note: That is an “agile” world that both functional and non-functional requirements are defined as User Stories

  • Why Choose the Better Business Analysis Institute for Your Business Analysis Training

    Why Choose the Better Business Analysis Institute for Your Business Analysis Training

    In the dynamic world of business, the role of a Business Analyst (BA) is pivotal. They bridge the gap between IT and business needs, ensuring that projects align with strategic goals. To excel in this role, comprehensive Business Analysis Training is essential. Among the myriad of options available, the Better Business Analysis Institute (BBA Institute) stands out as the premier choice. Here’s why:

    1. Comprehensive Curriculum: The BBA Institute offers a robust curriculum that covers all aspects of business analysis. From understanding business needs and requirements management to solution evaluation, the course ensures a holistic understanding of the BA role.
    2. Experienced Instructors: The BBA Institute boasts a team of seasoned professionals who bring real-world experience to the classroom. Their insights and practical examples enrich the learning experience, making the theoretical concepts more relatable.
    3. Flexible Learning Options: The BBA Institute understands the need for flexibility, especially for working professionals. They offer both online and in-person training options, allowing you to learn at your own pace and convenience.
    4. Certification Recognition: The BBA Institute’s certification is widely recognized in the industry. It adds significant value to your resume and increases your marketability in the job market.
    5. Interactive Learning Environment: The BBA Institute emphasizes interactive learning. Their courses include case studies, group discussions, and projects that simulate real business scenarios, fostering a deeper understanding of the subject matter.
    6. Post-training Support: Unlike many other institutes, the BBA Institute provides post-training support. This includes access to course materials, webinars, and forums where you can discuss your queries with peers and instructors.
    7. Value for Money: The BBA Institute’s courses are competitively priced, offering high-quality training at an affordable cost. They also offer corporate training packages, making it a cost-effective solution for organizations looking to upskill their teams.

    When compared to other training providers, the BBA Institute’s comprehensive curriculum, experienced instructors, flexible learning options, and post-training support make it a standout choice. Whether you’re an aspiring BA or a seasoned professional looking to upskill, the BBA Institute offers a training solution that’s tailored to your needs.

    In conclusion, the Better Business Analysis Institute is a leading provider of Business Analysis Training. Their commitment to quality education, practical learning, and ongoing support ensures that their students are well-equipped to excel in their roles as Business Analysts. Choose the BBA Institute for your Business Analysis Training and take the first step towards a successful BA career.

    Get your CBBA – Level 1 today for only $550 USD ($899 NZD)

    or Complete the Free Introduction to Business Analysis Course today

    #BATraining #BusinessAnalysisTraining

  • Another AI Diagramming tool for Business Analysts

    Another AI Diagramming tool for Business Analysts

    We have found another AI Diagramming tool for Business Analysts and it’s much more focused on UML.

    chatuml.com

  • AI Whiteboard for Business Analysts

    AI Whiteboard for Business Analysts

    Kia ora Everyone, Happy Thursday! Today we are going to talk about another exciting AI diagramming tool that is more like a MURAL, Miro style whiteboarding tool. Some of the feature like process flow still be a bit of work (alpha stage) but some of the other areas will take hours off your tasks.

    Jeda.ai is amazing and states that it is a “Generative Ai Online Whiteboard for Interstellar Visual Collaboration” which makes me think the name is play on the word “Jedi” and this thing can do some serious AI magic.

    You can sign up for free here https://go.jeda.ai/register and: “Experience Jeda.ai Online Whiteboard with generative AI for exceptional template analysis, diagram creation, and more. Claim 10,000 free Ai Karma tokens daily and access exclusive features to elevate your projects. Embrace the future of content creation with Jeda.ai!”

    So what does it do? We have been looking into the use case every Business Analysis could use this tool for. The list is long and includes:

    • Online whiteboard for brainstorming
    • AI Process Modelling
    • Strategic planning
    • Design Thinking

    Here is one of the examples we tried:

    We used the Ai Recipes to generate a go-to-market-strategy with the following inputs

    The output was the following diagram (with some label movement need):

    Not only is the content pretty damn cool (and i don’t need to format anything), I can now a share and work on this whiteboard with my team.

    I think this is one to have a serious play with and please flick me any insights you find out.

  • AI Diagramming Tool For Business Analysts

    AI Diagramming Tool For Business Analysts

    Today I found a pretty good AI diagraming tool which might save you time as a #businessanalyst or architect.

    The tool is called diagramgpt and provide by Eraser.io (linked to tool below)

    The prompt i used was “The process flow of a person buying a t-shirt from a local clothes store” – Entity Relationship Diagram

    Try it out here:

    https://www.eraser.io/diagramgpt

    Brought to you by the folks at Eraser

  • Applying for Business Analyst Jobs – What a candidate and hiring manager needs to know

    Applying for Business Analyst Jobs – What a candidate and hiring manager needs to know

    Are you looking to become a successful business analyst? Look no further! In this podcast episode, Benjamen Walsh from The Better Business Analysis Institute shares valuable insights on what to look for when hiring a business analyst and how to succeed in the job search process.

    Benjamen emphasises the importance of gaining experience and completing certified courses to move up to an intermediate level.

    Candidates should also tailor their CV and cover letter to the specific job and company they are applying for, and showcase their personality and connection with the company in their application.

    For hiring managers, Benjamen suggests having a structured interview process, including technical and culture fit interviews, and creating a job description specific to the level and job being hired for.

    So, if you’re looking to become a successful business analyst, take these tips to heart and start your journey today!

  • How Business Analysts Can Help Companies Survive a Recession

    How Business Analysts Can Help Companies Survive a Recession

    How Business Analysts Can Help Companies Survive a Recession

    The current financial climate has seen a recession not only in New Zealand but also overseas, leading to companies looking for ways to cut costs, restructure, and even merge to survive. Business analysts can play a crucial role in helping companies during this period by focusing on continuous improvement and business transformation.

    Continuous improvement involves applying process-level improvements to reduce waste in the organization. Business analysts can help by focusing on reducing waste at the process level, making processes more efficient, and providing clarity to senior leaders about the impact of cost-cutting measures. On the other hand, business transformation involves a top-down approach where a company reflects on its business model and unique value proposition (UVP). Business analysts can assist by reviewing the company’s UVP and identifying areas where fundamental changes can be made.

    During a recession, companies tend to focus on their UVP, which is what customers come to them for. This may result in turning off services that are not core to the business or not what makes them unique to their target customers. It’s important for businesses to be conservative with their spending and to look for ways to cut costs. However, this can be a difficult time for many people, and it’s important to remember that there are ways to help.

    Business analysts can use their skills and knowledge to advise friends and family who may be affected by the recession, helping them to identify new career opportunities and navigate the job market. By focusing on continuous improvement and business transformation, business analysts can help companies and individuals survive and thrive during a recession.

  • Free Business Analysis Templates

    Free Business Analysis Templates

    The BBAI template library gives business analysts everything they need to deliver professional, consistent work — from requirements gathering through to solution validation. All templates are free. Use them as-is or adapt them to your project context.

    Jump to section: Requirements · Analysis & Assessment · Stakeholder Management · Process & Workflow · Business Case & Planning · Testing & Quality · BA Project Management · Agile & Product


    Requirements Templates

    The most-used templates in a BA’s toolkit. Requirements templates help you capture, document, and manage what the business needs from a solution.

    Business Requirements Document (BRD)

    The BRD captures what the business needs to achieve, independent of how the solution will be built. Use at the start of a project to align stakeholders before solution design begins.

    SectionContent to Include
    1. Executive SummaryProblem statement, business opportunity, and recommended approach (1 page)
    2. Business ObjectivesSMART goals the solution must achieve, linked to strategic objectives
    3. Current StateAs-is process description, pain points, and root causes
    4. ScopeIn-scope processes, systems, and stakeholder groups. Explicit out-of-scope list.
    5. StakeholdersKey stakeholders, roles, and approval authorities
    6. Business RequirementsNumbered list: BR-001, BR-002… Each with priority (MoSCoW) and owner
    7. Assumptions & ConstraintsKnown limitations, dependencies, regulatory requirements
    8. Success CriteriaHow the business will measure whether the solution delivered value
    9. GlossaryBusiness terms and definitions used in this document

    Functional Requirements Specification (FRS)

    Translates business requirements into specific, testable functional behaviours. Used by development teams to understand what the system must do. Write this after the BRD is approved.

    FieldDescriptionExample
    FR-IDUnique reference numberFR-001
    TitleShort name for the requirementUser Login
    DescriptionWhat the system must doThe system shall allow registered users to log in using email and password
    SourceBusiness requirement it traces toBR-003
    PriorityMoSCoW classificationMust Have
    Acceptance CriteriaHow to confirm it worksGiven [context], When [action], Then [expected outcome]
    OwnerStakeholder responsibleProduct Owner
    StatusDraft / Approved / Implemented / TestedDraft

    Requirements Traceability Matrix (RTM)

    Maps each business requirement through to functional requirements, test cases, and implementation. Ensures nothing is missed and every requirement can be tested. Essential for projects with regulatory compliance requirements.

    BR-IDBusiness RequirementFR-IDFunctional RequirementTest Case IDTest StatusSign-off
    BR-001Users must authenticate securelyFR-001, FR-002Login, Password ResetTC-001, TC-002Pass
    BR-002[Requirement text][FR-IDs][FR titles][TC-IDs]Pending

    User Story Template

    Captures requirements from the user’s perspective in agile projects. Each story should be independently deliverable and testable. Use the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) to validate stories before sprint planning.

    FieldFormat / Example
    Story IDUS-001
    As a…[Type of user / role]
    I want to…[Goal or action]
    So that…[Business value or outcome]
    Acceptance CriteriaGiven [context], When [action], Then [result]. Add one row per criterion.
    Story Points[Effort estimate]
    PriorityMust Have / Should Have / Could Have
    Dependencies[Other story IDs]
    NotesEdge cases, exclusions, open questions

    Use Case Template

    Describes a system interaction from the actor’s perspective. Use cases are more detailed than user stories and are better suited to complex workflows or compliance-heavy projects.

    FieldContent
    Use Case IDUC-001
    TitleDescriptive name (verb + noun: “Submit Expense Claim”)
    Primary ActorWho initiates the use case
    Secondary ActorsOther systems or roles involved
    PreconditionsWhat must be true before this can start
    Main Success ScenarioStep-by-step numbered list of the happy path
    Alternative FlowsValid variations of the main flow (Alt-1, Alt-2…)
    Exception FlowsError conditions and how the system handles them
    PostconditionsSystem state after successful completion
    Business RulesRules that govern this use case (link to BR-IDs)

    Business Rules Template

    Documents the operational policies, regulations, and constraints that govern how the business works. Business rules are separate from functional requirements — they define the boundaries of acceptable system behaviour.

    Rule IDRule StatementCategorySourceImpactOwner
    BR-001All purchase orders above $10,000 must have two approvalsApprovalFinance Policy v3.1HighCFO
    BR-002[Write rule as: Entity must/shall/must not verb condition]Validation / Approval / Calculation / Restriction[Policy, regulation, or SME]High / Medium / Low[Name]

    Data Dictionary Template

    Defines every data element used in a system or process — its name, format, valid values, and business meaning. Essential for integration projects, data migration, and anywhere multiple systems exchange data.

    Field NameBusiness DefinitionData TypeFormatValid ValuesMandatory?Source System
    CustomerIDUnique identifier for a customer accountStringCUST-NNNNNNCUST-000001 to CUST-999999YesCRM
    [Field name][Plain English meaning]String / Integer / Date / Boolean / Decimal[Pattern or example][List or range]Yes / No[System name]

    Analysis & Assessment Templates

    Gap Analysis Template

    Compares the current state to the desired future state to identify what needs to change. Use early in a project to scope the work and justify investment.

    DimensionCurrent State (As-Is)Desired State (To-Be)GapPriorityRecommended Action
    ProcessManual data entry, 3-day cycleAutomated, same-day processingNo automation; manual errorsHighImplement workflow automation
    Technology[Current tools][Target tools][Difference]High / Med / Low[Action]
    People / Skills[Current capability][Required capability][Skills gap][Training / hiring]
    Data[Current data state][Required data state][Data gap][Migration / cleanse]

    Root Cause Analysis — 5 Whys Template

    Traces a problem back to its root cause by asking “why” repeatedly. Works best for process failures where human or system factors compound. Use before defining requirements so you solve the actual problem, not just the symptom.

    LevelQuestionAnswer
    Problem StatementWhat is the observable problem?[Describe the symptom clearly]
    Why 1Why does this problem occur?[First cause]
    Why 2Why does [Why 1 answer] happen?[Second cause]
    Why 3Why does [Why 2 answer] happen?[Third cause]
    Why 4Why does [Why 3 answer] happen?[Fourth cause]
    Why 5Why does [Why 4 answer] happen?[Root cause]
    Corrective ActionWhat addresses the root cause?[Recommended action]

    SWOT Analysis Template

    Evaluates a business, product, or initiative across four dimensions. Use in enterprise analysis, feasibility studies, and strategic planning workshops. Facilitating a SWOT session is a core BA skill — include it in your stakeholder workshop plan.

    Strengths (Internal, Positive)Weaknesses (Internal, Negative)
    What advantages does the organisation/product have?
    What does it do well?
    What unique resources does it have?
    What could be improved?
    What is done poorly?
    What should be avoided?
    Opportunities (External, Positive)Threats (External, Negative)
    What opportunities exist in the market?
    What trends could be exploited?
    What changes in technology/regulation help?
    What obstacles exist?
    What are competitors doing?
    What regulations or market shifts threaten success?

    Cost-Benefit Analysis Template

    Quantifies the financial case for a change initiative. Required for most business cases. Identify both tangible (measurable) and intangible (qualitative) costs and benefits.

    ItemTypeYear 1Year 2Year 3TotalNotes
    COSTS
    Software licencesOne-off$50,000$50,000CRM platform
    Implementation / developmentOne-off$80,000$80,000
    TrainingOne-off$15,000$15,000
    Ongoing maintenanceRecurring$10,000$10,000$10,000$30,000Per year
    Total Costs$155,000$10,000$10,000$175,000
    BENEFITS
    Labour savings (automation)Recurring$40,000$40,000$40,000$120,0002 FTE
    Revenue upliftRecurring$60,000$75,000$90,000$225,0005% conversion lift
    Total Benefits$100,000$115,000$130,000$345,000
    Net Benefit-$55,000$105,000$120,000$170,000ROI: 97%

    Risk Register Template

    IDRisk DescriptionCategoryLikelihood (1–5)Impact (1–5)ScoreResponse StrategyOwnerStatus
    R-001[What could go wrong]Technical / People / Process / External3412Mitigate / Accept / Transfer / Avoid[Name]Open

    Stakeholder Management Templates

    Stakeholder Register Template

    A living document that records every stakeholder involved in or affected by a change initiative. Build this at project kick-off and update it throughout delivery.

    NameRole / TitleOrganisationInterest in ProjectInfluence (H/M/L)Impact on Them (H/M/L)Engagement LevelCommunication PreferenceBA Notes
    [Name][Role][Dept/Org][What they care about]HMChampion / Supporter / Neutral / Critic / BlockerEmail weekly / Meeting bi-weekly[Key concerns, motivators]

    Power / Interest Stakeholder Matrix

    Maps stakeholders by their power to influence the project and their interest in its outcome. Determines your engagement strategy for each group.

    Low InterestHigh Interest
    High PowerKeep Satisfied
    Manage their concerns. Keep informed at a high level. Avoid surprises. Example: Executive sponsor who isn’t involved day-to-day.
    Manage Closely
    Engage actively. Involve in decisions. Regular detailed communication. Example: Project sponsor, key business owner.
    Low PowerMonitor
    Minimal effort. Keep on distribution list. Example: End users not yet in scope.
    Keep Informed
    Provide regular updates. Involve in workshops. Example: End users, subject matter experts.

    RACI Matrix Template

    Defines who is Responsible, Accountable, Consulted, and Informed for each activity or deliverable. Use to eliminate confusion about ownership and prevent decisions stalling. Every activity should have exactly one Accountable person.

    Activity / DeliverableBAProject ManagerProduct OwnerDeveloperBusiness SMEExecutive Sponsor
    Requirements ElicitationRCAICI
    BRD Sign-offRCCICA
    UAT PlanningACRCRI
    [Activity]

    Key: R = Responsible (does the work) · A = Accountable (owns the outcome, approves) · C = Consulted (input needed) · I = Informed (kept updated)

    Requirements Elicitation Interview Template

    Structure your stakeholder interviews to consistently capture requirements, pain points, and priorities. Adapt these questions to your project context.

    CategoryQuestions
    Context SettingCan you walk me through your current process?
    What does a typical day/week look like for you in this area?
    Pain PointsWhat are the biggest frustrations with how things work today?
    Where does the process break down most often?
    What takes longer than it should?
    RequirementsWhat would the ideal solution look like for you?
    What does the new system/process absolutely must do?
    What would be a nice-to-have but not essential?
    ConstraintsAre there any systems this must integrate with?
    Are there regulatory or policy requirements we must comply with?
    What timeline or budget constraints should we be aware of?
    SuccessHow will you know this project has been successful?
    What does “done” look like from your perspective?
    Wrap-upIs there anyone else I should speak to?
    Is there any documentation I should review?
    Is there anything I haven’t asked that’s important?

    Process & Workflow Templates

    SIPOC Template

    SIPOC maps a process at a high level before diving into detailed modelling. Use it at the start of any process improvement or requirements project to scope the work and align stakeholders on what the process actually is.

    SuppliersInputsProcess (High Level)OutputsCustomers
    Who provides the inputs?What materials, data, or information enter the process?5–7 high-level steps only (verb + noun: “Receive order”, “Validate data”)What does the process produce?Who receives the outputs?
    [Supplier 1]
    [Supplier 2]
    [Input 1]
    [Input 2]
    1. [Step]
    2. [Step]
    3. [Step]
    4. [Step]
    5. [Step]
    [Output 1]
    [Output 2]
    [Customer 1]
    [Customer 2]

    As-Is / To-Be Process Comparison Template

    StepAs-Is (Current)Pain PointTo-Be (Future)Change RequiredBenefit
    1[Current step description][What’s wrong with it][Improved step description]Process / Technology / People / Policy[Quantified benefit if possible]

    Business Case & Planning Templates

    Business Case Template

    SectionContent
    1. Executive SummaryProblem, proposed solution, key benefits, cost, recommendation. Max 1 page.
    2. Problem / OpportunityEvidence of the problem. Current cost of inaction. Strategic alignment.
    3. Options AnalysisAt least 3 options including “do nothing”. Pros/cons and costs for each.
    4. Recommended OptionWhich option and why. Risk-adjusted rationale.
    5. Financial SummaryCosts, benefits, NPV, ROI, payback period. Use the cost-benefit template above.
    6. Implementation PlanHigh-level timeline, milestones, resource requirements.
    7. RisksTop 5 risks with likelihood, impact, and mitigation. Reference risk register.
    8. RecommendationDecision requested from the approving authority.

    Project Scope Statement Template

    FieldContent
    Project Name
    Project Sponsor
    Business ObjectiveOne sentence: what the project must achieve for the business
    In ScopeBulleted list of what IS included
    Out of ScopeExplicit list of what is NOT included (prevents scope creep)
    DeliverablesTangible outputs the project will produce
    MilestonesKey dates and decision points
    ConstraintsFixed budget, deadline, technology, regulatory
    AssumptionsWhat you’re assuming to be true (if wrong, replan)
    DependenciesWhat this project depends on / what depends on it
    Approved by[Sponsor name and date]

    Testing & Quality Templates

    UAT Test Plan Template

    The BA typically owns UAT planning. This template ensures every business requirement has at least one test case and that the right stakeholders are doing the testing.

    TC-IDRequirement (BR/FR ID)Test ScenarioTest StepsTest DataExpected ResultActual ResultPass/FailTesterDate
    TC-001FR-001User logs in with valid credentials1. Navigate to login page
    2. Enter valid email
    3. Enter valid password
    4. Click Login
    Email: test@example.com
    Password: Test@123
    User lands on dashboard[Name]

    Defect Log Template

    Defect IDTC-IDDescriptionSteps to ReproduceSeverityPriorityAssigned ToStatusResolution
    DEF-001TC-003[What went wrong][How to reproduce it]Critical / High / Medium / Low1–4[Developer]Open / In Progress / Resolved / Closed[How it was fixed]

    BA Project Management Templates

    BA Meeting Minutes Template

    FieldContent
    Meeting Title[Project name] – [Meeting type: Requirements Workshop / Review / Sign-off]
    Date & Time
    Location / Platform
    Attendees[Name, Role] for each attendee
    Apologies
    Agenda Items Covered1. [Item] — [Summary of discussion] — [Decision reached]
    2. [Item] — [Summary] — [Decision]
    Decisions MadeList each decision clearly with decision owner
    Action Items[Action] | [Owner] | [Due date] | [Status]
    Open Issues / Parking LotItems raised but not resolved — carry to next meeting
    Next Meeting[Date, time, location]

    BA Status Report Template

    FieldContent
    Project / Initiative
    Reporting Period
    Overall Status🟢 On Track / 🟡 At Risk / 🔴 Off Track
    BA Activities This PeriodBulleted list of what was completed
    Planned Activities Next PeriodBulleted list of what’s coming
    Requirements StatusTotal / Approved / In Progress / Not Started
    Issues / Blockers[Issue description] | [Impact] | [Action needed] | [Owner]
    Risks[Risk] | [Likelihood] | [Impact] | [Mitigation status]
    Decisions NeededList of pending decisions with deadlines

    Agile, Product & Design Templates

    These templates are useful for BAs working in agile teams, product discovery, or design-led projects.

    TemplateLink
    Agile RetrospectiveMiro Template
    Business Model CanvasMiro Template
    Continuous Product DiscoveryMiro Template
    Customer DiscoveryMiro Template
    Customer Journey MapMiro Template
    Design Sprint (5-Day)Miro Template
    Design Thinking ProcessMiro Template
    Empathy MapMiro Template
    Feature Prioritization MatrixMiro Template
    Impact MappingMiro Template
    Impact-Effort MatrixMiro Template
    Jobs To Be Done (JTBD)Miro Template
    Kano ModelMiro Template
    Lean CanvasMiro Template
    Mind MapMiro Template
    Minimum Viable Product (MVP)Miro Template
    Persona TemplateMiro Template
    Problem Statement TemplateMiro Template
    Product Backlog TemplateMiro Template
    Product Requirements Document (PRD)Miro Template
    Product RoadmapMiro Template
    Project CharterMiro Template
    Scrum FrameworkMiro Template
    Sprint RetrospectiveMiro Template
    SWOT Analysis (Visual)Miro Template
    User PersonaMiro Template
    User Story MapMiro Template
    Value Proposition CanvasMiro Template
    KPI DashboardMiro Template
    4P+ Business ModelBBAI Framework

    Get Certified in Business Analysis

    Templates are only as useful as the analyst using them. The Certified Better Business Analyst (CBBA) course teaches you how to apply every template above in real delivery contexts — not just fill in the boxes, but understand what questions to ask, when to use which tool, and how to turn completed templates into decisions and action.

    ✓ 80+ lessons covering the full BBAI Framework
    ✓ Practical assignments using real project scenarios
    ✓ Verifiable digital certificate
    ✓ Self-paced — complete in 4–8 weeks

    Start free → Try the Introduction to Business Analysis course — no payment required.

    Get certified → Full CBBA certification. NZD $499.

  • Project Management Software (for Business Analysts)

    Project Management Software (for Business Analysts)

    When you read the title of this blog post you might be tempted to ask the question – Isn’t Project management software for Project Managers? Well, the short answer is yes, but as Business Analysts are a large part of managing the scope of work through the delivery journey (which is primarily focused on delivering requirements) we should have the skills to understand stand up and run the delivery-focused project management software.

    Business Analysts may use project management software such as Jira, Trello, Asana, MS Project, and Excel to manage project tasks, track progress, and collaborate with team members. Again, yes this should be owned by the Project Manager or sometimes the Scrum master but in many situations you will find that Business Analyst is creating, updating or managing the content within these tools.

    I would like to spend some time talking about 3 of these tools that focus on the Delivery & Requirement Managements sides of things:

    • Excel
    • Jira
    • Azure DevOps

    As a Business Analyst, your Requirements Traceability Matrix should be managed within one of these 3 tools (or more than) or something very similar.

    Excel

    Excel is a great tool for any business professional to learn however as a Business Analyst you should have advanced Excel knowledge.

    Creating a Requirement Traceability Matrix in Excel is a simple task however there is no UX or system joins, dependencies or constraints between the Objectives, Epics and User Stories.

    1. Define the requirements: Business Analysts can use Excel to capture and organize the requirements in a structured format. This may include columns for the requirement ID, description, priority, status, and any other relevant information. You may also use Excel to create a traceability matrix that maps the requirements to the project objectives.
    2. Categorize the requirements: To make it easier to manage and prioritize requirements, BAs may use Excel to categorize them based on their functional or non-functional attributes. This may include creating columns for the requirement type, category, and sub-category.
    3. Track changes and updates: Requirements are likely to change throughout the project lifecycle, so BAs can use Excel to track changes and updates to the requirements. This may include creating a separate column for change history, where BAs can document any changes made to the requirements and the reason for the change.
    4. Use formulas and filters: Excel allows BAs to use formulas and filters to quickly analyze and manipulate data. For example, BAs can use formulas to calculate the total number of requirements, or use filters to sort requirements by priority, status, or category.
    5. Generate reports: Finally, BAs can use Excel to generate reports on the requirements, such as a requirements traceability matrix or a requirements status report. These reports can help keep stakeholders informed of the progress of the project and ensure

    Jira

    Jira is a popular project management tool that can be used to manage requirements for software development projects

    1. Create a project in Jira: The first step is to create a new project in Jira, or use an existing one. Make sure to select the appropriate project type based on your needs.
    2. Define requirements: Once the project is created, define the requirements that need to be tracked. You can create a new issue type called “requirement” or use an existing one like “user story” or “feature” to represent the requirements.
    3. Create issues: Create an issue for each requirement and enter a summary and description that clearly explains what the requirement is and what it should accomplish. You can also add labels, attachments, and comments to provide additional context.
    4. Link requirements: To link related requirements, use the “link” feature in Jira to establish relationships between issues. For example, you can link a “parent” requirement to several “child” requirements that are necessary to fulfill the parent requirement.
    5. Prioritise requirements: Use Jira’s priority system to prioritise requirements based on their importance and impact. You can assign a priority level to each requirement, such as “critical”, “high”, “medium”, or “low”.
    6. Assign requirements: Assign requirements to team members responsible for implementing them. You can assign issues to specific individuals or to a team, and set due dates to ensure timely completion.
    7. Track progress: Use Jira’s reporting features to track progress on requirements. You can generate reports to show the status of individual requirements, the progress of the entire project, and any issues that need attention.

    Azure DevOps

    Azure DevOps is a cloud-based project management tool that can be used to manage requirements for software development projects.

    1. Create a project in Azure DevOps: The first step is to create a new project in Azure DevOps or use an existing one. Make sure to select the appropriate project type based on your needs.
    2. Define requirements: Once the project is created, define the requirements that need to be tracked. You can create a new work item type called “requirement” or use an existing one like “user story” or “feature” to represent the requirements.
    3. Create work items: Create a work item for each requirement and enter a title and description that clearly explains what the requirement is and what it should accomplish. You can also add labels, attachments, and comments to provide additional context.
    4. Link requirements: To link related requirements, use the “link” feature in Azure DevOps to establish relationships between work items. For example, you can link a “parent” requirement to several “child” requirements that are necessary to fulfill the parent requirement.
    5. Prioritise requirements: Use Azure DevOps’ priority system to prioritise requirements based on their importance and impact. You can assign a priority level to each requirement, such as “critical”, “high”, “medium”, or “low”.
    6. Assign requirements: Assign requirements to team members responsible for implementing them. You can assign work items to specific individuals or to a team, and set due dates to ensure timely completion.
    7. Track progress: Use Azure DevOps’ reporting features to track progress on requirements. You can generate reports to show the status of individual requirements, the progress of the entire project, and any issues that need attention.

    There a number of specialist requirements management tools, such as IBM Rational DOORS or Jama Connect however in our opinion the above 3 tools are your best option.

  • Building a Framework for Living – Building Programmes from Strategy

    Building a Framework for Living – Building Programmes from Strategy

    We have defined our strategic objectives and now we need to look at how we are going to get after them.

    A lot of big businesses have a project management office that manages the programme of work for the year and have project managers, business analysis and solution architects that collectively work on a project to complete a piece of work.

    As far as a project owner and/or sponsor is concerned this is a great model and they can define their requirement and get a solution implemented through the solution delivery lifecycle.

    What is sometimes forgotten when you work on projects is that generally your project is part of a greater programme and what is more commonly missed is that those programmes exist to help achieve a strategic objective.

    With the structure of corporate being quite hierarchical with multiple department heads wanting to get their project funded the programme of work can get messy very quickly. Linking the Strategy objectives to each programme and then project can help prioritise what is important and what will give the business the biggest bang for buck!

    In order to keep programme planning simple I am going to take our example from chapter 4 – Just Law and I am going to work down from the Strategic objectives. Be well aware that most companies’ programmes of work are already in flight from the year before and strategic objectives are hardly even linked or used to prioritise one programme against another – this is changing however!

    In the case of  Just Law we have our 3 strategic objectives which we examined in more detail. To meet SO1 John firstly needs to work out  how he plans to get more clients in the door.

    For S02 John’s needs a change project to reduce steps in his current sales and purchase management process and finally for S03 johns needs to have a small recruitment project to find and hire the right lawyer.

    As I have been involved in many projects I would go ahead and state that John will have a programme consisting of at least 3 projects: 1. Investigate the options for increasing client number and implement, Implement a streamline sales and purchase process and recruit a lawyer.

    Seeing as John wants to increase revenue this year through client number he will use a reserve fund to hire a business analyst who has recruitment skills to help him get after this change programme.