Analyse
Take a vague business problem, identify stakeholders, ask useful questions and frame the real need.
LEARNING · PRACTICE · INDUSTRY READINESS
This is not a collection of disconnected notes. The curriculum is designed as a progression: understand the business problem, define the work, deliver it, communicate decisions, and evaluate outcomes. Every chapter has concepts, practical application and a piece of proof-of-work.
Each topic moves through four levels. Learn gives you the mental model. Apply puts it into a realistic scenario. Produce creates an artifact. Explain makes sure you can defend your thinking in a meeting or interview.
Follow this order if you are starting from zero. You can still jump into an individual chapter, but the sequence is deliberate: each phase prepares you for the next.
Build the core BA skill: understand the business problem, discover what is really happening, turn needs into buildable requirements, and evaluate whether the solution created value.
Problem vs solution • BA mindset • value and outcomes • BA responsibilities • BA vs PM/Product/Developer
Problem statements • business objectives • root cause • assumptions • evidence • scope of the problem
Stakeholder identification • influence/interest • roles • needs • engagement strategy • conflicts
Interviews • workshops • observation • document analysis • questioning • active listening • elicitation planning
Business/stakeholder/solution requirements • functional/non-functional • constraints • assumptions • dependencies • acceptance criteria
AS-IS • TO-BE • flowcharts • swimlanes • decisions • handoffs • bottlenecks • process improvement
Prioritization • MoSCoW • validation • requirement quality • traceability • change impact
Acceptance • outcome measurement • KPIs • benefits realization • adoption • feedback • continuous improvement
Learn to turn an approved objective into controlled delivery: initiation, scope, WBS, schedule, cost, quality, risk, communication, execution and closure.
Projects vs operations • value delivery • lifecycle • constraints • tailoring • PM role • delivery environment
Business case • feasibility • objectives • success criteria • charter • assumptions • high-level stakeholders
Scope boundary • deliverables • acceptance • decomposition • WBS • work packages • scope creep
Activities • dependencies • sequencing • milestones • critical path • float • schedule risk
Budget • estimates • cost baseline • quality planning • variance • EV/PV/AC • CPI/SPI
Risk identification • probability/impact • responses • RAID • issues • change control • escalation
Stakeholder engagement • team roles • communication planning • status reporting • conflict • escalation
Readiness • UAT • go-live • handover • closure • lessons learned • benefits review
Understand Agile as a delivery system built around value, feedback, small increments, transparency and adaptation — not simply ceremonies.
Agile values • empiricism • feedback • uncertainty • incremental delivery • collaboration • customer value
Product vision • goals • outcomes • backlog • ordering • value • MVP • discovery
User story structure • personas • value • acceptance criteria • examples • edge cases • INVEST
Sprint goal • planning • capacity • refinement • increment • Definition of Done
Product Owner • Scrum Master • Developers • Sprint Planning • Daily Scrum • Review • Retrospective
Relative estimation • story points • planning poker • capacity • prioritization • uncertainty
Product metrics • delivery metrics • flow • velocity • feedback • retrospectives • experiments
Build the consulting layer: discover the real problem, challenge assumptions respectfully, compare options, make scope/commercials clear and help clients make decisions.
Discovery structure • business context • goals • pain points • current state • questioning • evidence
Requested solution • underlying need • root cause • evidence • challenge assumptions • reframing
Options • feasibility • effort • cost • risk • scalability • trade-offs • recommendation
Scope boundary • assumptions • estimates • dependencies • pricing logic • change requests • negotiation
Executive updates • status • decisions • risks • escalation • demos • approvals • expectation management
Learn to design a delivery model around the nature of the work: predictive control where certainty matters and iterative learning where uncertainty is high.
Predictive vs iterative • uncertainty • complexity • compliance • fixed dates • tailoring
Workstream design • lifecycle choices • governance • decision rights • cadence • tailoring principles
Controls • baselines • approvals • review gates • reporting • change • decision forums
Integrated planning • interfaces • dependencies • milestones • release planning • uncertainty
eCommerce transformation • fixed launch • iterative UX • migration • governance • learning
Progress is based on what you can do, not how many videos you watched.
Take a vague business problem, identify stakeholders, ask useful questions and frame the real need.
Produce requirements, process maps, acceptance criteria and a traceable scope that another person can understand.
Turn the defined work into a plan, manage risks and dependencies, coordinate people and communicate status.
Compare options, explain trade-offs, challenge assumptions and make a decision-ready recommendation to a client.
These stay intentionally separate from the core BA/PM path. Each will be built from fundamentals to practical work rather than as a tool-tour.
Storefront foundations, Liquid, theme architecture, sections, snippets, metafields, apps, integrations, performance and real-world eCommerce builds.
Database thinking, querying, filtering, aggregation, joins, subqueries, analysis patterns and business-question-driven practice.
Data preparation, modelling, relationships, DAX fundamentals, KPI design, dashboards and decision-focused storytelling.
Practical analysis, formulas, lookups, PivotTables, cleaning, reporting and workplace-ready workflows.
These are deliberately different from the curriculum: practical judgment, patterns and lessons that are easier to understand after seeing the structured concepts.
Separating a requested solution from the underlying business need.
Read field note →DELIVERYHow predictive controls and iterative delivery can fit together.
Read field note →PROJECT MANAGEMENTTurning status reporting into a decision tool instead of a data dump.
Read field note →The curriculum is written for practical learning. When a formal framework matters, verify the definition against the authoritative source.