Scaled Professional Scrum and Nexus – The Definitive Guide

Comments 13

1. Himadri_1983

   1st November 2020 at 1:41 pm

   Hi Simon,

   I am not sure why I am unable to find my query : I am again posting by creating my account.

   Query 1: Nexus is based on Scrum and in Scrum , Scrum Team discuss quality and adapt its DOD as it matures,

   What about the adaptation of the DOD at nexus level – who involved and how that is being adapted?

   Query 2: My teams has faced many times , where there is huge dependency between 2 teams and what we should focus on ? Is it merging the two teams to collaborate or focus on more Product backlog refinement to reduce the dependency ?

   Thanks!

   Reply
   1. Post
      Author
      Simon Kneafsey

      2nd November 2020 at 12:09 pm

      Hi,

      Some thoughts for you on your 2 queries:

      Query 1

      The Scrum Teams in the Nexus are responsible for this.

      The Nexus Integration Team may play a supporting/guiding role when it comes to adapting the Defintion of Done for a Nexus.

      Query 2

      You could reform the teams. Although there will be a price to pay for this, it could be appropriate.

      You could resequence the work so that the dependency is not brought into the Sprint. Team 1 completes some work in 1 Sprint and then team 2 continues in the next Sprint and the dependency is less likely to have an impact on team 2 this way.

      Reply
      1. Himadri_1983

         2nd November 2020 at 12:14 pm

         Thanks Simon for your valuable input and advise .. it really helps. Thanks !

         Reply
      2. Himadri_1983

         2nd November 2020 at 12:33 pm

         Just to ensure if I correctly interpret the first query : The NIT is responsible for nexus DOD , but for adaptation in later time it should be by Scrum Teams and NIT may guide about the same. and This should be part of nexus retrospective improvement to adapt DOD.

         Please correct me in case I have misunderstood!

         Thanks Simon!

         Reply
         1. Post
            Author
            Simon Kneafsey

            2nd November 2020 at 12:41 pm

            Here is what the Nexus Guide says about this:
            “The Nexus Integration Team is responsible for a definition of “Done” that can be applied to the Integrated Increment developed each Sprint”

            Reply
            1. Himadri_1983

               2nd November 2020 at 1:46 pm

               Thanks Simon!
2. Xiaojing

   5th December 2019 at 9:22 am

   Hi Simon,

   Thanks for writing so many good blogs, I read all the articles list in this blog, I gained a lot, especially the “Should We scale?”, because I have seen a lot project try to scale without considering if they reach a good condition to scale, it cost a lot of wastes in the team. I will share your blog with my stakeholders as well 😉

   Thanks,
   Xiaojing aka Sarah

   Reply
3. carryyou

   4th January 2019 at 6:09 am

   Thank you for your info. Is there any update for:

   Coming soon: Major Differences Between The Scrum Framework and The Nexus Framework
   Coming soon: Comparison of Scaled Professional Scrum And Nexus To Other Scaling Approaches

   I’m looking forward to them.

   Reply
   1. Post
      Author
      Simon Kneafsey

      4th January 2019 at 3:21 pm

      Hi,

      They are both on the Product Backlog but still some way off so I don’t have a date for you at this point.

      Regards

      Simon

      Reply
4. Elton Melo

   18th December 2016 at 3:17 pm

   Very good indeed! I’m curiously waiting for “Major differences between Scrum and Nexus”; and also for “Comparison of SPS/Nexus to other approaches”.

   Reply
5. Pradip Ghosh

   3rd March 2016 at 6:28 pm

   Hi Simon when you are writing the remaining 2 most important blogs of SPS & Nexus. 🙂

   Reply
   1. simonkneafsey

      4th March 2016 at 1:56 am

      Hi Pradip,

      As soon as I can. I don’t have a date yet unfortunately.

      Regards

      Simon

      Reply
6. Pradip Ghosh

   10th December 2015 at 8:27 am

   Simon great approach & effort in popularizing Scaled Professional Scrum and Nexus.

   Reply