It's pretty crazy how expensive a simple sprint planning meeting really is if you have 5+ engineers.
Sometimes it leads the death of many man-month projects, or worse.
11–20 of 146 posts
It's pretty crazy how expensive a simple sprint planning meeting really is if you have 5+ engineers.
Sometimes it leads the death of many man-month projects, or worse.
No matter how you say it to those kinds of people, expressing that meetings are keeping you from getting engineer-related work done will be viewed extremely negatively.
I’ve been in IT decades and still don’t know what the best answer is.
You may want to consider renaming the tool, it's overlapping with getclockwise.com, which is quite popular.
It's pretty crazy how expensive a simple sprint planning meeting really is if you have 5+ engineers.
What this clock does not compute, is how much money you leave on the table by reducing your meeting count/time and have your engineers/workers dive straight into the problem without talking enough to each other or with the stakeholders beforehand. Sometimes it leads the death of many man-month projects, or worse.
Technical solutions to social problems don't usually work, why would this be different?
I don't see this as a technical solution to a social problem. I see this as a technical tool to help with a social solution to a social problem. Specifically, finding a way to communicate the opportunity cost of a meeting, which is a social solution to the social problem, because I don't need this app to do it, but it could help.
The terminal UI is one thing. From my personal experience, displaying the running cost of meetings in my Zoom camera would always be a bad idea. It's an optional feature of this program so it doesn't detract away from the entire idea, just saying that from my experience, managers already know that meetings cost money so displaying the cost of the meeting is pointless, you need to instead argue why your manager is wrong that the cost of the meeting is worth it.
Technical solutions to social problems don't usually work, why would this be different?
Earlier quoted context omitted.
I don't see this as a technical solution to a social problem. I see this as a technical tool to help with a social solution to a social problem. Specifically, finding a way to communicate the opportunity cost of a meeting, which is a social solution to the social problem, because I don't need this app to do it, but it could help.
> finding a way to communicate the opportunity cost of a meeting ... I don't need this app to do it, but it could help. The terminal UI is one thing. From my personal experience, displaying the running cost of meetings in my Zoom camera would always be a bad idea. It's an optional feature of this program so it doesn't detract away from the entire idea, just saying that from my experience, managers already know that m…
I just ask up front whether we can accomplish the same thing without a meeting, and if we can, I just say no to the meeting. If I'm actually necessary, then it'll get done one way or another without the meeting. If I'm not, then it's most likely not my battle to fight. (Substitute "We" for "I" if I'm the manager or a mentor or tech lead or something.)
Good luck. There are some people in organizations whose entire job is to schedule and attend meetings. No matter how you say it to those kinds of people, expressing that meetings are keeping you from getting engineer-related work done will be viewed extremely negatively. I’ve been in IT decades and still don’t know what the best answer is.
While in my country, engineers are paid around 50k$...