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.

When do the stakeholder and the Scrum team meet?
Last Post 24 Jul 2014 11:13 PM by nikos batsios. 8 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
Topic is locked
Author Messages Resolved
Umberto Mathias Iagushi Ferreira
New Member
New Member
Posts:4
Umberto Mathias Iagushi Ferreira

--
07 Mar 2014 02:45 AM
    Is it true that the Sprint review is the only time that the stakeholder and the Scrum team Should meet?
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1556
    Ian Mitchell

    --
    07 Mar 2014 07:50 AM
    What do you think are the arguments for and against limiting stakeholder involvement in this way? Consider how the role of the Product Owner might have a bearing on this.
    Francois SALAZAR
    New Member
    New Member
    Posts:3
    Francois SALAZAR

    --
    22 Jun 2014 02:58 AM
    Hi,

    I answered 'No' because
    1. Transparency means that everyone is authorized to meet an discuss with the Team
    2. The ScrumMaster has to help those outside the team understand which interactions are good or not
    3. Meet does not mean that there will be commitment taken without the PO
    3. Stakeholder represent a wide variety of parties and not only management. The Dev Team has to meet providers, consultants, trainers, Central IT guys ...

    Bye
    Garin Reyneke
    New Member
    New Member
    Posts:21
    Garin Reyneke

    --
    22 Jun 2014 07:07 AM
    1: SM protects the team from disruptive influences including Stakeholders
    Scrum meetings are designed to eliminate waste from excess meetings
    2: The meetings are prescribed for good reason, the SM should help those outside the team understand why they ARE the better meetings within the framework and use them to keep Scrum optimised
    3: The PO cannot be excluded from any meeting dealing with deliverables , no one but the PO can refine the backlog based on feedback from stakeholders and then help the team keep value optimised. These interactions should be enough to keep the team informed to only relevant changes that affect value priority or risk to sprint goals. Outside of the sprint planning this is a team decision to decide how much PO input they might require to affirm and ensure that the items are still in focus in terms of value, (emerging work could require the team and PO to negotiate on what will be realistic for the team to demonstrate as working/shippable)
    4: SM- ensures inspection of progress and/or interaction from any party doesn't cause a loss of focus or velocity and add risk.
    Any Required inputs from vendors or additional consultants should (IMO) be factored in during sprint planning, refining the sprint backlog is a team decision. If other specialist parties that can't be part of a dev team , are required to remove impediments , hardware failure for example.. The SM should ensure it's done with minimal disruption to the team. If the disruption is going to completely endanger the sprint goal, then the PO should be involved to decide if the sprint is terminated or the sprint goal needs to be reduced to a set of backlog items such as refining documentation ( which could be the entire focus of a sprint if the DoD is defined as such) and keep the sprint intact...

    Ludwig Harsch
    Basic Member
    Basic Member
    Posts:272
    Ludwig  Harsch

    --
    23 Jun 2014 11:18 PM
    The Review is the only event in Scrum where Stakeholders and the Scrum team meet.
    I agree that it should not be forbidden to talk to each other - that would be anti-agile.
    However, if you have additional meetings with stakeholders and the Scrum team (not only the PO, not only the SM, but the whole Scrum team!) this is a process smell.
    What you can do: Find out what is being achieved in this meeting, and what value is generated by this. Eliminate the things without value and assign the others to the appropriate Scrum events. Usually there should be nothing remaining.
    Jeroen Cranendonk
    New Member
    New Member
    Posts:4
    Jeroen Cranendonk

    --
    11 Jul 2014 02:44 AM
    Does anyone have any more thoughts on this? I've looked at all that's said, and I'm still unsure.
    Note: In the context of the PSM1 assessment, since that's what most here are looking at, so Spring Guide is the bible ;)

    Mind, I'm not sure about the question either, which might be significant, does "the stakeholder and the Scrum team Should meet" (btw., Scrum team, not Dev. team) mean that the whole team actually goes into a meeting, or do informal meetings between single team members count? If it's the first case, I think I'd say yes, since the reason for having the scrum events is so that other meetings are not necessary (to prevent waste). In the latter case I'd say no, because it makes sense to me for the PO to meet with stake holders outside of the review meeting (to clarify things on request of the PO for example, or to get informed about market changes), and I would think even the Development team might ask a stakeholder to visit, if they possess domain knowledge they need (but then, mayby it's not the role stakeholder, but outside expert?)

    As you can see, I find it complicated ;)
    michael
    Basic Member
    Basic Member
    Posts:132
    michael

    --
    20 Jul 2014 10:17 AM
    My vote is on the yes they can, based off the services of the scrum master to the Organization.

    Scrum Master Service to the Organization
    The Scrum Master serves the organization in several ways, including:
     Leading and coaching the organization in its Scrum adoption;
     Planning Scrum implementations within the organization;
     Helping employees and stakeholders understand and enact Scrum and empirical product development;
     Causing change that increases the productivity of the Scrum Team; and,
     Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.


    If the SM is helping employees and stakeholders understand scrum via coaching.
    They would be able to meet outside a review would be a valid comment.
    Could any PST say what the logic is and what the scrum.org take is on this question?
    nikos batsios
    New Member
    New Member
    Posts:11
    nikos batsios

    --
    24 Jul 2014 07:05 AM
    hello all,
    clearly described in the scrum guide that sprint review is the event where scrum team and stakehoderes meet and collaborate. there are no other events that are required for stakeholders collaboration. PdO could invite "other people" in sprint planning to provide "technical" or "domain" advide. i am not seeing these people as "stakeholders"!. concluding, i could say that yes...sprint review is the event to meet stakeholders!
    nikos batsios
    New Member
    New Member
    Posts:11
    nikos batsios

    --
    24 Jul 2014 11:13 PM

    Posted By nikos batsios on 24 Jul 2014 12:05 PM
    hello all,
    clearly described in the scrum guide that sprint review is the event where scrum team and stakehoderes meet and collaborate. there are no other events that are required for stakeholders collaboration. PdO could invite "other people" in sprint planning to provide "technical" or "domain" advide. i am not seeing these people as "stakeholders"!. concluding, i could say that yes...sprint review is the event to meet stakeholders!


    correction: it's not the PdO but rather the development team that could invite other people to attend the sprint planning...
    Topic is locked


    Feedback