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.

Integration of Increments
Last Post 08 Sep 2013 04:21 AM by Sanjay Saini. 4 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Shirley Santiago
New Member
New Member
Posts:7
Shirley Santiago

--
19 Aug 2013 01:21 AM
    Hi,

    When many Scrum teams are working on the same product, should all of their increments be integrated every Sprint?

    Thanks.
    Michael Mai
    New Member
    New Member
    Posts:4
    Michael Mai

    --
    19 Aug 2013 02:41 AM
    Yes they should.

    Let's think about, if they don't:
    - The state of the product is unclear (due to not yet discovered problems that will arise during integration and complete product increment tests)
    - The PO does not have a clue whether the THING he/she was presented is potential shippable
    - It is not transparent to the organization what the next reasonable steps are (if there difficulties due to integration, the next steps would be rather clear, but not integrated - its only wishful thinking)

    All this sad, there are some occasions where integrating each sprints is futile:
    - If the sprint is abnormally terminated by the PO
    - If testing gear needed to verify a potential shippable product increment is not as available as it should -> clear impediment
    - Integration environment is not accessible -> clear impediment
    - Integration procedure is to complicated to do every sprint -> clear impediment, and yes pain is sometimes a good teacher
    - The other teams are working on different products (I stress: not components of the same product) that are highly integrated into your team's work -> a nasty impediment

    Don't take "too much effort", "too much time", "too high cost" easy, see it as an impediment and a leverage to act as a Scrum Master by taking responsibility in removing these impediments.

    I hope, this answers your question.
    Michael
    Shirley Santiago
    New Member
    New Member
    Posts:7
    Shirley Santiago

    --
    19 Aug 2013 03:51 AM
    Thank you Michael. I appreciate your explanation.
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1556
    Ian Mitchell

    --
    19 Aug 2013 05:31 AM
    Each increment released by each Scrum team at the end of a Sprint must be potentially shippable. This implies that they must not only be integrated, but also subjected to whatever system integration, UAT, or pre-release testing is needed.

    That's a tall order. There is controversy at the moment about the use of enterprise release frameworks (e.g. SAFe), which dilute this standard somewhat.
    Sanjay Saini
    Basic Member
    Basic Member
    Posts:151
    Sanjay Saini

    --
    08 Sep 2013 04:21 AM

    I would say the integration should happen multiple times during the sprint as and when required. We have eight teams working on the same product and we have multiple integration environments. Dev Int - where the integration happens twice a day, QA Int - where the integration happens twice in a week and UAT - where integration happens every sprint.

    It doesn't mean we have to release all eight team's feature every sprint, we have a mechanism which allows us to release the selected feature every sprint, if required.

    Cheers
    Sanjay
    You are not authorized to post a reply.


    Feedback