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.

Engineering Tools for Dev Team
Last Post 06 Mar 2016 12:36 PM by Kat Ocol-Marasigan. 7 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Vinodh Gurusamy
New Member
New Member
Posts:1
Vinodh Gurusamy

--
18 Nov 2013 03:46 AM
    I came across a question in PSM1 Assessment about Non availability of Engineering tools for Dev team in the middle o the sprint which is impediment to progress towards the Sprint Goal.

    Should Scrum Master should Dev Team or Dev team stop working in the Sprint.

    Thanks.
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1556
    Ian Mitchell

    --
    18 Nov 2013 04:27 AM
    If the non-availability of tools threatens the Sprint Goal, the Development Team should collaborate to try and resource them or to find a work-around. The Scrum Master should support them as far as possible in this, so that the team can focus on development activities and on meeting the Sprint Goal.

    If the problem cannot be removed, such that neither the tools can be obtained and a work-around is not possible, then the Product Owner should be notified and alternative plans should be agreed. In exceptional circumstances the Sprint may need to be cancelled, and any value incurred to that point should be secured and released.
    Nitin Khanna
    New Member
    New Member
    Posts:94
    Nitin Khanna

    --
    18 Nov 2013 08:46 AM
    Also assume for a moment that the PO is unavailable.

    Keep going -- do the best you can and also discuss this at the Retrospective.

    P.S. Did the question explicitly state this as an impediment?
    Siva Chandrasekaran
    New Member
    New Member
    Posts:1
    Siva Chandrasekaran

    --
    03 Mar 2016 07:44 AM
    Do you refocus the sprint on establishing DT infrastructure or adjust the Definition of done to deliver the increment? what would you do in this situation as SM.
    Steven Zachary
    New Member
    New Member
    Posts:8
    Steven Zachary

    --
    03 Mar 2016 10:48 AM
    I think the key point from this question is when/if you engage the PO. How much does the team engage a solution before they engage additional support. Self-management.
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1556
    Ian Mitchell

    --
    03 Mar 2016 11:36 PM
    > Do you refocus the sprint on establishing DT
    > infrastructure or adjust the Definition of done
    > to deliver the increment? what would you do in
    > this situation as SM.

    If an adjustment of the DoD is being floated as an option, it's really a question of what the Development Team should do. They are the ones who would be held accountable for any technical debt that is subsequently incurred by the increment. They don't have to accept that responsibility at all, and sprint cancellation might weigh as a serious option. Ken Schwaber has recently proposed the idea of "scrumbling" outside of sprints in order to rectify the situation before sprinting is allowed to recommence.
    Dipankar Datta
    New Member
    New Member
    Posts:9
    Dipankar Datta

    --
    05 Mar 2016 04:20 AM

    If an adjustment of the DoD is being floated as an option, it's really a question of what the Development Team should do. They are the ones who would be held accountable for any technical debt that is subsequently incurred by the increment. They don't have to accept that responsibility at all, and sprint cancellation might weigh as a serious option. Ken Schwaber has recently proposed the idea of "scrumbling" outside of sprints in order to rectify the situation before sprinting is allowed to recommence.


    Interesting point on "Scrumbling", Ian. I wasn't aware of this concept & will try to find out. However, "outside of sprints" is a red flag for me. It seems like a possible "escape route" for scrum teams to push unresolved issues outside their sprint scope & responsibility/accountability. It also sounds similar to so called "hardening sprint". I might be mistaken as I haven't gone through the the concept except what I read above.

    There is concept of "swarming" in agile, which may be one way to tackle nonavailability of tools issue.
    Kat Ocol-Marasigan
    New Member
    New Member
    Posts:5
    Kat Ocol-Marasigan

    --
    06 Mar 2016 12:36 PM
    I know this is a hypothetical question since it's part of the PSM1 exam but will the business actually allow an acceptancej of the project if there's a lack of dev infrastructure?
    You are not authorized to post a reply.


    Feedback