11–20 of 62 posts
I have found this to be true in my own experience both as a developer and team lead, and now as a CEO. But we are getting office space from our new investor, and I have to start coming into the office or we will seem ungrateful! What are some of the most major benefits you've found from coming into the office every single day?
Because it's rare that you do.
I have found this to be true in my own experience both as a developer and team lead, and now as a CEO. But we are getting office space from our new investor, and I have to start coming into the office or we will seem ungrateful! What are some of the most major benefits you've found from coming into the office every single day?
In my experience, it's waaaay more efficient for developers to be in the same room if you do it right, though I'm starting to think I might have a minority opinion on that.
I have found this to be true in my own experience both as a developer and team lead, and now as a CEO. But we are getting office space from our new investor, and I have to start coming into the office or we will seem ungrateful! What are some of the most major benefits you've found from coming into the office every single day?
I droned on and on about it in a blog post once if you're interested: http://caines.ca/blog/programming/in-defense-of-the-office/ . In my experience, it's waaaay more efficient for developers to be in the same room if you do it right, though I'm starting to think I might have a minority opinion on that.
To understand lean, you have to understand its roots in operations management and lean production methods at Toyota and other companies. The whole purpose is not predictable planning, it's continuous process improvement.
It's the process of improving your process.
If you were doing agile or async right, you would start with a process or manifesto or whatever, and then you'd use it for some period of time, say a 2 week sprint, then at the end you talk about what works and what doesn't, and what needs to change to get better.
You try the changes and after 2 weeks you talk again, and again, and again until after a few months the process you have looks a lot different in big and small ways than it did when you started.
Nearly every criticism of agile feels hollow to me because they all bemoan the meetings or the planning or the cards or whatever and instead of having a team retrospective, fixing the process, and finding a better way... they trash agile.
If you are doing agile right, your processes will change and improve over time and that's a good thing. When your process stops changing and stops improving, you've lost.
Async manifesto is maybe a nice starting point for teams, but it's a woefully suboptimal end point for teams. We can do better than this.
Never stop improving.
I have found this to be true in my own experience both as a developer and team lead, and now as a CEO. But we are getting office space from our new investor, and I have to start coming into the office or we will seem ungrateful! What are some of the most major benefits you've found from coming into the office every single day?
I droned on and on about it in a blog post once if you're interested: http://caines.ca/blog/programming/in-defense-of-the-office/ . In my experience, it's waaaay more efficient for developers to be in the same room if you do it right, though I'm starting to think I might have a minority opinion on that.
There are plenty of cases where better documentation, training, or other means of communication would provide a higher bus factor than always relying on pestering another dev. Also, with video chat, it's harder to believe that it is so difficult to meet or plan without being in the same building.
This misses on the most important part of agile/scrum/lean... retrospectives. To understand lean, you have to understand its roots in operations management and lean production methods at Toyota and other companies. The whole purpose is not predictable planning, it's continuous process improvement. It's the process of improving your process. If you were doing agile or async right, you would start with a process or man…
And as you say, they've missed the biggest point - consider your process, and iteratively improve it.
Take scrum, cut out everything that involves direct human interaction and replace it with tools and documents.
God forbid us developers should waste time communicating with other human beings. Who needs the bandwidth of face-to-face interaction when you can just do a pull request?
Asnc communication is great for introverts who write well. I am a rarity in that I am a leader as a coder, Run teams Deliver products, but due to having Dysgraphia I write with great difficulty. No where in this set of guidelines is mentoring.
It could be summed up as RTFM
I have found this to be true in my own experience both as a developer and team lead, and now as a CEO. But we are getting office space from our new investor, and I have to start coming into the office or we will seem ungrateful! What are some of the most major benefits you've found from coming into the office every single day?
I droned on and on about it in a blog post once if you're interested: http://caines.ca/blog/programming/in-defense-of-the-office/ . In my experience, it's waaaay more efficient for developers to be in the same room if you do it right, though I'm starting to think I might have a minority opinion on that.
There are some big picture, architectural design discussions covering many interrelated components that can benefit form in-person meetings but those kind of meetings are the exception and not the norm in my experience.