home.social

#featureteams — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #featureteams, aggregated by home.social.

  1. The 1st time I was called out for leaning toward my passion and preferences and ignoring the pros of an alternative technique was by Giulio Vian. We have all been there; moving beyond that is part of the journey toward professional maturity.

    Thanks to Outpace Conf for hosting a potentially controversial topic and for the great discussions with the audience 🎉

    #OutpaceConf
    #Manchester
    #technologyConference
    #seniorPractitioners
    #leaders
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  2. The 1st time I was called out for leaning toward my passion and preferences and ignoring the pros of an alternative technique was by Giulio Vian. We have all been there; moving beyond that is part of the journey toward professional maturity.

    Thanks to Outpace Conf for hosting a potentially controversial topic and for the great discussions with the audience 🎉







  3. The 1st time I was called out for leaning toward my passion and preferences and ignoring the pros of an alternative technique was by Giulio Vian. We have all been there; moving beyond that is part of the journey toward professional maturity.

    Thanks to Outpace Conf for hosting a potentially controversial topic and for the great discussions with the audience 🎉

    #OutpaceConf
    #Manchester
    #technologyConference
    #seniorPractitioners
    #leaders
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  4. The 1st time I was called out for leaning toward my passion and preferences and ignoring the pros of an alternative technique was by Giulio Vian. We have all been there; moving beyond that is part of the journey toward professional maturity.

    Thanks to Outpace Conf for hosting a potentially controversial topic and for the great discussions with the audience 🎉

    #OutpaceConf
    #Manchester
    #technologyConference
    #seniorPractitioners
    #leaders
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  5. The 1st time I was called out for leaning toward my passion and preferences and ignoring the pros of an alternative technique was by Giulio Vian. We have all been there; moving beyond that is part of the journey toward professional maturity.

    Thanks to Outpace Conf for hosting a potentially controversial topic and for the great discussions with the audience 🎉

    #OutpaceConf
    #Manchester
    #technologyConference
    #seniorPractitioners
    #leaders
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  6. ============================
    Team Topologies Vs Feature Teams
    ============================
    Here at the tech conference Outpace Conf (Manchester), I am exploring the trade-offs, pros and cons, and contextual fitness of two ways to organise teams. And sharing insights from the audience, based on their lived experience.

    --------------------
    ... contine

    #OutpaceConf
    #Manchester
    #technologyConference
    #seniorPractitioners
    #leaders
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  7. ============================
    Team Topologies Vs Feature Teams
    ============================
    Here at the tech conference Outpace Conf (Manchester), I am exploring the trade-offs, pros and cons, and contextual fitness of two ways to organise teams. And sharing insights from the audience, based on their lived experience.

    --------------------
    ... contine







  8. ============================
    Team Topologies Vs Feature Teams
    ============================
    Here at the tech conference Outpace Conf (Manchester), I am exploring the trade-offs, pros and cons, and contextual fitness of two ways to organise teams. And sharing insights from the audience, based on their lived experience.

    --------------------
    ... contine

    #OutpaceConf
    #Manchester
    #technologyConference
    #seniorPractitioners
    #leaders
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  9. ============================
    Team Topologies Vs Feature Teams
    ============================
    Here at the tech conference Outpace Conf (Manchester), I am exploring the trade-offs, pros and cons, and contextual fitness of two ways to organise teams. And sharing insights from the audience, based on their lived experience.

    --------------------
    ... contine

    #OutpaceConf
    #Manchester
    #technologyConference
    #seniorPractitioners
    #leaders
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  10. ============================
    Team Topologies Vs Feature Teams
    ============================
    Here at the tech conference Outpace Conf (Manchester), I am exploring the trade-offs, pros and cons, and contextual fitness of two ways to organise teams. And sharing insights from the audience, based on their lived experience.

    --------------------
    ... contine

    #OutpaceConf
    #Manchester
    #technologyConference
    #seniorPractitioners
    #leaders
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  11. I'll be speaking at Outpace Conf in Manchester on the 16th of October.
    A 1-day tech conf for Sr practitioners & leaders.

    I'll be sharing about
    ----------------------------------------------------------------
    TEAM TOPOLOGIES VS FEATURE TEAMS
    ----------------------------------------------------------------
    Polar opposites or points of a continuum?

    Early bird tickets until Friday, 26th

    The Conf => outpaceconf.com/

    #Manchester
    #Conference
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  12. I'll be speaking at Outpace Conf in Manchester on the 16th of October.
    A 1-day tech conf for Sr practitioners & leaders.

    I'll be sharing about
    ----------------------------------------------------------------
    TEAM TOPOLOGIES VS FEATURE TEAMS
    ----------------------------------------------------------------
    Polar opposites or points of a continuum?

    Early bird tickets until Friday, 26th

    The Conf => outpaceconf.com/




  13. I'll be speaking at Outpace Conf in Manchester on the 16th of October.
    A 1-day tech conf for Sr practitioners & leaders.

    I'll be sharing about
    ----------------------------------------------------------------
    TEAM TOPOLOGIES VS FEATURE TEAMS
    ----------------------------------------------------------------
    Polar opposites or points of a continuum?

    Early bird tickets until Friday, 26th

    The Conf => outpaceconf.com/

    #Manchester
    #Conference
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  14. I'll be speaking at Outpace Conf in Manchester on the 16th of October.
    A 1-day tech conf for Sr practitioners & leaders.

    I'll be sharing about
    ----------------------------------------------------------------
    TEAM TOPOLOGIES VS FEATURE TEAMS
    ----------------------------------------------------------------
    Polar opposites or points of a continuum?

    Early bird tickets until Friday, 26th

    The Conf => outpaceconf.com/

    #Manchester
    #Conference
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  15. I'll be speaking at Outpace Conf in Manchester on the 16th of October.
    A 1-day tech conf for Sr practitioners & leaders.

    I'll be sharing about
    ----------------------------------------------------------------
    TEAM TOPOLOGIES VS FEATURE TEAMS
    ----------------------------------------------------------------
    Polar opposites or points of a continuum?

    Early bird tickets until Friday, 26th

    The Conf => outpaceconf.com/

    #Manchester
    #Conference
    #TEAMTOPOLOGIES
    #FEATURETEAMS

  16. The right adage is “First, make the change easy, then make the easy change” instead of "It will get worse before it gets better" when forming a Platform team, a Complicated subsystem team, or more in general moving a responsibility/task outside a team => smharter.com/blog/2024/01/01/w

    #TeamTopologies #FeatureTeams #CrossFuncionalTeams

  17. The right adage is “First, make the change easy, then make the easy change” instead of "It will get worse before it gets better" when forming a Platform team, a Complicated subsystem team, or more in general moving a responsibility/task outside a team => smharter.com/blog/2024/01/01/w

  18. The right adage is “First, make the change easy, then make the easy change” instead of "It will get worse before it gets better" when forming a Platform team, a Complicated subsystem team, or more in general moving a responsibility/task outside a team => smharter.com/blog/2024/01/01/w

    #TeamTopologies #FeatureTeams #CrossFuncionalTeams

  19. The right adage is “First, make the change easy, then make the easy change” instead of "It will get worse before it gets better" when forming a Platform team, a Complicated subsystem team, or more in general moving a responsibility/task outside a team => smharter.com/blog/2024/01/01/w

    #TeamTopologies #FeatureTeams #CrossFuncionalTeams

  20. The right adage is “First, make the change easy, then make the easy change” instead of "It will get worse before it gets better" when forming a Platform team, a Complicated subsystem team, or more in general moving a responsibility/task outside a team => smharter.com/blog/2024/01/01/w

    #TeamTopologies #FeatureTeams #CrossFuncionalTeams

  21. Ever wondered when/how to effectively move a task/responsibility outside the team? To a Global/shared Function, a Subject Matter Expert, an external contractor, an Agency, a Team Topologies’ Platform team or a Complicated subsystem team.

    Here are some thoughts => smharter.com/blog/2024/01/01/w

    What is your experience? When did it work well for you? When it did not?

    #FeatureTeams #SME #ExternalContractor #Agency #GlobalFunction #SharedFunction #TeamTopologies #PlatformTeam #ComplicatedSubsystemTeam

  22. Ever wondered when/how to effectively move a task/responsibility outside the team? To a Global/shared Function, a Subject Matter Expert, an external contractor, an Agency, a Team Topologies’ Platform team or a Complicated subsystem team.

    Here are some thoughts => smharter.com/blog/2024/01/01/w

    What is your experience? When did it work well for you? When it did not?

  23. Ever wondered when/how to effectively move a task/responsibility outside the team? To a Global/shared Function, a Subject Matter Expert, an external contractor, an Agency, a Team Topologies’ Platform team or a Complicated subsystem team.

    Here are some thoughts => smharter.com/blog/2024/01/01/w

    What is your experience? When did it work well for you? When it did not?

    #FeatureTeams #SME #ExternalContractor #Agency #GlobalFunction #SharedFunction #TeamTopologies #PlatformTeam #ComplicatedSubsystemTeam

  24. Ever wondered when/how to effectively move a task/responsibility outside the team? To a Global/shared Function, a Subject Matter Expert, an external contractor, an Agency, a Team Topologies’ Platform team or a Complicated subsystem team.

    Here are some thoughts => smharter.com/blog/2024/01/01/w

    What is your experience? When did it work well for you? When it did not?

    #FeatureTeams #SME #ExternalContractor #Agency #GlobalFunction #SharedFunction #TeamTopologies #PlatformTeam #ComplicatedSubsystemTeam

  25. Ever wondered when/how to effectively move a task/responsibility outside the team? To a Global/shared Function, a Subject Matter Expert, an external contractor, an Agency, a Team Topologies’ Platform team or a Complicated subsystem team.

    Here are some thoughts => smharter.com/blog/2024/01/01/w

    What is your experience? When did it work well for you? When it did not?

    #FeatureTeams #SME #ExternalContractor #Agency #GlobalFunction #SharedFunction #TeamTopologies #PlatformTeam #ComplicatedSubsystemTeam

  26. A frequent critique to feature teams and collective code ownership is that it requires people excellence (collaboration, growth mindset/mastery, discipline). But then tech debt never stopped us from aiming and working toward tech excellence.
    I see Cognitive Load used too often as an excuse not to collaborate and learn outside one's comfort zone and share responsibilities
    #people #collaboration #teamtopologies #featureteams

  27. A frequent critique to feature teams and collective code ownership is that it requires people excellence (collaboration, growth mindset/mastery, discipline). But then tech debt never stopped us from aiming and working toward tech excellence.
    I see Cognitive Load used too often as an excuse not to collaborate and learn outside one's comfort zone and share responsibilities

  28. A frequent critique to feature teams and collective code ownership is that it requires people excellence (collaboration, growth mindset/mastery, discipline). But then tech debt never stopped us from aiming and working toward tech excellence.
    I see Cognitive Load used too often as an excuse not to collaborate and learn outside one's comfort zone and share responsibilities
    #people #collaboration #teamtopologies #featureteams

  29. A frequent critique to feature teams and collective code ownership is that it requires people excellence (collaboration, growth mindset/mastery, discipline). But then tech debt never stopped us from aiming and working toward tech excellence.
    I see Cognitive Load used too often as an excuse not to collaborate and learn outside one's comfort zone and share responsibilities
    #people #collaboration #teamtopologies #featureteams

  30. A frequent critique to feature teams and collective code ownership is that it requires people excellence (collaboration, growth mindset/mastery, discipline). But then tech debt never stopped us from aiming and working toward tech excellence.
    I see Cognitive Load used too often as an excuse not to collaborate and learn outside one's comfort zone and share responsibilities
    #people #collaboration #teamtopologies #featureteams

  31. @matthewskelton @jessitron @jeffsussna

    > The problem I have with all the LeSS

    Note that this was widespread among XPers a decade before LeSS.

    > I have yet to hear a convincing story

    My own experience with related tradeoffs is here: smharter.com/blog/2022/11/21/t

    > 24x7 services and "on call" was not really a thing

    I've seen a development team where members rotated to provide "on-call" incident support.

    Could you expand on which DevOps principles are lacking?

    #FeatureTeams #TeamTopologies

  32. @matthewskelton @jessitron @jeffsussna

    > The problem I have with all the LeSS

    Note that this was widespread among XPers a decade before LeSS.

    > I have yet to hear a convincing story

    My own experience with related tradeoffs is here: smharter.com/blog/2022/11/21/t

    > 24x7 services and "on call" was not really a thing

    I've seen a development team where members rotated to provide "on-call" incident support.

    Could you expand on which DevOps principles are lacking?

  33. @matthewskelton @jessitron @jeffsussna

    > The problem I have with all the LeSS

    Note that this was widespread among XPers a decade before LeSS.

    > I have yet to hear a convincing story

    My own experience with related tradeoffs is here: smharter.com/blog/2022/11/21/t

    > 24x7 services and "on call" was not really a thing

    I've seen a development team where members rotated to provide "on-call" incident support.

    Could you expand on which DevOps principles are lacking?

    #FeatureTeams #TeamTopologies

  34. @matthewskelton @jessitron @jeffsussna

    > The problem I have with all the LeSS

    Note that this was widespread among XPers a decade before LeSS.

    > I have yet to hear a convincing story

    My own experience with related tradeoffs is here: smharter.com/blog/2022/11/21/t

    > 24x7 services and "on call" was not really a thing

    I've seen a development team where members rotated to provide "on-call" incident support.

    Could you expand on which DevOps principles are lacking?

    #FeatureTeams #TeamTopologies

  35. @matthewskelton @jessitron @jeffsussna

    > The problem I have with all the LeSS

    Note that this was widespread among XPers a decade before LeSS.

    > I have yet to hear a convincing story

    My own experience with related tradeoffs is here: smharter.com/blog/2022/11/21/t

    > 24x7 services and "on call" was not really a thing

    I've seen a development team where members rotated to provide "on-call" incident support.

    Could you expand on which DevOps principles are lacking?

    #FeatureTeams #TeamTopologies

  36. @jessitron @jeffsussna

    I recently had a meaningful conversation, with Bas Vodde, which remembered me of the dual solution, compared to TT, consisting of transcending dependencies and Conway's Law => featureteams.org/

    It was common while XP was popular and I used it a lot in 2006÷2013.

    #FeatureTeams #TeamTopologies

  37. @jessitron @jeffsussna

    I recently had a meaningful conversation, with Bas Vodde, which remembered me of the dual solution, compared to TT, consisting of transcending dependencies and Conway's Law => featureteams.org/

    It was common while XP was popular and I used it a lot in 2006÷2013.

  38. @jessitron @jeffsussna

    I recently had a meaningful conversation, with Bas Vodde, which remembered me of the dual solution, compared to TT, consisting of transcending dependencies and Conway's Law => featureteams.org/

    It was common while XP was popular and I used it a lot in 2006÷2013.

    #FeatureTeams #TeamTopologies

  39. @jessitron @jeffsussna

    I recently had a meaningful conversation, with Bas Vodde, which remembered me of the dual solution, compared to TT, consisting of transcending dependencies and Conway's Law => featureteams.org/

    It was common while XP was popular and I used it a lot in 2006÷2013.

    #FeatureTeams #TeamTopologies

  40. @jessitron @jeffsussna

    I recently had a meaningful conversation, with Bas Vodde, which remembered me of the dual solution, compared to TT, consisting of transcending dependencies and Conway's Law => featureteams.org/

    It was common while XP was popular and I used it a lot in 2006÷2013.

    #FeatureTeams #TeamTopologies