Before you pick up that next story (in Scrum)

Before you pick up that next story (in Scrum)

Have you ever heard a team member say this during a sprint: "I have finished my work, now what?" - It's easy to have this conversation go sideways. What if we can have a guided discussion? (hint: there is a way.)

 I learned a tip from Joel Bancroft-Connors at Agile Open Northwest that I'd like to share.

 Help the team member self-reflect with the following flow of questions (instead of picking up new stories while the sprint is in flight):

  1. Can I help someone with a current task?
  2. Can I fix a bottleneck in the workflow?
  3. Can I work an unstarted task on an in-progress story (that I can finish in the sprint)?
  4. Can I fix some technical debt?
  5. Can I learn something?
  6. Can I start a new story in the sprint backlog (that I can finish in the sprint)?
  7. And remember that the team trusts you to make the right decision



Joel Robinson

I help organizations and teams evolve to identify and deliver customer value collaboratively, incrementally and sustainably.

8 年

Oh, and the team-owned sprint backlog is a pretty standard Scrum concept, isn't it? I like to keep everything unassigned (e.g. team-owned) until it gets pulled into progress which helps reinforce the shared ownership mentality.

Joel Robinson

I help organizations and teams evolve to identify and deliver customer value collaboratively, incrementally and sustainably.

8 年

Funny, I shared a very similar list in the form of an algorithm with my team this week. I like the bottleneck removal idea, I didn't think of it. I did include fixing a bug as possibility.

回复
Arlo Belshee

Fractional CTO & Advisor, Distinguished Engineer | Ex Microsoft | Legacy Code & DevOps

8 年

Are you assuming that each individual is assigned stories at the beginning of the sprint, and thus picking up a story means adding something to the sprint? Because if so, I'd challenge that assumption. What does that cause for shared work? For handouts? For informal and emergent collaboration? What if you started each sprint with a set of stories owned by the whole team? And never assigned them to individuals. instead of putting the individual at the center, put the work at the center, and then several times per day each person finishes some chunk of work and asks where is the next most effective piece of work to do? What different results does that make become natural and automatic?

Joel Bancroft-Connors

Sustainable Value Expert | Product Delivery Coach | More Efficient | More Effective | Certified Scrum Trainer | Passionate about making the world a better place

8 年

Thank you, I'm honored.

回复
Ahmed Avais

Digital Transformation Leader | Chief of Staff Liaison | Business Agility Coach | Agile Project Manager | Modern Product Manager

8 年

Joel Bancroft-Connors - couldn't find a way to mention you inline in the article - wanted to say thank you for sharing the original idea

回复

要查看或添加评论,请登录

Ahmed Avais的更多文章

  • The Coach as a Mirror

    The Coach as a Mirror

    I have been thinking (uh oh) about interactions between leaders and coaches. Why is it that so many people want a quick…

    7 条评论
  • Framing Business Agility through Looney Tunes

    Framing Business Agility through Looney Tunes

    The Road Runner and Wile E. Coyote are cartoon characters from Looney Tunes released in 1949 by Chuck Jones.

    3 条评论
  • Nanny McPhee as an Agile Coach

    Nanny McPhee as an Agile Coach

    Recently, I heard an enterprise agile coach express their opinion on the difference between an agile coach and a scrum…

    4 条评论
  • Playing Poker at a Euchre Party

    Playing Poker at a Euchre Party

    I recently had the pleasure of attending the inaugural Agile Professional Learning Conference in Chicago. Doc Norton…

    2 条评论
  • In Praise of ScrumPLOP

    In Praise of ScrumPLOP

    It seems like there's a bit of Scrum-hate going on. As if something is fundamentally wrong with it.

    16 条评论
  • It was agile while it lasted

    It was agile while it lasted

    If observing patterns is your thing, you may notice a strange pattern emerge in agile case studies. Put simply, that…

    11 条评论
  • Getting better with an experiment mindset

    Getting better with an experiment mindset

    Every new product and project undertaking is by definition an experiment worthy of pursuit. We hope that this endeavor…

  • Things that kill trust (in teams)

    Things that kill trust (in teams)

    Yanking people Yanking budget Not letting people make their own mistakes Punishing mistakes Cancelling the project at…

  • The need for visual communication in software

    The need for visual communication in software

    A quote worth repeating: “Ask somebody in the building industry to visually communicate the architecture of a building…

社区洞察

其他会员也浏览了