Horizontal segregation and multi-disciplinary/cross-functional teams

[gtramontina]

Is this a proposal or a request?

• Proposal (I'm sharing)
• Request (I'm learning)

Subject

Horizontal segregation and multi-disciplinary/cross-functional teams

Comments

It seems today that having segregated roles such as frontend, backend, mobile, DevOps, QA has become the go-to approach for software development. While it seems right to have these roles within a team, more often than not these "cross-functional teams" tend to work very waterfall-y. Instead of moving people to work, we move work to people. If, for example, the frontend person is out sick for a week, the team won't deliver anything because, although this is a "cross-functional team", only that person is capable of doing that kind of work. It creates bottlenecks, stories become tasks, we end up managing people instead of work to be done… Anyway, I don't want to turn this into a rant… just an idea for a fishbowl. 😄

(…)
as haiku
The soil is dry--
the irrigator has gone
I start to water
– James Shore

[gtramontina]

Done! 👍
https://www.meetup.com/Software-Crafters-Sydney/events/258492283/