3 ms·
That doesn't make any sense.
by giantg2 5y ago
That doesn't make any sense.
- soco 5y agoUnfortunately it does. It's comparatively quick and easy to slap together an application which does the first 80%. Then, come edge cases, stuff your req engineers didn't come around to define, or which your approach moved fast and broke, or which simply couldn't fit in the architecture as your initial sprints created. Everything doable of course but...
- giantg2 5y agoSo you're thinking on a project level. I'm talking about a resource level. Why hire a couple senior devs to spend 90% of their time on junior tasks? A better model is to hire a couple juniors to handle the junior tasks and use the seniors for the senior tasks and oversight. Much more efficient that way. Sure, you can have percentages over 100% for many things. When looking at a breakdown of tasks/time/work for an individual, you are constrained to 100% (the pie chart values might get bigger but it always adds up to 100%)
- PaulHoule 5y agoPro Tip: calling developers "resources" causes employee turnover. What is a "senior" task and what is a "junior" task depends on the organization of labor. It's certainly possible for a senior to divide a big task into small chunks that juniors can dispatch with great haste. You could possibly put 1 senior and 4 juniors together in a bullpen and get them to do the work that (say) 3 seniors or 10 juniors could do with a different organization. To realize that you have to get the human relationships right, a theme I keep harping on is that the people involve have to feel the tasks are worthy of them. Many juniors, in a situation like that, might feel like they are being micromanaged. Another thing you need is for the senior to have enough of a global view of the situation that their seniority really produces value. If you really don't understand where you are going and you'll need to rework everything you aren't getting value out of that kind of situation. Around my farm we have a large number of "junior resources" available for construction work. Those young people make silly mistakes that cost time and money and that's one reason why they make $18 an hour compared to a more experienced person who makes $40 an hour because they are twice as productive.
- PaulHoule 5y agoYes it does. I have heard so many business oriented people say that they want to do the 20% of the work that gets 80% of the way to the destination. 80% of the way to destination means "0% of the value delivered". Percentages over 100% occur all the time in project management, such as https://en.wikipedia.org/wiki/Olkiluoto_Nuclear_Power_Plant https://en.wikipedia.org/wiki/Olkiluoto_Nuclear_Power_Plant where you might have spent 500% of the budget to get 50% done. (China built a reactor of that type and turned it on but they had some fuel rods burst right away and had to turn it off.)
- giantg2 5y agoSo you're thinking on a project level. I'm talking about a resource level. Why hire a couple senior devs to spend 90% of their time on junior tasks? A better model is to hire a couple juniors to handle the junior tasks and use the seniors for the senior tasks and oversight. Much more efficient that way. Sure, you can have percentages over 100% for many things. When looking at a breakdown of tasks/time/work for an individual, you are constrained to 100% (the pie chart values might get bigger but it always adds up to 100%)
- PaulHoule 5y agoProjects get done when the "resource" does it what takes to make the project happen. The data scientist who thinks he is too good to check his notebooks into version control is just one version of people who think they are "too good" to be doing what they are doing. In small teams people do the work that is critical whether it is too "easy" in their estimation or if they have to stretch themselves to do something difficult. Sometimes they need to get help. A few people on the team can indulge in doing only the work they feel like doing, but that's because there are adults on the team who cover for them. There are many advanced programming tasks which could, in principle, be assigned to some juniors. For instance, CS majors usually take one or more courses in compilers and programming languages. If your organization is dependent on a legacy programming language you could possibly get one of those juniors to write a transpiler that compiles it to something current. Succeeding at that takes some guidance, but it might take some form that some "seniors" would find offensive such as writing a really tough set of unit tests. Many "seniors" on the other hand never took any compiler courses or sold their textbooks and forgot everything 10 years ago.
- HPsquared 5y agoI guess if you multiply all estimates by π, 110% is only about a third of the actual work.