Planning a sprint after reduced team strength

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












We have seven people team and their running velocity is ~50 points(2 weeks sprint). Now due to change in business focus, we have to reduce team size from 7 to 4.



How do we plan current sprint? According to running velocity or let the team guess how much they can deliver.










share|improve this question

























    up vote
    1
    down vote

    favorite












    We have seven people team and their running velocity is ~50 points(2 weeks sprint). Now due to change in business focus, we have to reduce team size from 7 to 4.



    How do we plan current sprint? According to running velocity or let the team guess how much they can deliver.










    share|improve this question























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      We have seven people team and their running velocity is ~50 points(2 weeks sprint). Now due to change in business focus, we have to reduce team size from 7 to 4.



      How do we plan current sprint? According to running velocity or let the team guess how much they can deliver.










      share|improve this question













      We have seven people team and their running velocity is ~50 points(2 weeks sprint). Now due to change in business focus, we have to reduce team size from 7 to 4.



      How do we plan current sprint? According to running velocity or let the team guess how much they can deliver.







      scrum agile software-development






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 hours ago









      ssharma

      3099




      3099




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote













          If you reduce a team from 7 to 4, especially if the reason is something outside the team, the best course of action is probably to treat this as a completely new team. People will need to change into new roles, find a new way of working together, cover fresh weaknesses caused by those leaving, find out who is in charge of what, and all the other problems that a new team runs in to.



          Cutting a team in half shouldn't be handled in a "business as usual" type of way; it's a pretty traumatic experience for the team, especially if they've been working together for a while. You could go all the way and run a new team introduction, but at the very least you should give them some time to reform and whatever velocity you have from the previous team can probably go out the window.



          Doing whatever it is you normally do when planning with a new team will likely give the most reliable results. (The most reliable possible, that is. They probably won't be very reliable regardless.)






          share|improve this answer




















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "208"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            noCode: true, onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fpm.stackexchange.com%2fquestions%2f25024%2fplanning-a-sprint-after-reduced-team-strength%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote













            If you reduce a team from 7 to 4, especially if the reason is something outside the team, the best course of action is probably to treat this as a completely new team. People will need to change into new roles, find a new way of working together, cover fresh weaknesses caused by those leaving, find out who is in charge of what, and all the other problems that a new team runs in to.



            Cutting a team in half shouldn't be handled in a "business as usual" type of way; it's a pretty traumatic experience for the team, especially if they've been working together for a while. You could go all the way and run a new team introduction, but at the very least you should give them some time to reform and whatever velocity you have from the previous team can probably go out the window.



            Doing whatever it is you normally do when planning with a new team will likely give the most reliable results. (The most reliable possible, that is. They probably won't be very reliable regardless.)






            share|improve this answer
























              up vote
              2
              down vote













              If you reduce a team from 7 to 4, especially if the reason is something outside the team, the best course of action is probably to treat this as a completely new team. People will need to change into new roles, find a new way of working together, cover fresh weaknesses caused by those leaving, find out who is in charge of what, and all the other problems that a new team runs in to.



              Cutting a team in half shouldn't be handled in a "business as usual" type of way; it's a pretty traumatic experience for the team, especially if they've been working together for a while. You could go all the way and run a new team introduction, but at the very least you should give them some time to reform and whatever velocity you have from the previous team can probably go out the window.



              Doing whatever it is you normally do when planning with a new team will likely give the most reliable results. (The most reliable possible, that is. They probably won't be very reliable regardless.)






              share|improve this answer






















                up vote
                2
                down vote










                up vote
                2
                down vote









                If you reduce a team from 7 to 4, especially if the reason is something outside the team, the best course of action is probably to treat this as a completely new team. People will need to change into new roles, find a new way of working together, cover fresh weaknesses caused by those leaving, find out who is in charge of what, and all the other problems that a new team runs in to.



                Cutting a team in half shouldn't be handled in a "business as usual" type of way; it's a pretty traumatic experience for the team, especially if they've been working together for a while. You could go all the way and run a new team introduction, but at the very least you should give them some time to reform and whatever velocity you have from the previous team can probably go out the window.



                Doing whatever it is you normally do when planning with a new team will likely give the most reliable results. (The most reliable possible, that is. They probably won't be very reliable regardless.)






                share|improve this answer












                If you reduce a team from 7 to 4, especially if the reason is something outside the team, the best course of action is probably to treat this as a completely new team. People will need to change into new roles, find a new way of working together, cover fresh weaknesses caused by those leaving, find out who is in charge of what, and all the other problems that a new team runs in to.



                Cutting a team in half shouldn't be handled in a "business as usual" type of way; it's a pretty traumatic experience for the team, especially if they've been working together for a while. You could go all the way and run a new team introduction, but at the very least you should give them some time to reform and whatever velocity you have from the previous team can probably go out the window.



                Doing whatever it is you normally do when planning with a new team will likely give the most reliable results. (The most reliable possible, that is. They probably won't be very reliable regardless.)







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 48 mins ago









                Erik

                59315




                59315



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fpm.stackexchange.com%2fquestions%2f25024%2fplanning-a-sprint-after-reduced-team-strength%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Comments

                    Popular posts from this blog

                    What does second last employer means? [closed]

                    List of Gilmore Girls characters

                    Confectionery