June 12

Latest Posts

  • Elevating your Scrum Board to Professional Kanban and Why It Matters
    Scrum is a conversation framework. Kanban is a framework for asking the right questions sooner rather than later. Combining the two sets the stage for a Scrum team to reach new heights of Throughput in value delivery.
  • Scrum Talk Daily # 25
    While “Definition of Done” appears in the Scrum Guide, you won’t find “Acceptance Criteria”. What’s the difference?
  • Scrum Talk Daily # 24
    A working agreement? I like to call it an “Agreed Approach to Professionalism”.
  • Scrum Talk Daily # 23
    If it doesn’t meet the Definition of Done, it isn’t an Increment.
  • Scrum Talk Daily # 22
    Have you ever spent a bunch of time on work only to be “informed” that it’s the wrong direction because it wasn’t clear, to begin with?
  • Scrum Talk Daily # 21
    An emergent, ordered list of what is needed to improve the product and the single source of work undertaken by the Scrum Team.
  • Scrum Talk Daily # 20
    If we don’t take action, we deviate more and more?
  • Scrum Talk Daily # 19
    Can you adapt without inspection? Would inspection without adaptation be considered pointless?
  • Scrum Talk Daily # 18
    Yesterday we talked about Empiricism being the foundation of Scrum. So where does transparency come in?
  • Scrum Talk Daily # 17
    Are the three pillars of Transparency, Inspection, and Adaptation being used by your team?
  • Scrum Talk Daily # 16
    Ever heard of “test early, test often”? What about “Community Driven Iteration”? If not, here’s the nutshell…
  • Daily Scrum Talk # 15
    This is the meat and potatoes of improving the team and where teams need to concentrate to exercise the 3 pillars of the empirical process: Transparency, Inspection, and Adaptation.
  • Daily Scrum Talk # 14
    How often are you making contact with users? During your Sprint Reviews, are only stakeholders giving feedback on your increment?
  • Scrum Talk Daily # 13
    A day’s plan? Remember, back in Sprint Planning, the Developers themselves broke down Product Backlog items into work items of one day or less…
  • Scrum Talk Daily # 12
    The Developers plan the work during Sprint Planning, not management?
  • Scrum Talk Daily # 11
    The Sprint is the container for all other Scrum events. All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints.
  • Scrum Talk Daily # 10
    I love this one. Courage wraps up the Core Values nicely because I believe in ties into other values.
  • Scrum Talk Daily # 9
    How many times have you had a job where your boss is hovering over your shoulder?
  • Scrum Talk Daily # 8
    “The Scrum Team and its stakeholders are open about the work and the challenges.” What does this mean?
  • Scrum Talk Daily # 7
    A Scrum Team’s primary focus is on the work of the Sprint to make the best possible progress toward their goals.