Project Manager
Scope, change and governance questions
131 questions on Scope, change and governance for project managers, easiest first.
Easy 47
- The triple constrainteasy
- Work breakdown structureeasy
- What a project charter doeseasy
- First steps on a new projecteasy
- Project or operations?easy
- What scope creep meanseasy
- Purpose of the retrospectiveeasy
- The Definition of Doneeasy
- When to capture lessons learnedeasy
- Purpose of a change requesteasy
- What a baseline iseasy
- Closing a projecteasy
- Product scope or project scopeeasy
- What a scope statement holdseasy
- Why list exclusionseasy
- What gold plating meanseasy
- Why acceptance criteria mattereasy
- MoSCoW "Must have"easy
- Validating scopeeasy
- Parts of the scope baselineeasy
- Why run a requirements workshopeasy
- Spotting a non-functional requirementeasy
- The user story formateasy
- Learning from existing documentseasy
- What a context diagram showseasy
- When to prototypeeasy
- Business or solution requirementeasy
- The change control boardeasy
- Why keep a change logeasy
- Before approving a changeeasy
- What configuration management controlseasy
- What a RAID log trackseasy
- What a steering committee doeseasy
- A directive PMOeasy
- Why use stage gateseasy
- Why write a business caseeasy
- A PRINCE2 highlight reporteasy
- Why keep a decision logeasy
- Handing over at closureeasy
- What a programme iseasy
- Portfolio managementeasy
- The kick-off meetingeasy
- A new request mid-projecteasy
- Gold platingeasy
- Purpose of a kick-offeasy
- Formal sign-off at closureeasy
- When to capture lessonseasy
Medium 50
- A 'small' extra requestmedium
- Control chart rule of sevenmedium
- Using a Pareto chartmedium
- Prevention costsmedium
- The "I" in INVESTmedium
- Splitting a story wellmedium
- Kano model categoriesmedium
- The Definition of Readymedium
- What sign-off does and does not domedium
- A vague requirementmedium
- Observing users at workmedium
- The point of an MVPmedium
- Open questions in interviewsmedium
- Benchmarking competitorsmedium
- Transition requirementsmedium
- From verified to acceptedmedium
- Reaching many usersmedium
- A vendor statement of workmedium
- Exclusions in a fixed-price quotemedium
- Use case flowsmedium
- Why the backlog is orderedmedium
- Given-When-Thenmedium
- High power, low interestmedium
- Specifying an interfacemedium
- After a change is approvedmedium
- An emergency changemedium
- Which changes the PM can approvemedium
- Manage by exceptionmedium
- The PRINCE2 senior usermedium
- Who owns the benefitsmedium
- When benefits are measuredmedium
- A controlling PMOmedium
- A rejected change requestmedium
- Change in a Scrum projectmedium
- Two kinds of closuremedium
- Why audit a projectmedium
- Project assurancemedium
- Closing a cancelled projectmedium
- Deemed acceptance after silencemedium
- Signing above your limitmedium
- Escalating a forecast breachmedium
- At the end of a stagemedium
- When to raise an exceptionmedium
- Hypercare after go-livemedium
- A big change and the business casemedium
- The change curvemedium
- The ADKAR modelmedium
- Stating what is out of scopemedium
- Kotter's first stepmedium
- A change champions networkmedium
Hard 34
- Measuring project successhard
- Fixed date and budget, agile teamhard
- A valid reason to re-baselinehard
- A sponsor asks a developer directlyhard
- A missing migration in a fixed price dealhard
- Sign-off refused without criteriahard
- High requirements churnhard
- Fixed price with unclear needshard
- An unrequested feature is readyhard
- A missing peak-load requirementhard
- A story too big for a sprinthard
- When everything is a Musthard
- How Kano categories changehard
- When to validate deliverableshard
- Accepting with a snag listhard
- A stakeholder found too latehard
- A requirement from a new lawhard
- Charter or scope statementhard
- When the board cannot agreehard
- Many small changeshard
- A hotfix outside the processhard
- Liquidated damages with a caphard
- Skipping a gate reviewhard
- A change that hits another projecthard
- Measuring a benefit with no baselinehard
- Open items at closurehard
- A change approved by the wrong personhard
- Funding in lean portfolio managementhard
- Is this change worth ithard
- A steering committee that cannot decidehard
- When to review privacyhard
- Clarification or changehard
- Lessons that are never usedhard
- Who owns benefits after go-livehard