We often speak about the basics of scrum and rarely get into the problems and I wanted a session that represented the “next steps” after deciding that this Scrum thing was a good idea. I will, hopefully, be hitting this session at those that already understand Scrum, but are looking for a little implementation knowledge and guidance before they get stuck in.
UPDATE: [Register for Scrum-damentals on 17th February 2012 ]
UPDATE: [Join Scrum-damentals Live at 8:00 am UTC-8 (that’s like in less than 10 minutes]
UPDATE: I have added both a link to the PDF and the recording below. The sound is a little tinny as the room I was in was a echo box, but hey…you can’t have everything.
Download: Training - [Coffee] - Scrum-damentals 2012.pdf
[screencast url=“http://www.screencast.com/t/zJYxrnatZ0" width=“640” height=“360”] Webcast: The Scrum-damentals is just beyond the basics
As this is an open session it will still be busy (they always are) and there will be only a little room for questions. But I do want to try to spend more time on the complexities so most of my presentation and discussion is on the challenges and strategies of playing the game that is Scrum:
- What are the basics?
- What are the challenges?
- What are the strategies?
While I will try to cover many aspects of individual problems that are raised, there is usually a myriad of them so feel free to comment below with anything that does not get answered tomorrow.
Scrum is the most adopted and recognized agile methodology framework. However, there are still challenges to Scrum adoption. This Event will dive into several Scrum adoption pitfalls and how an organization can avoid them. In particular, we will highlight some of the proven practices that have worked for diverse sets of teams. We will also leave time for questions and encourage attendees to bring your most challenging problems. -Extract from Scrum-damentals on 17th February 2012
Make sure that you sign up as I am looking forward to this one.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Coffee Talk: Introduction to Scrum - webcast event this Friday!
Learn the basics of Scrum, including its key roles and processes, with practical tips for adoption. Ideal for those new to agile or seeking …
Are you doing Scrum? Really?
Explains recent changes to Scrum aimed at reducing rigidity, clarifying core practices, and providing a checklist to help teams assess if …
Mastering Scrum: Key Insights on Definition of Done, Spikes, and Managing Ad Hoc Work
Explains key Scrum concepts: distinguishing Definition of Done from acceptance criteria, using spikes vs. refinement, and strategies for …
Scrum is hard to adopt and disruptive to your organisation
Explains why adopting Scrum is challenging and disruptive, highlighting the need for training, mentoring, and dedication for successful …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.