They just recommended cross-checking status updates in "stand up" meetings with commit history to catch engineers underperforming. That is (1) (2) and (3).
You are not answering my question. No, you ask your acquaintances who work in law, finance or medicine. Neither does academia have any "stand up". What specific needs do CRUD software projects have that are met by…
What specific needs are met by daily status updates? Professionals outside of software don't do that. The best software projects don't do that. It's very popular in CRUD projects led by non-technical middle management…
Daily status updates are not useful. Linux kernel developers don't do them. I trust that nothing is stopping your engineers from having a chat and that their manager doesn't need to schedule their chats for them.
If six months of daily meetings did not lead anywhere then cancel those meetings.
Does French law mandate trial periods or 3 month notice periods? You can usually negotiate those away. Reference checks or trial period but you should really not require both, that's an employer problem. Europe pays…
Kanban is just a todo list in English and all sorts of professionals use todo lists.
That attitude works well in other professions. If you want to become a managing partner at a law form you are expected to have chops. Why should software engineers accept micromanagement by laymen?
Forcing every team in the company to use the same project management framework because consultants who never created great software claimed it's a panacea. Interesting decision.
Technical knowledge should be a necessary but not sufficient condition to become an engineering manager. A layman can't take a two day course with no exam and become a managing partner at a law firm. Why is that…
That's yearly planning. If estimation means giving your best effort to complete a project over the next year then that's not a problem. When you start micromanaging on a biweekly basis with daily status updates then it…
How about getting rid of the "stories", "points" and "sprints" altogether? Not only is the nomenclature abhorrent, the best software projects don't use enterprise agile methodology.
Planning too often is also a problem. You should not do it more often than every three to six months.
There is no evidence that you get better economic outcomes from micromanaging software engineers, and not for the lack of trying.
Why are you pushing software engineers for "estimates"? You don't ask mathematicians how long that conjecture will take to prove. It's done when it's done.
The non-technical managers and agile coaches are the problem. That's why the best software projects don't have them. Linux kernel developers don't run story ticket velocity poker sprints.
They didn't improve on human truck drivers yet.
Who claimed management consultants are not stochastic parrots?
The software engineers working on the best projects don't follow "scrum" frameworks. Where are the story velocity ticket points in Linux kernel development?
Learn the concept better, not an exception to an incorrect rule. It seems like the model architecture just isn't good enough.
You need business with them to browse the internet and now to even buy a car. There is a word for this.
You don't seem to understand them. German law does not force you to have a three month notice period at the start of your employment, you can negotiate for a shorter period without the at-will part.
Or you don't and end up making a non-functional website for the public sector for $100M. Software projects fail often, and not for the lack of trying, there is not yet any evidence that you can micromanage them into…
It's pretty bold to give a trial period to an international hire. Employment security is a good thing, and since wages are much lower than in the US, there is not much risk.
I don't see the risk. It seems German companies are making weak offers with "probation periods" even for international hires. One problem might be that such offers are not very attractive.
They just recommended cross-checking status updates in "stand up" meetings with commit history to catch engineers underperforming. That is (1) (2) and (3).
You are not answering my question. No, you ask your acquaintances who work in law, finance or medicine. Neither does academia have any "stand up". What specific needs do CRUD software projects have that are met by…
What specific needs are met by daily status updates? Professionals outside of software don't do that. The best software projects don't do that. It's very popular in CRUD projects led by non-technical middle management…
Daily status updates are not useful. Linux kernel developers don't do them. I trust that nothing is stopping your engineers from having a chat and that their manager doesn't need to schedule their chats for them.
If six months of daily meetings did not lead anywhere then cancel those meetings.
Does French law mandate trial periods or 3 month notice periods? You can usually negotiate those away. Reference checks or trial period but you should really not require both, that's an employer problem. Europe pays…
Kanban is just a todo list in English and all sorts of professionals use todo lists.
That attitude works well in other professions. If you want to become a managing partner at a law form you are expected to have chops. Why should software engineers accept micromanagement by laymen?
Forcing every team in the company to use the same project management framework because consultants who never created great software claimed it's a panacea. Interesting decision.
Technical knowledge should be a necessary but not sufficient condition to become an engineering manager. A layman can't take a two day course with no exam and become a managing partner at a law firm. Why is that…
That's yearly planning. If estimation means giving your best effort to complete a project over the next year then that's not a problem. When you start micromanaging on a biweekly basis with daily status updates then it…
How about getting rid of the "stories", "points" and "sprints" altogether? Not only is the nomenclature abhorrent, the best software projects don't use enterprise agile methodology.
Planning too often is also a problem. You should not do it more often than every three to six months.
There is no evidence that you get better economic outcomes from micromanaging software engineers, and not for the lack of trying.
Why are you pushing software engineers for "estimates"? You don't ask mathematicians how long that conjecture will take to prove. It's done when it's done.
The non-technical managers and agile coaches are the problem. That's why the best software projects don't have them. Linux kernel developers don't run story ticket velocity poker sprints.
They didn't improve on human truck drivers yet.
Who claimed management consultants are not stochastic parrots?
The software engineers working on the best projects don't follow "scrum" frameworks. Where are the story velocity ticket points in Linux kernel development?
Learn the concept better, not an exception to an incorrect rule. It seems like the model architecture just isn't good enough.
You need business with them to browse the internet and now to even buy a car. There is a word for this.
You don't seem to understand them. German law does not force you to have a three month notice period at the start of your employment, you can negotiate for a shorter period without the at-will part.
Or you don't and end up making a non-functional website for the public sector for $100M. Software projects fail often, and not for the lack of trying, there is not yet any evidence that you can micromanage them into…
It's pretty bold to give a trial period to an international hire. Employment security is a good thing, and since wages are much lower than in the US, there is not much risk.
I don't see the risk. It seems German companies are making weak offers with "probation periods" even for international hires. One problem might be that such offers are not very attractive.