Conquer Your Career: Scrum Master, Agile Coach & PMP Exam Prep (Part V)

–

Continued From Part IV HERE

–

Interview And Test Prep For Agile, Scrum And PMP Roles: 

#Q1: What is MoSCoW prioritization, and how does it work?
A:
MoSCoW is a prioritization framework that categorizes work into four buckets:
– M (Must have): Critical features for project success.
– S (Should have): Important but not vital (can be deferred if needed).
– C (Could have): Desirable but non-essential (included if time permits).
– W (Won’t have): Excluded from the current release (may be revisited later).
After categorization, features within each group are ranked by preference or dependency.

#Q2: Explain ICE prioritization and its formula.
A:
ICE (Impact, Confidence, Ease) scores features on three criteria (rated 1–10):
– Impact: How much value the feature delivers.
– Confidence: Certainty in the impact and ease estimates.
– Ease: Effort required to implement.
Formula: `ICE Score = Impact × Confidence × Ease`. Higher scores indicate higher priority.

#Q3: How does Agile handle changing requirements?
A:
Agile embraces changing requirements through backlog prioritization. The Product Owner continuously reorders the backlog, placing high-value items (e.g., “river rocks”) at the top. Lower-value items (e.g., “sand”) are deferred or dropped, ensuring the team always works on the most impactful tasks.

#Q4: Compare Kano and MoSCoW prioritization.
A:
– Kano categorizes features into:
– *Exciters/Delighters* (innovative, high-value).
– *Satisfiers* (basic expectations).
– *Dissatisfiers* (must-haves; absence causes frustration).
– *Indifferent* (low impact).
– MoSCoW focuses on necessity (Must/Should/Could/Won’t).
Key difference: Kano evaluates emotional impact, while MoSCoW assesses urgency.

#Q5: What are the five stages of Design Thinking?
A:
1. Empathize: Observe/user interviews to understand pain points.
2. Define: Create personas and articulate challenges.
3. Ideate: Brainstorm solutions (no bad ideas).
4. Prototype: Build quick mockups to test concepts.
5. Test: Iterate based on user feedback.

#Q6: Why is “failing fast” important in Design Thinking?
A:
Rapid prototyping and testing allow teams to identify flaws early, reducing costly rework later. It encourages experimentation and pivots before full-scale development.

#Q7: What testing is essential before launch?
A:
– User Acceptance Testing (UAT).
– Integration/Regression Testing.
– Performance/End-to-End Testing.
Goal: Ensure the system works as intended in real-world conditions.

#Q8: Why might a vendor handle API integrations for a COTS product?
A: Vendors have experience with their product’s APIs, reducing integration risks and ensuring compatibility.

#Q9: What key sections should an RFP for vendor selection include?
A:
– Project scope/deliverables.
– Management/communication plans.
– Requirements table.
– Timeline/budget range.
– Selection criteria (e.g., references, solution fit).
– Proposal submission deadlines.

#Q10: How does the “jar of rocks and sand” analogy relate to backlog prioritization?
A: The jar represents project capacity. High-priority items (“rocks”) are added first; lower-priority items (“sand”) fill gaps. This ensures critical work isn’t displaced by less valuable tasks.

#Q: What is SAFe, and why did Fannie Mae adopt it?
A:
SAFe (Scaled Agile Framework) is a scaling model focused on alignment, collaboration, and Lean-Agile practices across large organizations. It combines Agile software development, Lean product management, and systems thinking.
Fannie Mae adopted SAFe after the 2013 housing crisis to:
– Improve responsiveness to customer demands.
– Enable continuous integration and early testing to mitigate risk.
– Achieve reduced defect rates and improved quality through automation.

#Q: What are the key components of SAFe?
A:
– Team Level: Scrum/Kanban teams.
– Program Level: Agile Release Trains (ARTs) delivering Product Increments (PIs) on a fixed cadence (usually quarterly).
– Portfolio Level: Prioritizes work based on organizational objectives.

#Q: What are the pros and cons of SAFe?
A:
✅ Pros:
– Most popular scaling model (easy to find training/coaching).
– Provides a detailed implementation roadmap.
– Well-suited for large, structured organizations.
❌ Cons:
– Highly prescriptive – may not foster deep Agile mindset shifts.
– Requires extensive training/certifications (criticized as revenue-driven).
– Some information is locked behind SAFe’s paid community.

#Q: What is LeSS, and why did JPMorgan Chase use it?
A:
LeSS scales Scrum across large organizations by removing hierarchy to boost speed, quality, and collaboration. JPMorgan Chase adopted LeSS to:
– Eliminate bureaucracy slowing agility.
– Reduce handoffs, dependencies, and delays.
– Empower teams to make decisions autonomously.

#Q: What are the two levels of LeSS?
A:
1. LeSS (Basic): For up to 8 teams sharing one Product Backlog.
2. LeSS Huge: Scales to 1,000+ developers with additional role definitions.

#Q: What are the pros and cons of LeSS?
A:
✅ Pros:
– Simple (extends Scrum principles).
– Configurable to organizational needs.
– Focuses on working product over overhead.
❌ Cons:
– Requires high Scrum discipline.
– Demands complete IT restructuring (product-focused teams).
– Less prescriptive – gaps require customization.

#Q: What’s the risk of focusing on *doing* Agile rather than *being* Agile?
A:
Teams may follow rituals (e.g., standups, sprints) without embracing Agile values (collaboration, adaptability, customer focus). This leads to:
– Superficial compliance (e.g., “Waterfall in Agile clothing”).
– Missed cultural transformation (e.g., command-and-control persists).

#Q: What is technical debt, and how does it accumulate?
A:
Technical debt is the implied cost of rework from prioritizing speed over perfect code. Causes include:
– Bugs (untested code).
– Legacy code (outdated systems).
– Bit rot (patches from multiple developers).
– Missing documentation.
Impact: Slows future development and increases maintenance costs.

#Q: How can remote teams enhance brainstorming?
A:
– Use Miro (digital whiteboard) for real-time visual collaboration.
– Async tools (e.g., Slack, Confluence) for ongoing ideation.
– Structured virtual ceremonies (e.g., time-boxed retrospectives).

–

Free Assessments, Interview Prep and Exam Certification Study Guides:

Find the FREE resource HERE.

–

NOTE: This is a living document, and I will keep adding questions and answers occasionally, so please keep checking this space.

– 0 –

The Future Of Work Is Now

The Non-Cognitive Skills Needed For The Future, Our Hybrid Work Life And Much More

If you’re not careful you can follow your passion right into poverty. ~ Srini Rao

*