Full Description
Explore themes often glossed over in traditional Agile texts: navigating the transition from a technical architect to a servant leader, handling conflicting priorities and leadership misalignments, and managing value delivery in client-driven environments where frameworks alone are not enough. This book is an honest and relatable look into the day-to-day realities of leading Agile teams—filled with hard-earned lessons, internal conflicts, and war stories from the trenches of IT service delivery.
Many Agile professionals find themselves constrained by process rigidity, unable to adapt to real-world pressures. These topics are more relevant than ever, as enterprises demand agility in outcomes, not just ceremonies. This book offers timely guidance on how to focus on execution while remaining Agile in spirit. Structured as a series of thematic chapters based on real events and personal "confessions," each section ends with reflection questions and actionable takeaways. The narrative style guarantees engagement, while the learnings guarantee impact.
Unlike traditional guides that idealize Agile or limit themselves to theory, Confessions of an IT Scrum Master acknowledges the gray areas and equips you to navigate them with confidence. Its confession-style storytelling is not only compelling but also deeply authentic—because it's written by someone who's lived it.
What You Will Learn
The practical gaps between Agile theory and enterprise execution
How internal conflicts (e.g., architect vs. Scrum Master) affect delivery
Techniques to focus on value delivery in process-heavy environments
· Who This Book is For
Intermediate Agile professionals
Contents
Confession #1: I Didn't Plan on Becoming a Scrum Master.- Confession #2: Internal Conflict - The Architect vs. The Scrum Master.- Confession #3: When the Code Breaks, So Does the Team.- Confession #4: Stakeholders Think Agile is a Miracle Cure.- Confession #5: The Myth of Requirements (or Lack Thereof).- Confession #6: When Agile Meets Fixed Deadline.- Confession #7: Scaling Nightmares - Nexus, Chaos, and Customer Challenges.- Confession #8: How I Learned Velocity Isn't Everything.- Confession #9: Customer Feedback in IT - The Forgotten Metric.- Confession #10: Siloed Teams, Stalled Delivery.- Confession #11: The Human Side of Scrum - People Skills that Make or Break Teams.- Confession #12: Surviving Meetings That Should Have Been Emails.- Confession #13: The Dire Consequence of Ignoring Toxic Culture.- Confession #14: You Can't Hold Everyone Accountable All the Time.- Confession #15: When Teams Don't Play as One.- Confession #16: Agile for Lean Tech Teams.- Confession #17: Execution vs. Process - The XP Influence.- Confession #18: When Agile Rules Bend (and Break).- Confession #19: The Frameworks Are Coming - Don't Panic.- Confession #20: Is Agile Forgetting Its Roots? Learning from Toyota.
