Forums

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Activities for improving backlog refinement that work remotely
Last Post 22 May 2013 09:00 PM by Sanjay Saini. 7 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Ryan Cromwell
New Member
New Member
Posts:89
Ryan Cromwell

--
16 May 2013 05:16 AM
    I'm working with a highly distributed team that struggles with backlog decomposition; breaking down big things. Much of this comes from not understanding the business and that's being resolved through industry training, etc.

    I'm curious, though. Are there retrospective or training activities that you've found helpful in learning how to decompose that might work well for a distributed team? Something that works well in a collocated scenario that might be modified.

    I understand all of the problems with distributed teams and that this causes problems. I'm not interested in that particular discussion being repeated.
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1685
    Ian Mitchell

    --
    17 May 2013 12:34 AM
    Hi Ryan

    First let's consider why big PBI's are a problem. Usually it's because they cause uneven flow rate, the delayed delivery of value, and stand a higher risk of becoming impeded than smaller ones. You can therefore try to get the team to think in terms of where a work item is likely to become blocked (e.g. by needing something from another team or stakeholder), and encourage them to author smaller items that "wrap" these blockages. Sometimes a user story can be phrased in terms of delivering value to those other stakeholders or teams.

    Another option is to play hardball and adopt one point = 1 work item. I've used this in the past to encourage the authoring of smaller PBI's, It becomes better the more of them there are, because any residual sizing discrepancies tend to average out over the course of a Sprint.
    Alice Menezes
    New Member
    New Member
    Posts:39
    Alice Menezes

    --
    18 May 2013 12:33 AM
    Yes "Agile Distributed- http://www.agiledistributed.com/ " helps organizing distributed teams co ordinate work efficiently
    Ryan Cromwell
    New Member
    New Member
    Posts:89
    Ryan Cromwell

    --
    19 May 2013 07:34 PM
    Thanks Ian, do you have any **activities** that you find useful in teaching teams how to do what you're suggesting that might work for distributed teams? I have plenty of experience working through these challenges with collocated teams, but again - this isn't one of those situations.
    Ryan Cromwell
    New Member
    New Member
    Posts:89
    Ryan Cromwell

    --
    19 May 2013 07:35 PM
    Alice - were should I look on this website for activities. Thanks.
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1685
    Ian Mitchell

    --
    20 May 2013 03:23 AM
    Hi Ryan

    Unfortunately not, though I'd be strongly disposed towards using Google Docs as the basis for a distributed approach. There's an article on Pragmatic Agilist which I think is a good starting point:

    http://pagilista.blogspot.co.uk/201...-time.html
    Ryan Cromwell
    New Member
    New Member
    Posts:89
    Ryan Cromwell

    --
    22 May 2013 05:37 PM
    Thanks Ian. Certainly has some good ideas.
    Sanjay Saini
    Basic Member
    Basic Member
    Posts:156
    Sanjay Saini

    --
    22 May 2013 09:00 PM
    Hello Ryan

    It is good that you have started with the industry/domain training to team. Another thing I would like to add is that - as a standard, teams should spend at-least 10% of their sprint time in grooming for future sprints which may be more for your team, are you giving your team enough time for grooming and understanding the backlog? Also human brain understand the visual things earlier as compared to the textual so I would recommend to use mock-ups, HTML screens for your user stories.

    Also don't get frustrated and communicate with your team as much as you can.

    Cheers
    Sanjay
    You are not authorized to post a reply.


    Feedback