3 ms·
I think it depends on the industry and needs of the company. As an example, In video games this is used as a way to get a feature shipped. Plop a bunch of arti
by c0nfused 9y ago
I think it depends on the industry and needs of the company.
As an example, In video games this is used as a way to get a feature shipped. Plop a bunch of artists with a coder or two and a couple of QA guys and roll a feature together. It cuts communications time, keeps everyone focused, and as long as your feature is encapsulated nicely it should merge back cleanly into main in a few days.
If you are just applying a blender to the org chart it isn't going to be a great choice. However, something like putting a developer within ear shot of Technical Support isn't always a bad idea.
- sillysaurus3 9y agoAs an example, In video games this is used as a way to get a feature shipped. Plop a bunch of artists with a coder or two and a couple of QA guys and roll a feature together. It cuts communications time, keeps everyone focused, and as long as your feature is encapsulated nicely it should merge back cleanly into main in a few days. At the studios I worked at, these were called "meetings."
- pseudalopex 9y agoCross-functional feature teams are something entirely different. Having a developer spend a day with the support team every so often is a great idea. Putting them within earshot just leads to the developers wearing headphones all day.