[HN Gopher] Split Your Overwhelmed Teams: Two teams of five is n...
       ___________________________________________________________________
        
       Split Your Overwhelmed Teams: Two teams of five is not same as one
       team of ten
        
       Author : yarapavan
       Score  : 38 points
       Date   : 2022-11-13 13:26 UTC (9 hours ago)
        
 (HTM) web link (queue.acm.org)
 (TXT) w3m dump (queue.acm.org)
        
       | tspike wrote:
       | I'd love to see this article more fully fleshed out. What
       | happened after the split?
        
         | weare138 wrote:
         | That is something I immediately noticed. There's no follow up
         | as to whether any of this actually worked. This just seems like
         | a way for management to rationalize understaffing and shift the
         | blame to anything but the lack of adequate staff.
         | 
         | The article paradoxically argues against specialization but
         | then goes on to say generalist must choose a team and
         | specialize in certain team tasks. The entire article just
         | smacks of managerial double-speak that puts employees in a
         | situation that's unwinnable by design while alleviating
         | management of any responsibility for their decisions. Don't
         | specialize enough? Well that's the employees fault. And if they
         | over specialize? Well that's their fault too.
         | 
         |  _Just hire more people._ And if you can 't afford to
         | adequately staff your own company, that's your fault not your
         | employees. Your poor management skills is what got you into
         | that situation. You have no one to blame but yourself.
        
       | didip wrote:
       | No... then we need to hire 10 PMs to handle the communication.
        
       | faangiq wrote:
        
       | babaganoosh89 wrote:
       | +1 for specialization, in my experience working on a fullstack
       | team is significantly more painful than having a specialized
       | role. Of course it's partially because you have to learn a bunch
       | of stuff, but I've also found that fullstack teams tend to have
       | poor planning, e.g. it's structured as fullstack to constantly
       | fill gaps in a not well defined project / roadmap. Fullstack is
       | good experience if you want to do your own projects / startup,
       | but not a peaceful job.
        
         | sitkack wrote:
         | What is the reason though?
         | 
         | Even on a fullstack team, some folks will be better or
         | gravitate towards certain tasks.
        
           | baby wrote:
           | Maybe underestimating how different people can ramp up in
           | different parts of the stack, or underestimating the context
           | switch, or the amount of glue between the different parts of
           | the stack.
        
       ___________________________________________________________________
       (page generated 2022-11-13 23:01 UTC)