PMGT-BC study materials
PMGT-BC study resources

PMGT-BC case studies

PMGT-BC · Put your knowledge to work in context.

PMGT-BC is a business-analysis-focused project management certification aimed at practitioners who sit between the project team and the business: business analysts, project coordinators and leads, product owners, and process or requirements specialists who need to manage work and elicit, document, and validate requirements in the same role. The exam is multiple choice and is organized around four domains: project management fundamentals and core concepts (the largest single block), predictive and plan-based methodologies, agile frameworks and methodologies, and business analysis frameworks. Expect questions that test judgment rather than recall - choosing the right technique for a situation, distinguishing one framework from another, and recognizing which artifact or process belongs to which approach. Preparation works best in layers: build vocabulary and process knowledge for the fundamentals domain first, then study predictive and agile delivery side by side so you can compare them, and finish with business analysis frameworks, which rewards practice with elicitation, stakeholder, and requirements-traceability scenarios. The PMGT-BC case studies are 5 cases and about 2,648 words.

1

The Schedule Compression Squeeze

You are the project manager for a 9-month warehouse management system implementation with a fixed go-live date tied to a holiday peak season. The critical path currently runs 6 weeks past the committed date.

536 words, about 3 min
2

Requirements That Keep Moving

You are the business analyst on a customer onboarding portal for a regional bank. Six weeks into a 12-week discovery-and-design phase, you have 140 requirements documented.

493 words, about 2 min
3

The Sprint That Cannot Finish

You are the Scrum Master for a team of seven delivering an insurance claims intake product. Over the last four sprints, the team has committed to an average of 42 story points but completed an average of 29.

483 words, about 2 min
4

The Estimate Nobody Trusts

You are managing a data migration project moving 12 legacy systems into a single platform. Your lead architect provides a bottom-up estimate of 14 weeks for the migration work.

553 words, about 3 min
5

The Stakeholder Who Won't Sign

You are leading an ERP finance-module rollout for a mid-sized manufacturer. The project is 70% complete and on schedule.

583 words, about 3 min