Brolly Academy | Business Analysis
Business Analyst Projects
20 Ideas With Deliverables and Resume Lines (2026)
20 business analyst project ideas from beginner to advanced, across banking, e-commerce, healthcare, HR, logistics and ed-tech. Each one comes with a problem statement, the deliverables to build, tools, steps and a ready resume line, plus how to present your projects in a portfolio and an interview.
20 business analyst projects for 2026 in banking, e-commerce, healthcare and more, with deliverables, tools, steps and resume lines, plus portfolio tips.
By Brolly Academy Team · Brolly Academy · Updated 22 October 2026
Table of Contents
1. What is a business analyst project?
2. Why projects matter for business analyst jobs
3. What every business analyst project should include
4. How to choose the right project for you
5. Beginner business analyst projects (1 to 7)
6. Intermediate business analyst projects (8 to 14)
7. Advanced business analyst projects (15 to 20)
8. Free public datasets for data-heavy projects
9. Example: one project done end to end
10. How to present business analyst projects in a portfolio
11. How to explain a business analyst project in an interview
12. How to write projects on your resume
Quick answer
A business analyst project is a piece of work where you take a business problem, understand it, and turn it into clear documents that a team can build and test from, such as a BRD, user stories, process maps, wireframes and test cases. For a fresher or career switcher, two or three well-documented projects are the strongest proof that you can do the job. They give recruiters something real to read and give you real stories to tell in interviews.
- Start with one beginner project that covers the full cycle: problem, stakeholders, requirements, AS-IS and TO-BE process maps, user stories and test cases
- Add one data project with Excel, SQL or Power BI so you can show you work with numbers
- Pick domains that hire BAs, such as banking, e-commerce and healthcare
- Publish your work as PDFs in Google Drive, a Notion page or a GitHub repository
- Write each project as one resume line with the problem, what you built and the outcome
Key takeaways
- A BA project is judged on the quality of its documents and thinking, not on code.
- Every project should follow the same simple chain: problem, stakeholders, requirements, process, design, testing.
- Depth beats volume. One complete project with a BRD, process maps, user stories and UAT cases says more than five one-page summaries.
- Mix one process-focused project with one data-focused project to cover both sides of BA hiring.
- Practise explaining each project in two minutes using a simple structure: situation, task, action, result.
1. What is a business analyst project?
Short answer: A business analyst project is a structured case where you study how a business works today, find what is going wrong or missing, and document a better way that developers, testers and managers can act on.
In a real job, a BA project usually means one change initiative. A bank wants customers to open accounts online. A hospital wants to cut waiting time at discharge. An online store wants fewer returns. The BA sits between the business and the delivery team. You talk to the people affected, write down what they need, draw how the process works, and check that the final solution actually solves the problem.
For a learner, a portfolio project copies that same flow on a smaller scale. You do not need a real client. You can pick a real company you know as a customer, imagine a realistic problem, and play every role yourself: the stakeholder, the BA and the tester.
IIBA's BABOK Guide is the global reference for business analysis practice. It is currently in version 3 and defines six core knowledge areas, covering skills, deliverables and techniques (IIBA, October 2026). A good portfolio project touches most of them: planning your approach, eliciting needs, analysing the current and future state, documenting requirements and evaluating the solution.
2. Why projects matter for business analyst jobs
Short answer: Projects prove you can do the work. They turn a resume full of skill words into evidence, and they give you concrete examples to talk about in every interview round.
Here is why projects carry so much weight for BA roles:
- BA work is hard to judge from a degree. Any graduate can apply. A sample BRD or a clean process map shows a hiring manager how you think and write.
- Interviewers ask about projects first. "Walk me through a project you worked on" is one of the most common BA interview questions. With a project ready, you answer with facts instead of theory.
- They fill the experience gap. Freshers and career switchers often hear "we need experience". A documented project is the closest thing to experience you can build on your own.
- They show domain interest. A banking project tells a bank recruiter you already understand KYC, loans or payments.
- They build your tool skills. You learn Jira, Visio, draw.io, Figma, Excel, SQL or Power BI by using them for a purpose, not by watching videos.
If you also want supervised work experience, our guide on business analyst internships explains how to get supervised, real-world exposure. Projects and internships work well together: a project gets you the internship, and the internship gives you bigger projects.
3. What every business analyst project should include
Short answer: A complete BA project includes a problem statement, a stakeholder list, requirements (BRD or user stories), AS-IS and TO-BE process maps, wireframes where a screen is involved, acceptance criteria and UAT test cases. Data projects add SQL queries or a dashboard.
You do not need every document for every project. But you should know what each one is and when to use it.
For process maps, use BPMN, the standard notation from the Object Management Group. The BPMN specification page lists version 2.0.2 as the latest formal version, published in January 2014 (OMG, October 2026). Most diagram tools support it.
For user stories, check each one against the INVEST checklist. The Agile Alliance glossary describes a good story as independent, negotiable, valuable, estimable, small and testable (Agile Alliance, October 2026).
4. How to choose the right project for you
Short answer: Match the project to your level and your target domain. Beginners should pick a familiar process with a clear user. Intermediate learners should add detailed requirements and data. Advanced learners should add business cases, integrations and measurable outcomes.
Ask yourself three questions before you start:
- Which industry do I want to work in? If you are applying to banks or fintech companies, pick banking projects. If you come from a hospital or pharmacy background, healthcare projects let you use what you already know.
- What is my current level? Be honest. A clean beginner project is better than a confusing advanced one.
- What gap does my resume have? If you have no data skills on paper, add a data project. If you have only dashboards, add a requirements project.
Here are all 20 projects in this guide at a glance:
All company situations below are practice scenarios. Use them as starting points and make them your own.
5. Beginner business analyst projects (1 to 7)
Short answer: Beginner projects use a simple, familiar process with one main user. Focus on a clear problem statement, AS-IS and TO-BE process maps, 8 to 15 user stories, a few wireframes and basic UAT cases.
Project 1: Online order returns and refunds process (E-commerce)
- Problem: Customers of an online fashion store complain that returns take too long and they cannot see where their refund is. Support teams spend hours answering "where is my refund?" calls.
- Deliverables: Problem statement, stakeholder map (customer, support agent, warehouse, finance), AS-IS and TO-BE process maps, 10 to 12 user stories with acceptance criteria, a refund status wireframe, 8 UAT test cases.
- Tools: draw.io or Lucidchart, Figma or Balsamiq, Google Docs, Jira free plan or a spreadsheet backlog.
- Steps: Write the problem. List stakeholders and what each wants. Map today's return flow from request to refund. Mark delays and manual handoffs. Design a TO-BE flow with self-service return requests and status updates. Write user stories. Sketch the status screen. Write test cases for each story.
- Resume line: Mapped AS-IS and TO-BE returns process for an e-commerce case study, identified manual handoffs and wrote 12 user stories and 8 UAT cases for a self-service refund tracker.
Project 2: Digital savings account opening (Banking)
- Problem: A bank's branch-based account opening takes several visits. The bank wants customers to open a savings account fully on mobile, with digital KYC.
- Deliverables: BRD, AS-IS (branch) and TO-BE (mobile) process maps, use case diagram, user stories for each screen, wireframes for the onboarding flow, list of business rules (age, documents, minimum balance), UAT cases.
- Tools: MS Visio or draw.io, Figma, Google Docs or Word, Excel for the business rules table.
- Steps: Define scope (savings account only, resident individuals). Map the branch process. Design a mobile flow: details, document upload, verification, account creation. Document business rules and exceptions, such as a failed document check. Write the BRD. Draw the use case diagram. Create wireframes and test cases.
- Resume line: Wrote a BRD and use case model for a digital savings account opening journey, covering KYC steps, business rules and exception flows, with wireframes and UAT scenarios.
Project 3: Clinic appointment booking system (Healthcare)
- Problem: A multi-doctor clinic takes bookings by phone. Patients wait on hold, double bookings happen, and no-shows waste doctor time.
- Deliverables: Stakeholder map (patient, receptionist, doctor, clinic manager), user personas, user stories, wireframes for booking and reminders, non-functional requirements (availability, data privacy), UAT cases.
- Tools: Figma or Balsamiq, Lucidchart, Google Docs.
- Steps: Interview two or three friends or family members about their last clinic visit. Write personas. Map the phone booking process. Design an online booking flow with reminders and easy cancellation. Write stories and acceptance criteria. Add privacy requirements for patient data. Test the flow on paper with one person.
- Resume line: Designed requirements and wireframes for a clinic appointment booking system, including personas, 14 user stories, reminder rules and patient data privacy requirements.
Project 4: Employee leave management system (HR)
- Problem: A 200-person company tracks leave in emails and spreadsheets. Managers approve leave without seeing team calendars, and HR spends days reconciling balances.
- Deliverables: BRD, AS-IS and TO-BE leave approval flows, user stories for employee, manager and HR admin, business rules (leave types, carry forward, approvals), wireframes, UAT cases.
- Tools: draw.io, Excel, Jira or Trello, Google Docs.
- Steps: List leave types and policies (make realistic assumptions and state them). Map the email-based flow. Design a TO-BE flow with automatic balance checks and a team calendar. Write stories for each role. Build a business rules table. Create test cases for edge cases, such as applying for more leave than the balance.
- Resume line: Documented requirements for an HR leave management system with role-based user stories, a leave policy rules table and UAT cases for approval and balance edge cases.
Project 5: Course enrolment and fee payment (Ed-tech)
- Problem: An online learning platform loses learners between "view course" and "payment". Enrolment needs too many steps and offers few payment options.
- Deliverables: User journey map, AS-IS and TO-BE enrolment flows, user stories, wireframes for course page, checkout and confirmation, acceptance criteria, UAT cases.
- Tools: Figma, Miro or FigJam for the journey map, Google Docs.
- Steps: Go through the enrolment flow of two real learning platforms as a customer. Note every step and pain point. Build a journey map. Design a shorter TO-BE flow. Write stories covering guest checkout, payment failure and confirmation email. Create wireframes and test cases.
- Resume line: Built a user journey map and redesigned the enrolment and payment flow for an ed-tech case study, writing user stories, wireframes and acceptance criteria to reduce checkout steps.
Project 6: Courier delivery complaint handling (Logistics)
- Problem: A courier company receives complaints through calls, email and social media. There is no single ticket, so complaints get lost and customers repeat themselves.
- Deliverables: AS-IS and TO-BE complaint process maps in BPMN, gap analysis, complaint categories and priority rules, user stories for a ticketing system, a simple reporting requirement list.
- Tools: draw.io or Visio, Excel, Google Docs.
- Steps: List complaint channels and types (late delivery, damaged parcel, wrong address). Map how each is handled today. Identify gaps such as no tracking ID on tickets. Design one TO-BE flow with a single ticket and escalation rules. Write a gap analysis table and stories.
- Resume line: Created BPMN AS-IS and TO-BE maps and a gap analysis for a courier complaint process, defining complaint categories, priority rules and escalation requirements.
Project 7: Retail sales dashboard in Excel (E-commerce)
- Problem: The owner of an online gift store wants to know which products, countries and months drive sales, and which customers buy repeatedly.
- Deliverables: Business questions list, data dictionary, cleaned dataset, Excel pivot tables and charts, a one-page dashboard, a short insight summary with three recommendations.
- Tools: Excel (Power Query, pivot tables, charts). Dataset: the Online Retail dataset from the UCI Machine Learning Repository (see section 8).
- Steps: Write five business questions first. Download the data. Remove cancelled orders and blank customer IDs, and note what you removed. Build pivots for sales by month, product and country. Create a dashboard. Write insights in plain language with one recommendation per insight.
- Resume line: Analysed a public retail transactions dataset in Excel, cleaned the data, built a sales dashboard by product, month and country, and presented three business recommendations.
6. Intermediate business analyst projects (8 to 14)
Short answer: Intermediate projects add detailed functional requirements, an RTM, integrations with other systems, SQL or dashboards, and more stakeholders with competing needs.
Project 8: Personal loan origination system (Banking)
- Problem: A bank's personal loan applications move through email between sales, credit and operations. Approvals are slow and applicants get no status updates.
- Deliverables: BRD and FRD, AS-IS and TO-BE loan journey maps, use case diagram, business rules for eligibility and documents, RTM, status notification requirements, UAT test pack.
- Tools: Visio or Lucidchart, Word, Excel for the RTM, Jira for the backlog.
- Steps: Map the journey from lead to disbursement. List stakeholders and their goals (sales wants speed, credit wants risk control). Define eligibility rules as a table. Write functional requirements by stage: application, document check, credit decision, sanction, disbursement. Add non-functional needs such as audit trail. Build the RTM and test cases.
- Resume line: Wrote a BRD, FRD and RTM for a personal loan origination system covering application to disbursement, eligibility rules, status notifications and a UAT test pack.
Project 9: Cart abandonment analysis with SQL (E-commerce)
- Problem: An online store sees many users add products to the cart but leave without paying. Management wants to know where users drop off and what to fix.
- Deliverables: Business questions, a simple data model (users, sessions, cart events, orders), SQL queries for the funnel, a funnel chart, root-cause hypotheses, requirements for two fixes (for example guest checkout and saved carts).
- Tools: MySQL or PostgreSQL (free), Excel or Power BI for charts, Google Docs.
- Steps: Create sample tables with realistic test data, or adapt a public e-commerce dataset. Write queries for each funnel step: product view, add to cart, checkout start, payment, order. Calculate drop-off at each stage. List possible causes. Turn the top two causes into user stories with acceptance criteria.
- Resume line: Built a checkout funnel analysis using SQL on sample e-commerce data, identified the largest drop-off stage and wrote requirements for guest checkout and saved carts.
Project 10: Hospital discharge and billing process (Healthcare)
- Problem: Patients in a private hospital wait hours on discharge day while bills, pharmacy returns and insurance approvals are cleared one after another.
- Deliverables: Swimlane AS-IS map (ward, pharmacy, billing, insurance desk, patient), wait-time analysis using assumed timings, TO-BE map with parallel steps, gap analysis, requirements for a discharge tracker screen, UAT cases.
- Tools: Visio or Lucidchart, Excel, Figma.
- Steps: Map every handoff from "doctor approves discharge" to "patient leaves". Note which steps wait for others. Redesign so billing, pharmacy and insurance work in parallel with a shared status tracker. Write requirements and a wireframe for the tracker. Add test cases.
- Resume line: Analysed a hospital discharge process with swimlane maps, redesigned it for parallel processing and wrote requirements and wireframes for a shared discharge tracker.
Project 11: Employee onboarding workflow (HR)
- Problem: New joiners at an IT services company wait for laptops, email IDs and access. HR, IT and admin each work from their own checklist.
- Deliverables: Stakeholder RACI, AS-IS and TO-BE onboarding flows, epics and user stories in Jira, a sprint plan for the first release, acceptance criteria, a definition of done.
- Tools: Jira (free plan), Confluence or Notion, draw.io.
- Steps: List every onboarding task and owner. Build a RACI (responsible, accountable, consulted, informed). Map the current flow and its waiting points. Design an automated TO-BE flow triggered when an offer is accepted. Create epics, stories and a two-sprint plan in Jira. Export screenshots for your portfolio.
- Resume line: Set up a Jira backlog with epics, user stories and a two-sprint release plan for an automated employee onboarding workflow, supported by a RACI and TO-BE process map.
Project 12: Warehouse inventory management (Logistics)
- Problem: A regional distributor runs stock counts on paper. The sales team promises stock that is not there, and expired goods pile up.
- Deliverables: BRD, AS-IS and TO-BE inbound and outbound flows, data requirements (item, batch, expiry, location), integration requirements with the order system, reorder rules, reporting requirements, UAT cases.
- Tools: Visio, Excel, Word, Lucidchart for a simple entity diagram.
- Steps: Map receiving, storage, picking and dispatch. Define what data each step needs. Write rules for reorder levels and first-expiry-first-out picking. Describe what the inventory system must send to and receive from the order system. List reports the warehouse manager needs. Write test cases.
- Resume line: Documented requirements for a warehouse inventory system, including batch and expiry tracking, reorder rules, order-system integration and warehouse reporting needs.
Project 13: Student performance dashboard (Ed-tech)
- Problem: An online coaching platform has test scores and attendance data but mentors cannot see which students are falling behind until it is too late.
- Deliverables: KPI definitions (attendance rate, average score, course progress), data dictionary, dashboard wireframe, Power BI or Tableau dashboard on sample data, user stories for mentors and managers, alert rules.
- Tools: Power BI Desktop or Tableau Public, Excel, Figma for the wireframe.
- Steps: Interview a teacher or mentor if you can. Define each KPI in one sentence with its formula. Create sample data for a few hundred students. Sketch the dashboard on paper first. Build it. Write rules for "at-risk" flags and the stories that use them.
- Resume line: Defined KPIs and built a Power BI student performance dashboard on sample data, with at-risk alert rules and user stories for mentors and academic managers.
Project 14: Credit card dispute management (Banking)
- Problem: Card holders who dispute a transaction wait long for updates, and the bank's dispute team tracks cases in spreadsheets.
- Deliverables: Dispute life cycle map (raise, review, temporary credit, investigation, resolution), case statuses, business rules, user stories for customer and agent, RTM, detailed UAT cases including negative scenarios.
- Tools: Lucidchart, Jira, Excel.
- Steps: List dispute types (unrecognised transaction, duplicate charge, item not received). Map the life cycle and statuses. Define rules for each status change. Write stories for raising a dispute in the app and handling it in an agent screen. Build an RTM. Write positive and negative test cases.
- Resume line: Designed a credit card dispute life cycle with case statuses and business rules, and produced an RTM and UAT pack with positive and negative test scenarios.
7. Advanced business analyst projects (15 to 20)
Short answer: Advanced projects connect requirements to business value. Add a business case with options, KPIs, risks, non-functional requirements, data analysis and a change or rollout plan.
Project 15: UPI payment failure reduction (Banking)
- Problem: A bank's mobile app sees complaints about failed UPI payments where money is debited but the merchant is not paid. Customers raise tickets and trust falls.
- Deliverables: Problem framing, fishbone root-cause diagram, sample failure data analysis in SQL, current and future state flows for failed transactions, requirements for clear failure messages and auto-reversal status, KPIs, risk register, business case.
- Tools: SQL, Power BI, Lucidchart, Excel, Word.
- Steps: Learn the basic UPI payment flow between payer app, banks and merchant. Build sample transaction data with failure reasons. Analyse failures by reason, time and bank. Draw a fishbone diagram. Write requirements for customer messaging and reversal tracking. Define success KPIs such as failed-transaction tickets per thousand transactions. Write a short business case.
- Resume line: Analysed sample UPI failure data with SQL, built a root-cause model and business case, and wrote requirements for failure messaging and auto-reversal tracking in a banking app.
Project 16: Customer churn and retention programme (Ed-tech)
- Problem: A subscription learning app loses many users after the first month. Leadership wants to know who leaves, why, and what retention offer to build.
- Deliverables: Churn definition, SQL cohort analysis on sample data, churn drivers, customer segments, three solution options with costs and benefits, recommended option, user stories, success metrics, rollout plan.
- Tools: SQL, Power BI or Tableau, Excel, Google Slides.
- Steps: Define churn precisely (for example, no login for 30 days). Build cohorts by signup month. Compare usage of users who stayed with those who left. Identify drivers. Write three options, such as onboarding nudges, a study planner or a pause feature. Compare them in a table. Recommend one and write its requirements and metrics.
- Resume line: Led a churn analysis case study using SQL cohort analysis, compared three retention options in a business case and wrote requirements and success metrics for the recommended feature.
Project 17: Health insurance claim settlement (Healthcare)
- Problem: Cashless claims at network hospitals are delayed by back-and-forth on documents between the hospital, the third-party administrator and the insurer.
- Deliverables: Multi-party swimlane map, document checklist by claim type, gap analysis, FRD for a claims portal, data and privacy requirements, integration requirements, RTM, change management notes for hospital staff.
- Tools: Visio, Word, Excel, Figma.
- Steps: Map pre-authorisation, admission, interim updates, final bill and settlement. Identify every point where a claim waits for documents. Design a portal where all parties see one checklist and status. Write the FRD with role-based access. Add privacy and audit requirements. Plan training for hospital desks.
- Resume line: Mapped a multi-party cashless claim process, wrote an FRD and RTM for a shared claims portal with role-based access, privacy rules and a staff change plan.
Project 18: Last-mile delivery tracking platform (Logistics)
- Problem: A delivery company has no live view of riders. Customers call to ask where parcels are, and missed deliveries are high.
- Deliverables: Product vision, personas (customer, rider, hub manager), epics and a prioritised backlog using MoSCoW, non-functional requirements (performance, offline mode, battery use), release roadmap, KPI dashboard mock-up, UAT strategy.
- Tools: Jira, Confluence or Notion, Figma, Miro.
- Steps: Write a one-page product vision. Create personas. Break the platform into epics: live tracking, delivery slots, proof of delivery, hub dashboard. Prioritise with MoSCoW. Write non-functional requirements. Plan three releases. Define KPIs and mock up the hub dashboard.
- Resume line: Created the product vision, MoSCoW-prioritised backlog, non-functional requirements and three-release roadmap for a last-mile delivery tracking platform.
Project 19: Employee attrition analysis and business case (HR)
- Problem: An IT services firm is losing early-career employees within two years. HR wants evidence on why, and a costed plan to fix it.
- Deliverables: Analysis of a public or sample HR dataset, attrition drivers, a Power BI dashboard, cost-of-attrition model using clearly stated assumptions, three intervention options, business case, implementation roadmap.
- Tools: Excel, SQL, Power BI.
- Steps: Find a public HR attrition dataset on Kaggle and read its licence, or build sample data. Analyse attrition by department, tenure, overtime and salary band. Build a dashboard. Estimate attrition cost with assumptions written down. Compare options such as a mentoring programme or career paths. Recommend one with a roadmap.
- Resume line: Analysed employee attrition drivers in Power BI, built a cost-of-attrition model with stated assumptions and presented a business case for a retention programme.
Project 20: AI chatbot for customer support (E-commerce)
- Problem: An online electronics store wants an AI chatbot to answer order-status and return questions, but managers worry about wrong answers and data privacy.
- Deliverables: Use-case scope (what the bot will and will not answer), conversation flows, intents list, handoff-to-human rules, guardrail and privacy requirements, acceptance criteria for answer quality, UAT script with sample conversations, KPIs.
- Tools: Miro or draw.io for conversation flows, Google Docs, Excel for the test script, any AI chat assistant to prototype answers.
- Steps: Pick the top five customer questions. Draw a flow for each. Define when the bot must hand over to a human. Write requirements for verifying the customer before sharing order details. Write acceptance criteria such as "the bot never shares another customer's order". Test with 20 sample conversations and record results.
- Resume line: Defined scope, conversation flows, guardrails and acceptance criteria for an AI customer support chatbot, and ran a 20-conversation UAT script covering handoff and privacy rules.
8. Free public datasets for data-heavy projects
Short answer: For data projects, use open, well-documented datasets with a clear licence. The UCI Machine Learning Repository, India's Open Government Data Platform and Kaggle are good places to start.
Requirements projects do not need real data. Data projects (7, 9, 13, 15, 16, 19) do. Here are sources we checked:
- UCI Online Retail dataset. The Online Retail dataset on the UCI Machine Learning Repository has 541,909 transactions from a UK-based online gift retailer, covering 1 December 2010 to 9 December 2011, under a CC BY 4.0 licence (UCI, October 2026). It is ideal for sales dashboards, repeat-customer analysis and product performance.
- Open Government Data Platform India. data.gov.in is the Government of India's open data portal. You can find datasets on topics such as agriculture, health, education and transport. These suit Indian public-sector or social-impact projects.
- Kaggle datasets. Kaggle hosts a large collection of community datasets, including e-commerce, banking and HR attrition data. Quality varies, so read each dataset's description and licence before you use it.
Three rules for using any dataset:
- Credit the source in your project document.
- Write down every cleaning step you take, so a reviewer can follow your logic.
- Never use real personal data from a company you worked for. Use public or sample data only.
If you are unsure which data tools to learn first, our guide to business analyst tools compares Excel, SQL, Power BI, Tableau and the main requirements tools.
9. Example: one project done end to end
Short answer: Here is how Project 4 (employee leave management) looks when written up, with a sample user story, acceptance criteria, a UAT test case and an RTM row. Use this as a pattern for any project.
Problem statement
Employees at a 200-person company apply for leave by email. Managers approve without seeing who else is on leave, and HR updates balances manually each month. This causes clashes, errors in leave balances and wasted HR time. The goal is a self-service leave system with automatic balances and team visibility.
Sample user story
As an employee, I want to see my current leave balance before I apply, so that I do not request more days than I have.
Acceptance criteria
- Given I am logged in, when I open the leave page, then I see my balance for each leave type.
- Given my casual leave balance is 2 days, when I apply for 3 days of casual leave, then the system blocks the request and shows a clear message.
- Given my request is approved, when I check my balance, then it is reduced by the approved days.
Sample UAT test case
Sample RTM rows
This small chain, from problem to requirement to story to test, is exactly what interviewers want to see. It proves you understand traceability, which is a core part of requirements work.
10. How to present business analyst projects in a portfolio
Short answer: Put each project on one clean page with the problem, your role, the deliverables as downloadable PDFs or images, and the outcome. Host it on Google Drive, Notion, a simple website or GitHub, and link it from your resume and LinkedIn.
A recruiter may spend only a few minutes on your portfolio. Make it easy to scan.
Structure each project page like this:
- Title and domain, for example "Digital Savings Account Opening (Banking)"
- Problem in two or three sentences
- Your approach: stakeholders, techniques and tools used
- Deliverables with thumbnails: process maps, a few user stories, wireframes, test cases
- Outcome or recommendation, and what you would do next
- Links to the full documents as PDFs
Where to host it:
Portfolio tips:
- Lead with your best project, not your first.
- Show your thinking. Add a short "assumptions" and "decisions" section so reviewers see why you chose an approach.
- Keep files professional. Use consistent fonts, numbered requirement IDs and version numbers on documents.
- Mark practice work honestly. Write "case study" or "practice project". Never present a practice project as client work.
- Three strong projects are enough for most fresher applications: one process project, one requirements project and one data project.
11. How to explain a business analyst project in an interview
Short answer: Use the STAR structure: situation, task, action, result. Spend most of your time on the actions you took, name the deliverables and techniques, and finish with what you learned or would improve.
Here is a two-minute answer pattern for Project 8 (personal loan origination):
- Situation: "In my loan origination case study, a bank was processing personal loan applications by email, and approvals were slow with no status updates for applicants."
- Task: "My job as the BA was to define requirements for a system covering the journey from application to disbursement."
- Action: "I mapped the AS-IS process, identified stakeholders in sales, credit and operations, wrote a BRD and FRD, defined eligibility rules as a table, built an RTM and wrote a UAT pack with positive and negative cases."
- Result: "The final package showed how status notifications and a shared workflow remove the email handoffs. If I did it again, I would add an earlier review with a credit officer to validate the rules."
Questions interviewers often ask about projects:
- What was the problem and who were the stakeholders?
- How did you gather requirements?
- How did you handle conflicting requirements?
- How did you prioritise?
- How did you make sure the solution met the requirements?
- What would you do differently?
Prepare a short answer to each for every project on your resume. For a full list of questions with sample answers, see our business analyst interview questions.
12. How to write projects on your resume
Short answer: Add a "Projects" section with three to four projects. For each, write the project name, domain, tools and one or two lines that start with an action verb and name the deliverables.
Format to follow:
Personal Loan Origination System (Banking case study). Tools: Visio, Jira, Excel
- Wrote a BRD, FRD and RTM covering application to disbursement for a personal loan journey.
- Built a UAT pack with positive and negative scenarios for eligibility and document checks.
Resume tips for projects:
- Use action verbs: mapped, documented, analysed, designed, defined, validated, prioritised.
- Name the deliverable: BRD, user stories, BPMN process maps, RTM, dashboard. These words help with applicant tracking systems.
- Add numbers you can defend, such as "12 user stories" or "8 UAT cases". Do not invent business results for practice work.
- Link your portfolio next to your name and email at the top.
- Match the job. For a banking BA job, move banking projects to the top.
Our business analyst resume guide shows full sample resumes for freshers and career switchers, including how to lay out the projects section.
13. Common mistakes to avoid in business analyst projects
Short answer: The most common mistakes are jumping to solutions, writing vague requirements, skipping testing, copying templates without thinking and choosing projects that are too big to finish.
- Starting with the solution. "Build an app" is not a problem statement. Start with who is affected and why.
- Vague requirements. "The system should be fast" cannot be tested. Write "The search results page should load within an agreed time under normal load" and state the target.
- No acceptance criteria. A user story without acceptance criteria is a wish, not a requirement.
- Only the happy path. Real systems fail. Add exception flows: payment failure, missing document, rejected approval.
- Copy-pasted templates. Templates help with structure, but reviewers notice generic content. Fill every section with your own scenario.
- Too many tools, too little thinking. A clear process map in draw.io beats a messy one in an expensive tool.
- Unfinished projects. A small, complete project is better than a big, half-done one.
- No version control. Add a version number and date to every document, just as you would at work.
Build portfolio-ready BA projects with a mentor
Our Business Analyst Course in Hyderabad includes six capstone projects, from a BRD and process workflow analysis to a banking loan system and an Agile project simulation in Jira, with resume building and mock interviews. Join a classroom batch in Hyderabad or a live online batch, and book a free demo class first.
14. How Brolly Academy helps
- Our Business Analyst Course in Hyderabad is a 3-month programme with 16 modules, available as classroom training in Hyderabad and live online batches.
- You complete six capstone projects: requirement gathering and BRD, process workflow analysis, data analysis and reporting, an e-commerce business case, a banking loan system and an Agile project simulation in Jira. A hands-on real-time project module lets you work as a junior BA.
- You practise with the tools used in this guide, including Excel, SQL, Jira, Confluence, MS Visio, Lucidchart, Power BI and Tableau.
- Lead instructor Mr. Sri Ram has 15+ years of experience in business analysis.
- Placement assistance includes BA-focused resume building, LinkedIn optimisation, mock interviews and interview preparation.
- Fees listed on the course page: ₹9,999 for the video recording plan, ₹24,999 for the live online course and ₹29,999 for classroom training, with EMI options. A free demo class is available before you enrol.
Frequently asked questions
What is a business analyst project?
A business analyst project is a structured case where you study how a business process works today, find what is wrong or missing, and document a better solution. Typical outputs are a problem statement, stakeholder map, BRD or user stories, AS-IS and TO-BE process maps, wireframes and UAT test cases. Learners can build one using a realistic practice scenario without a real client.
What are some good business analyst project ideas for beginners?
Good beginner ideas include an online order returns process, digital savings account opening, a clinic appointment booking system, an employee leave management system, course enrolment for an ed-tech platform, courier complaint handling and a retail sales dashboard in Excel. Each uses a familiar process with one main user, so you can focus on clean requirements, process maps and test cases.
Which business analyst projects are best for freshers?
Freshers should pick one process project, one requirements project and one data project. For example, a returns process redesign, a leave management system with user stories and UAT cases, and an Excel sales dashboard built on a public dataset. Together they show you can map processes, write testable requirements and work with numbers, which covers most entry-level BA job descriptions.
How many projects should a business analyst have in a portfolio?
Three strong projects are enough for most fresher applications. Aim for one process-focused project, one requirements-focused project and one data-focused project. Depth matters more than volume. One complete project with a BRD, process maps, user stories and UAT cases tells a recruiter more than five one-page summaries that show no real analysis.
What documents should a business analyst project include?
A complete project includes a problem statement, stakeholder map, requirements as a BRD or user stories with acceptance criteria, AS-IS and TO-BE process maps, and UAT test cases. Add wireframes when screens are involved, an FRD and requirements traceability matrix for larger systems, SQL or a dashboard for data work, and a business case for advanced projects.
How do I add business analyst projects to my resume?
Add a Projects section with three or four projects. For each, write the project name, domain, tools and one or two lines that start with an action verb and name the deliverables, such as BRD, user stories or RTM. Use numbers you can defend, such as the count of user stories, and clearly label practice work as a case study.
Can I show business analyst projects on GitHub?
Yes. GitHub works well for data and SQL projects. Create one repository per project and add a README with the problem, approach, key screenshots and links to your documents. For requirements projects, a Notion page or Google Drive folder of PDFs is often easier for recruiters to read, so many BAs use GitHub for data work and Notion or Drive for documents.
What is an example of a business analyst project in banking?
A digital savings account opening project is a good banking example. You map the branch-based process, design a mobile journey with digital KYC, write a BRD with business rules for documents and eligibility, draw a use case diagram, create wireframes and write UAT scenarios. More advanced banking projects include loan origination, credit card disputes and UPI payment failure reduction.
What are good healthcare business analyst projects?
Healthcare projects that work well include a clinic appointment booking system for beginners, a hospital discharge and billing process redesign at the intermediate level, and a health insurance cashless claim settlement portal for advanced learners. Each involves several stakeholders, clear process delays to fix and patient data privacy requirements, which interviewers in this domain value.
What is an end-to-end business analyst project?
An end-to-end project follows the full chain from problem to tested solution. You write the problem statement, identify stakeholders, gather and document requirements, map AS-IS and TO-BE processes, write user stories with acceptance criteria, trace each requirement to a test case in an RTM and write UAT cases. This shows a recruiter you understand the whole requirements life cycle.
What is a real-time business analyst project?
A real-time or live project usually means work on a realistic business case that copies how BAs operate on the job, often guided by a mentor or done during an internship. It goes beyond theory by using real deliverables such as a BRD, Jira backlog, process maps and UAT cases. Always be honest about whether a project was practice work or for a real client.
Do I need coding skills for business analyst projects?
No. Most BA projects focus on understanding problems, writing requirements, drawing process maps and planning testing, which need no coding. Basic SQL and Excel do help for data-focused projects such as funnel or churn analysis, and many employers like seeing them. You can build strong requirements projects with only diagramming, wireframing and document tools.
Which tools should I use for business analyst projects?
For process maps, use draw.io, Lucidchart or MS Visio with BPMN notation. For wireframes, use Figma or Balsamiq. For backlogs and user stories, use Jira or Trello, with Confluence or Notion for documentation. For data projects, use Excel, SQL and Power BI or Tableau. Free plans and free tools are enough for portfolio work.
Where can I find free datasets for business analyst projects?
Good free sources include the UCI Machine Learning Repository, India's Open Government Data Platform at data.gov.in and Kaggle. The UCI Online Retail dataset has 541,909 transactions from a UK online gift retailer between December 2010 and December 2011 under a CC BY 4.0 licence. On Kaggle, always check each dataset's description and licence first.
Can I do a Power BI project as a business analyst?
Yes. A Power BI dashboard is a strong addition when it answers a clear business question. Good examples are a student performance dashboard with at-risk alerts, an employee attrition dashboard with a business case, or a churn analysis for a subscription app. Define your KPIs and business questions before you build, and add a short insights summary with recommendations.
What Excel projects can a business analyst do?
A retail sales dashboard is a great Excel project. Take a public dataset such as the UCI Online Retail data, clean it with Power Query, build pivot tables for sales by month, product and country, and create a one-page dashboard. Finish with three plain-language insights and recommendations. Excel also works well for business rules tables, RTMs and UAT test scripts.
What is a good SQL project for a business analyst?
A cart abandonment funnel analysis is a practical SQL project. Create sample tables for users, sessions, cart events and orders, or adapt a public e-commerce dataset. Write queries for each funnel step, calculate drop-off at each stage and turn the biggest causes into user stories. This shows you can use data to support requirements, not just write queries.
How do I explain my business analyst project in an interview?
Use the STAR structure: situation, task, action and result. Briefly describe the business problem and your role, then spend most of the time on the actions you took, naming deliverables such as the BRD, process maps and RTM. End with the outcome and one thing you would improve. Prepare answers on stakeholders, prioritisation and handling conflicting requirements.
What are good business analyst projects for MBA students?
MBA students should pick projects that link analysis to business value. Strong choices include a customer churn and retention programme with options and a business case, an employee attrition analysis with a cost model, and UPI payment failure reduction with KPIs and a risk register. These show strategic thinking alongside requirements and data skills.
What is the difference between AS-IS and TO-BE process maps?
An AS-IS map shows how a process works today, including delays, manual handoffs and pain points. A TO-BE map shows the improved process after your proposed change. Comparing the two gives you a gap analysis, which lists what must change to move from the current to the future state. Most BA projects use BPMN notation for both maps.
How do I write user stories for a business analyst project?
Write each story in the format "As a user type, I want a goal, so that a benefit." Add acceptance criteria, often in the Given, When, Then style, so each story can be tested. Check every story against the INVEST checklist from the Agile Alliance: independent, negotiable, valuable, estimable, small and testable.
Can I do an AI-related business analyst project?
Yes. A good example is defining requirements for an AI customer support chatbot. Set the scope of questions it answers, draw conversation flows, write rules for handing over to a human, and add guardrail and privacy requirements, such as verifying the customer before sharing order details. Then test it with a script of sample conversations and record the results.
What mistakes should I avoid in business analyst projects?
Avoid jumping straight to a solution, writing vague requirements that cannot be tested, skipping acceptance criteria, covering only the happy path and filling templates with generic content. Also avoid projects too large to finish. A small, complete project with clear exception flows, version numbers and traceable test cases makes a far better impression than an unfinished big one.
Does Brolly Academy include real-time business analyst projects?
Yes. The Brolly Academy Business Analyst Course in Hyderabad includes six capstone projects: requirement gathering and BRD, process workflow analysis, data analysis and reporting, an e-commerce business case, a banking loan system and an Agile project simulation in Jira. A hands-on real-time project module also lets learners work as a junior business analyst under guidance.
How long is the Brolly Academy Business Analyst course and what does it cost?
The Brolly Academy Business Analyst Course in Hyderabad runs for 3 months with 16 modules, in classroom and live online batches. The course page lists ₹9,999 for the video recording plan, ₹24,999 for the live online course and ₹29,999 for classroom training, with EMI options. You can attend a free demo class before enrolling.
Learn with Brolly Academy
Review the syllabus, practical projects and batch timings, and book a free demo before you enrol.
Related Articles
Continue Your Learning
Business Analyst Course in Hyderabad
Requirements, BRD and user stories, UML, Agile, Jira, SQL, Excel and Power BI with six capstone projects and placement support.
View CourseData Analytics Course in Hyderabad
Excel, SQL, Python, Power BI and Tableau with real business datasets and projects.
View CourseProduct Management Course
Product discovery, roadmaps, user research, metrics and Agile delivery for aspiring product managers.
View Course