Ideally your estimates would just be complexity points. And those estimates would go on on the stories in Jira/Azure Dev Ops / wherever
And honestly the team should meet up and discuss the estimates
MechanicalJester
joined 1 year ago
I don't understand your statement. The Mythical Man Month teaches exactly that lesson of more bodies != Faster in many cases.
How long to build the site with 1 full stack dev? 1.5 years.
How long with an existing high performance team of 5? 2 months.
How long if you hire 4 plus the one original (all qualified)? 1 to 1.5 years.
How long if we hire 30 full stack devs? Maybe never.
Good ones are pretty rare and good program managers are even rarer.
What they should do, and what most actually do, are different things.
Project managers must be great with humans and communication. If they are not, then they just can't be effective.
If the timing is critical then the only reasonable solution is to cut scope and features until it fits.
The triangle isn't a rubbery floppy thing, it is iron!
Geez... Project managers are forbidden from making work estimates- they only get to collect them.
They don't get to argue estimates either. They can ask questions to gain understanding but the estimates are the estimates.
Wearing an architect or chief engineer hat is sometimes more fun because you get to call bullshit on dumb estimates like "4 to 5 weeks to model a table with 7 fields, with 2 of them being PK, FK" like GTFO we can model it in the next 5 minutes if I talk slowly.
Some of y'all are look to ask Steve the Miller about this when your answers would be easier to find on Baker Street
I wonder if that sheep is look for the wheel that thief took?
No you don't have a problem.
My partner broke down into tears when I told them how much adding one was going to be.
And, when suitable, almond extract
You know? I literally figured that out a minute before I saw your reply. And I rolled my eyes at myself.
That makes sense. Silly me
Cheers