Loading ...
Sorry, an error occurred while loading the content.

Multiple P.O.'s / Team or Single P.O./ Team with Multiple Products ?

Expand Messages
  • Michael Tibbert
    We have 1 team of 5 developers, 1 team of 3 developers and 1 team of 3 developers. There is talk about combining the 2 teams of 3 developers into 1 team of 6
    Message 1 of 5 , Apr 25, 2012
    • 0 Attachment
      We have 1 team of 5 developers, 1 team of 3 developers and 1 team of 3 developers.

      There is talk about combining the 2 teams of 3 developers into 1 team of 6 developers.

      I am very interested in hearing others experiences how they address the situation of a team working on multiple products.

      Thanks in advance for your assistance.

      Michael Tibbert
    • Michael James
      In a similar situation we had good results with one Product Owner, one Product Backlog, one Sprint Planning Meeting with two breakout sessions for detailed
      Message 2 of 5 , Apr 25, 2012
      • 0 Attachment
        In a similar situation we had good results with one Product Owner, one Product Backlog, one Sprint Planning Meeting with two breakout sessions for detailed task discussions, two separate taskboards, two separate daily meetings with cross pollination (i.e. representatives visit other meetings), one integrated product shown at Sprint Review Meeting, two Sprint Retrospectives with a common items discussed between teams at the end.

        Let us know what you do.

        --mj
        (Michael)

        On Apr 25, 2012, at 11:36 AM, Michael Tibbert wrote:

         

        We have 1 team of 5 developers, 1 team of 3 developers and 1 team of 3 developers.


        There is talk about combining the 2 teams of 3 developers into 1 team of 6 developers.

        I am very interested in hearing others experiences how they address the situation of a team working on multiple products.

        Thanks in advance for your assistance.

        Michael Tibbert


      • RonJeffries
        Hi Michael, ... First thing I d like to know is why work on multiple projects? Second thing would be to hear a bit about how you do it, what your release
        Message 3 of 5 , Apr 25, 2012
        • 0 Attachment
          Hi Michael,

          On Apr 25, 2012, at 2:36 PM, Michael Tibbert wrote:

          I am very interested in hearing others experiences how they address the situation of a team working on multiple products.

          First thing I'd like to know is "why work on multiple projects?"

          Second thing would be to hear a bit about how you do it, what your release cycles are like, and such like.
          You never know what is enough unless you know what is more than enough. -- William Blake

        • Steve
          Hi Michael What is the stated rationale for combing the teams? Will all team members be working on each Backlog item or will there still be a final product
          Message 4 of 5 , Apr 25, 2012
          • 0 Attachment
            Hi Michael

            What is the stated rationale for combing the teams?

            Will all team members be working on each Backlog item or will there still be a final product 'split? ie multple codebases, multiple TDD repositories and different builds for different products throughout the Sprints?

            The number of 6 is within acceptable limits but it what is they are going to do that is important.

            One PO can serve multiple teams and one ScrumMaster can serve up to 3 teams (just - but its hard work!).

            Find out what the driver for this initiative is and see if that is practical and fits with Agile Principles.

            --- In scrumdevelopment@yahoogroups.com, "Michael Tibbert" <michael.tibbert@...> wrote:
            >
            > We have 1 team of 5 developers, 1 team of 3 developers and 1 team of 3
            > developers.
            > There is talk about combining the 2 teams of 3 developers into 1 team of
            > 6 developers.
            > I am very interested in hearing others experiences how they address the
            > situation of a team working on multiple products.
            > Thanks in advance for your assistance.
            > Michael Tibbert
            >
          • Kevin Callahan
            HI Micheal, First a couple clarifying questions: 1. is the technology homogenous, or mixed (java, C#, rails, etc) 2. Is there an existing mapping of
            Message 5 of 5 , Apr 26, 2012
            • 0 Attachment
              HI Micheal,

              First a couple clarifying questions: 

              1. is the technology homogenous, or mixed (java, C#, rails, etc)
              2. Is there an existing mapping of team:product now? In other words do the existing teams have ownership, either explicitly through designated ownership or implicitly through something like tech expertise?

              This is a *very* poignant question as my organization is currently forming a 4th engineering team; there will thus be 3 teams working on a WOA/platform architecture solution set that is heterogeneous between java and rails. We have yet to commit to a specific approach to how many backlogs, and how teams will pull from those backlog(s), as well as to what degree the teams should be generalists or specialist on the tech stacks and code bases. This of course doesn't even get into the cultural differences across the teams. Oh, and we're our org is distributed across the continental US...

              Anyhow, I'll be reading answers to your questions with much interest ;)

              -k

              On Apr 25, 2012, at 2:36 PM, Michael Tibbert wrote:

               

              We have 1 team of 5 developers, 1 team of 3 developers and 1 team of 3 developers.


              There is talk about combining the 2 teams of 3 developers into 1 team of 6 developers.

              I am very interested in hearing others experiences how they address the situation of a team working on multiple products.

              Thanks in advance for your assistance.

              Michael Tibbert


              Kevin Callahan, CSP
              Scrum Master
              mobile: 207-691-2997
              AIM: kevmocal


            Your message has been successfully submitted and would be delivered to recipients shortly.