Enterprise BA: Crisis to Continuity

[rlscorner]

Enterprise BA: Crisis to Continuity
Published 10/2026
MP4 | Video: h264, 1920x1080 | Audio: AAC, 44.1 KHz, 2 Ch
Language: English | Duration: 3h 29m | Size: 4.38 GB

Master a crisis playbook for any company: war room, emergency CAB, triage, comms and post-mortems, then apply it live

What you'll learn
Run a command center with an Incident Commander, clear roles, and separate technical and executive channels
Bypass red tape safely with an Emergency CAB, a quorum of three and a verbal audit trail
Triage a multi-system outage by business impact using SLAs, RTO, RPO and application tiers
Run crisis communications that build trust: update cadence, business-language translation, and Legal and PR gates
Lead a blameless post-mortem with the Five Whys and turn the findings into mandated fixes
Frame a rollback vs fix-forward decision and secure explicit executive sign-off
Design manual workarounds and draft procedures fast with AI, then verify them before anyone follows them
Validate a recovery and reconcile the data lost, using Jira and Confluence as your crisis workspace

Requirements
Basic familiarity with the business analyst role
No coding or technical background needed
Experience with Jira or Confluence is helpful but not required

Description
This course contains the use of artificial intelligence.

When a core system fails, the technology is rarely the first thing that breaks. The structure is. Forty people talk over each other on one bridge call, executives demand answers from the engineers fixing the problem, and nobody knows who is allowed to approve the fix. In a crisis, a business analyst brings order: coordinate, translate, document and help the business decide.

This course gives you a crisis playbook you can use at any company, then puts you inside a realistic simulation to see it applied. Learn the playbook, then watch it work.

Module 0: The Enterprise Crisis Playbook

Six short lessons, a welcome and five methods, independent of any company or scenario

- Command center: name an Incident Commander, assign roles, and split the technical and executive channels

- Emergency CAB: bypass red tape without bypassing accountability

- Triage: prioritize recovery with Service Level Agreements, RTO, RPO and application tiers

- Crisis communications: control the narrative without distracting the engineers

- Blameless post-mortem: fix systems, not people, with the Five Whys

Capstone Modules 1-4: The Simulation

A rushed security patch goes live at Boreal Clearing House Limited, a fictional company headquartered in New York with branches around the world. Four modules follow the incident from the first bridge call to the final report for the Board. You work alongside two Enterprise BAs, Victoria Chen and Prakash Rao, and a distributed team across the US, London, Bangalore and Chennai, applying the playbook step by step.

What you will learn
- Structure a crisis: turn a chaotic bridge into a command center with a Jira crisis epic and a Confluence decision log.

- Translate between technical and business: size the business impact, brief executives, and work with Legal and Corporate Communications.

- Work across time zones: run hand-offs, escalation paths and contact lists.

- Frame a high-stakes decision: build a rollback vs fix-forward matrix and secure explicit executive sign-off.

- Keep the business running: design manual workarounds, and draft procedures fast with AI and verify them before anyone follows them.

- Recover and verify: validate recovery and reconcile the data lost during the outage.

- Turn the crisis into process change: lead a blameless post-mortem and add an auditable emergency path to your workflow.

- Prove it and fund the fix: run business validation checklists, track corrective actions with owners and dates, and report to the executives in two pages.

How the course works
Each capstone module opens with an Agile team meeting and closes with a Sprint Review. Each lesson ends with a lesson learned: one practical takeaway you can apply in your own crisis. This is a practical, scenario-based course, not a tool tutorial. Jira and Confluence appear as the places where the crisis is managed.

All companies, people and events in the capstone are fictional and created for teaching.

About the instructor
Mo Kammoun is a healthcare IT and interoperability professional with more than 25 years of experience across telecom, pharma and healthcare. He has worked on many mission-critical enterprise projects for internal and external customers, leading and supporting distributed teams around the world. He teaches only what he has applied in real work.

Who this course is for
Business analysts working in large enterprises
Scrum Masters who also act as BAs
Aspiring enterprise BAs who want to see how the role works under pressure
Product owners and project managers who work alongside BAs on releases and incidents

Homepage

Code:

https://www.udemy.com/course/enterprise-ba-crisis-to-continuity/

Code:

https://rapidgator.net/file/8b2218fa8d2793fb59e38820633b6b30/Enterprise_BA_Crisis_to_Continuity.part5.rar.html
https://rapidgator.net/file/45537a85963556a3c0b490cdf79ccb06/Enterprise_BA_Crisis_to_Continuity.part4.rar.html
https://rapidgator.net/file/cce77d2ba8fb5753822bdb9204662f25/Enterprise_BA_Crisis_to_Continuity.part3.rar.html
https://rapidgator.net/file/440825ad0c4fa69b13e2c53aea10a4c0/Enterprise_BA_Crisis_to_Continuity.part2.rar.html
https://rapidgator.net/file/413b257e3d58364d1881336a5f04cd32/Enterprise_BA_Crisis_to_Continuity.part1.rar.html

https://nitroflare.com/view/73A7323CA1308C2/Enterprise_BA_Crisis_to_Continuity.part5.rar
https://nitroflare.com/view/51928A4793399D0/Enterprise_BA_Crisis_to_Continuity.part4.rar
https://nitroflare.com/view/5CF0220ACDAF142/Enterprise_BA_Crisis_to_Continuity.part3.rar
https://nitroflare.com/view/E9779D63FA93591/Enterprise_BA_Crisis_to_Continuity.part2.rar
https://nitroflare.com/view/234C7C9B6D6CF93/Enterprise_BA_Crisis_to_Continuity.part1.rar