3 ms·
I love this model of working, but I think it's a lot more common in engineering teams than people realize. My company isn't anything special, and certainly most
by hacknat 12y ago
I love this model of working, but I think it's a lot more common in engineering teams than people realize. My company isn't anything special, and certainly most of the rest of the company doesn't work open allocation, but the engineering team pretty much does. You work on what you want, and you tell people what you're doing. Does anyone else feel this way?
- erikschoster 12y agoIt's not formalized in any way, but we have a small team that works this way. I would imagine it would be hard to scale, and takes the right sort of people, but it's a really great environment to work in. We are constantly experimenting and everyone is welcome where they feel they can be helpful - our video production team is deeply involved with the devops side of our streaming server for example...
- thearn4 12y agoThere's definitely pockets like this where I work (Gov't agency), but these pockets are still floating in a sea of the expected waterfall bureaucracy. It's basically up to team leads/PMs to decide if they're going to act as a buffer against that or not.
- zerr 12y agoExactly. I've worked in several small companies and it used to be a case always... I guess the challenge is to have a similar structure in relative big organizations (e.g. 200+ engineers).