4 ms·
That training sounds absurd and forcing people switch roles for a sprint is worse. That said, your example merely indicates that corporate workshops are bullsh
by gherkinnn 4y ago
That training sounds absurd and forcing people switch roles for a sprint is worse.
That said, your example merely indicates that corporate workshops are bullshit. It does not contradict the value of T people.
In my experience, two highly specialised but disjoint people can only produce rubbish. This is where you need some entry-level intersection of knowledge.
In your case, I don’t expect a FE dev to care about persistence, nor a BE dev to worry about form validation. But both need to be aware of the customer, the business, and robust API design.
- jvanderbot 4y agoI'm not sure that's "T shaped" as much as it is "cross functional", which can be done without requiring anyone to know about anything outside their silo, as long as someone crosses silos and communicates. That's more of a systems engineering model, where a specific role forms the bridge and only the bridge, and specialists form the teams. It's a very Aerospace model of doing business.