Forums

By posting to our forums you are agreeing to the Forum terms of use.
Scrum - TFS - Tasks - Not being updated timely
Last Post 29 Jan 2014 11:10 AM by Sandeep Kamat. 6 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
whyato8
New Member
New Member
Posts:1
whyato8

--
30 Sep 2013 04:14 AM
    I am currently doing the role of a scrum master. The team is using TFS to track the backlog and they break down the PBI's into multiple task's and assign the hours against each. Now, the team is achieving the sprint goal but they are not updating their task state (WIP, Done etc) and reducing the hours which are left on that. It looks like they keep on forgetting that or may be its not something worth it for them. I have to remind them at times to update that and its done then. So, I just wanted to understand what is the most effective way so that team keeps on updating tasks daily, so that everyone is updated with how much work is remaining?
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:562
    Ian Mitchell

    --
    30 Sep 2013 04:31 AM
    Most standups happen around a Scrum board where it should be obvious if task states are not being updated or burndown looks poor. If you're using TFS rather than a physical board, you should have a screen nearby with this on. Then you can spend 5 minutes before the standup going round the developers and asking them if they have done their preparation.

    Remember to coach the team that board updates should be pull driven and not pushed to the next state.
    Sanjay Saini
    New Member
    New Member
    Posts:78
    Sanjay Saini

    --
    30 Sep 2013 05:39 AM

    UrbanTurtle is a good tool which gets integrated with TFS for showing the tasks movement. It works like a scrum board.

    Project it during your standup meeting.

    Cheers
    Sanjay
    Viva
    New Member
    New Member
    Posts:1
    Viva

    --
    02 Oct 2013 10:02 AM
    You can always rely on 3rd party tools, or you can have iterative approach, where you help others to adjust by small steps like - ask everyone to update their current work state at the end of daily stand up meeting (if doing those). Then after few weeks ask to update in the day end. And continue till you reach behavior where everyone will update their work before asked.
    Fletch
    New Member
    New Member
    Posts:1
    Fletch

    --
    03 Oct 2013 01:09 PM
    Hey,

    Could you comment further on this idea:

    " Remember to coach the team that board updates should be pull driven and not pushed to the next state.
    Subject"

    I like the term "pull driven" but not exactly sure what you mean.

    Thanks,
    TF
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:562
    Ian Mitchell

    --
    03 Oct 2013 03:11 PM
    "Pull driven" means that work flows through the system as a result of demand. At each stage in the value chain, somebody should actually want the prior output as an input and be able to use it. This stops waste accumulating.

    Pushing work leads to the buildup of excess stock on hand which is wasteful.
    Sandeep Kamat
    New Member
    New Member
    Posts:21
    Sandeep Kamat

    --
    29 Jan 2014 11:10 AM
    If your team is breaking down the stories into tasks and also estimating them that that is great. If they are also meeting the sprint goes and keeping the stakeholders happy at sprint review what more can you ask for.
    I would update the tasks myself based on the daily stand-ups. If the above paragraph is true for your team than I would calculate the number of hours needed to be burned down each day and ....
    You are not authorized to post a reply.


    Feedback