home.social

#scrummaster — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #scrummaster, aggregated by home.social.

fetched live
  1. 🪞 Even ScrumMasters fall into anti-patterns. The one I see most: the Scrum Parent, solving every problem for the team instead of letting them try first. It looks like helpfulness. It quietly damages the system the same way MicroManagement does, by taking self-organization away.

    Close cousin: Facilitator only, running the meetings but never coaching.

    Which is closer to your default: Scrum Parent, or Only Facilitation? 20+ years ago mine was Scrum know-it-all.

    #ScrumMaster

    agilepainrelief.com/glossary/s

  2. 🚧 A Developer mentions the same work four days running and still says "no blockers." Usually the team just doesn't share a definition of what an impediment is.

    Working definition: anything that slows progress toward the Sprint Goal. Bad connection, interruptions, waiting on another team, broken builds, slow decisions, a poorly understood PBI. All impediments.

    A trick: swap "impediment" for "slowdown," easier to admit. Then check the board for items stuck in one state for days.

    An impediment you can't name is one nobody can remove.

    #Scrum #ScrumMaster

    agilepainrelief.com/glossary/i

  3. Ein sehr sehr guter Text über "Code Review", der in Scrum Teams oft eine eigene Spalte auf dem Scrum Board darstellt.
    Oft ein Diskussionsthema in Retrospektiven. Oft fühlt es sich nervig an. Jetzt kommt AI ins Team. Wie kann es helfen? Und warum machen wir das eigentlich alles nochmal?

    newsletter.getdx.com/p/what-ar

    #AgileAI #Scrum #Agile #ScrumMaster #AgileCoach #Retrospektive #CodeReview

  4. Was sind eure Erfahrungen mit Formaten wie "Agile Tapas"?

    Agile Tapas: kurze fokussierte "Knowledge-Sharing" Sessions, die sich mit 1 Aspekt aus der Agilen Arbeitswelt beschäftigt.

    #AgileTapas #Agile #ScrumMaster #AgileCoach

  5. 🤖 Good news for ScrumMasters: you're safe.

    I went looking for useful Claude skills for ScrumMasters, Product Owners and Agile Coaches. What's out there: run the Daily Scrum as a progress summary (it even had a token budget), plan Sprints from capacity and velocity, run Retrospectives where the LLM does all the thinking, turn BDD (a conversation tool) into a rigid spec generator.

    Automating the output, skipping the thinking.

    #ScrumMaster #AIinSoftwareDevelopment

  6. 🤝 Building a Working Agreement? The ScrumMaster coaches, not leads. Canvass the team first on what matters: Daily Scrum time, respect, phones, equal voice.

    Start with a check-in, then use a format where every voice is heard (I like 1-2-4 with the Decider Protocol). When someone says no, they suggest something better.

    Every few Sprints, ask: is this still our Working Agreement?

    #Scrum #ScrumMaster

    agilepainrelief.com/blog/team-

  7. 🚦 Most teams treat Definition of Ready as a checklist to enforce. Hold it lightly instead.

    If items get stuck mid-Sprint, a Definition of Ready can help, but only cover the details actually causing problems now. As the team matures, make it thinner. The failure mode: it becomes a dumping ground for every little problem the team ever had.

    Does your "Ready" gate reduce delay, or just hide it earlier?

    #Scrum #ScrumMaster

    agilepainrelief.com/glossary/d

  8. ✅ The 2020 Scrum Guide made Definition of Done a formal commitment. Done is not optional: it's the team's promise about what "complete" means.

    The hardest problem is pressure to deliver more. As it builds, teams compromise on Done. Short term it looks fine, they get more finished. Long term the bugs offset the value, and each shortcut accumulates as technical debt that slows future work.

    Only take on work you can bring to truly Done.

    #Scrum #ScrumMaster

    agilepainrelief.com/glossary/d