---
title: "Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109 160114-Meeting Recording"
type: cloud-learning
source-type: video
category: "DevOps & SRE/10_OpenText-Series"
tags:
  - Business-Analysis
  - Techniques
date-added: 2026-04-14
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109_160114-Meeting Recording.mp4"
audio-source: ""
status: summarized (Gemini 摘要)
---

# Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109 160114-Meeting Recording

**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Applicable Business Analysis Techniques - 20240109_160114-Meeting Recording.mp4`

**Type:** VIDEO | **Category:** 10_OpenText-Series

**Status:** 🟡 Awaiting Whisper transcription → Summary

---

## Business Analysis Techniques Learning Session

This learning session introduces business analysis, T-shaped skill sets, and learning resources. It focuses on three techniques for defining new work: BOSCARD (Background, Objectives, Scope, Constraints, Assumptions, Risks, Roles, Deliverables), the stakeholder wheel, and a method for gathering requirements that combines agile user stories with metadata.

Business analysis aligns business needs with change solutions, considering IT and process changes, training, and role shifts. The business analysis process involves investigating the current situation, analyzing needs, identifying solutions, evaluating options, and defining requirements. Benefits include clarity and consistency. *Business analysis helps us work out what changes will be beneficial in our business architecture, including changes to IST systems and defining the requirements for those changes.*

T-shaped skills are valuable in agile squads, combining core expertise with a broad understanding of related skills. Business analysis skills bridge the gap between business problems and technical solutions. Resources for learning business analysis include the BCS and IIBA curriculums.

### BOSCARD Technique

BOSCARD defines complex new work by clarifying background, objectives, scope, constraints, assumptions, risks, roles, and deliverables. It helps avoid confusion about goals, timelines, and deliverables. *If you can get scope tied down early on and agreed, that's priceless.*

### Stakeholder Wheel

The stakeholder wheel identifies all stakeholders for a project, including customers, partners, regulators, employees, managers, owners, and competitors. Identifying stakeholders early prevents changes and uncovers risks. The wheel starts with the customer and moves clockwise. Stakeholder analysis can involve mapping stakeholders on a power/influence grid or creating a RACI (Responsible, Accountable, Consulted, Informed) chart.

### Requirements Gathering

Combining user stories with metadata adds rigor to requirements capture. User stories capture the what, who, and why, but lack versioning, dependencies, and traceability. The Scaled Agile Framework (SAFe) includes features, capabilities, and non-functional requirements in addition to stories.

A detailed Excel sheet example captures requirements for a garage business, including user stories, versioning, dependencies, traceability, scheduling, acceptance criteria, and categorization (business, technical, functional). The INVEST acronym (Independent, Negotiable, Valuable, Estimable, Small, Testable) is used to check requirements. *Every requirement should be independent, meaning not duplicating something else, that's the I in invest, negotiable, so the business should state what they need, but be open to how it's implemented.*
