Business Analysis | Project Management | Practical Learning
Learn Business Analysis. Master Project Delivery. Solve Real Business Problems.
Learn how business analysts identify problems, gather requirements, analyse processes and define solutions. Discover how project professionals plan delivery, coordinate stakeholders and manage risks.
Follow structured paths, explore a worked case study, use templates and practise real-world scenarios.
Start LearningExplore Case StudiesBrowse ResourcesSearch the library
Search lessons, glossary terms, templates, the case study and interview questions.
Learn: Business Analysis, Project Management and Agile
Five phases that follow a real project lifecycle. Pick a phase, filter by role, open a topic, and tick it off. See the study map for how lessons line up with BABOK and PMBOK topics.
Case study: e-commerce order management
Simulated educational scenario. ShopEase is fictional. All numbers are illustrative assumptions, not real results.
More case studies (outlines only, deliverables not yet written)
Banking loan origination
Problem: slow applications and inconsistent customer updates. Planned: stakeholders, workflow, business rules, exceptions, UAT, risks.
Ride-hailing retention
Problem: failed rides and cancellations. Planned: customer journey, root causes, KPIs, prioritisation.
Inventory management
Problem: stockouts and excess stock. Planned: process maps, rules, stories, UAT, risks.
Support ticketing
Problem: lost requests and inconsistent response times. Planned: ticket lifecycle, SLAs, escalation matrix, dashboards.
Templates and resources
Illustrative starter templates, not official industry standards. Download a file or copy the text. Each has one example row to show the format.
Not yet available: FRD, SRS, change request, project plan, WBS, status report, sprint worksheets and the burndown example.
Glossary
Knowledge check
Six questions on core lessons. Answer all, then check.
Study map
A loose study guide written by The 360 Analyst, not an official mapping. Use it to find lessons when you study the BABOK Guide v3 knowledge areas or the PMBOK process groups.
| BABOK v3 knowledge area | Lessons to start with |
|---|---|
| Business analysis planning and monitoring | Stakeholder analysis, RACI and DACI |
| Elicitation and collaboration | Elicitation techniques, Wireframes and user journeys |
| Requirements life cycle management | BRD, FRD and RTM, MoSCoW prioritization |
| Strategy analysis | SWOT analysis, PESTLE and MOST, Gap analysis, AS-IS vs TO-BE analysis |
| Requirements analysis and design definition | Requirement types, BPMN process modeling, UML diagrams, Data modeling, User stories and Gherkin |
| Solution evaluation | User Acceptance Testing, Root cause analysis |
| Project process group | Lessons to start with |
|---|---|
| Initiating | Project charter and business case, Stakeholder analysis |
| Planning | Work Breakdown Structure, Scheduling: CPM, PERT, Gantt, Risk management |
| Executing | Quality management, Procurement and vendors, Agile and Scrum |
| Monitoring and controlling | Earned Value Management, Change control |
| Closing | Closure and lessons learned, User Acceptance Testing |
BA vs PM at a glance
Two roles, one outcome. Knowing where they differ makes handoffs smoother.
| Business Analyst | Project Manager | |
|---|---|---|
| Core question | What problem are we solving, and what must the solution do? | How, when and at what cost will we deliver it? |
| Main output | Requirements, models, business case, acceptance criteria | Plan, schedule, budget, risk register, status reports |
| Standard | BABOK Guide (IIBA) | PMBOK Guide (PMI) |
| Certifications | ECBA, CCBA, CBAP | CAPM, PMP |
| Success measure | Solution delivers the intended business value | On time, on budget, in scope, with quality |
Example: fixing stock discrepancies
Role boundaries vary between organizations. This is one common split.
| Activity | Usually led by | Collaboration |
|---|---|---|
| Investigate why stock counts differ | BA | PM schedules time with warehouse staff |
| Define inventory visibility requirements | BA | PM confirms scope and budget fit |
| Build the delivery plan, milestones and dependencies | PM | BA flags requirement-driven dependencies |
| Manage risks and vendor timelines | PM | BA assesses impact on requirements |
| Assess a change request for scanners | Shared | BA: business impact. PM: time and cost impact |
| Plan and run UAT, then sign-off | Shared | BA: scenarios. PM: schedule and approvals |
Career Hub
Practice answers that explain the reasoning. Use your own experience and projects, and never claim simulated work as employment.
Portfolio and resume
List projects like this case study under "Projects" and label them "simulated". Show the problem, your method, the deliverables and what you learned. Do not state fictional results as real.
Use a clear headline (for example "Aspiring Business Analyst | Requirements | Process Modelling"), summarize your projects, and link your portfolio. Describe skills you can demonstrate.
Job-readiness checklist
No tool or course can guarantee a job or certification result.
About The 360 Analyst
The 360 Analyst is an independent learning project for aspiring business analysts and project professionals. Content is for education and is not affiliated with IIBA or PMI. Terms and role boundaries differ between organizations, so check the BABOK Guide, PMBOK Guide and your employer’s practice.