I'm a lead Dev on an agile team. We were just handed a fixed scope, fixed date project. On Monday, instead of helping push this out, I get to have a meeting to explain how throwing more bodies at it will slow us down.

"No! We are not code monkeys! Knowing JS and Java isn't the same as knowing our application. Stop fantasizing that it's a simple manpower issue and leave us alone so we can work these fucking nightmare timelines in peace!!"

I'm looking for a better way than that to explain it to the Sr management for the business so I don't get fired.

There is research backing up your claim. They also have made some pretty nice graphics for it. Just so you can bring a giant "I am right" slide to the meeting.
Usually people shut up quickly when you hit them with a university logo and data.

@vringar if you know a good graphic, I'll ram it down their throats. :)

The concept you're looking for is called Brook's Law. https://en.m.wikipedia.org/wiki/... - it's a pretty nuanced thing, but there might be something you can use to make your point. Sometimes financial realities take precedence over anything else.

http://bfy.tw/9t7n
What I meant was Tuckman's stages of group development. But Brooks Law also seems to apply.

Honest answer:

Have been trapped several times in companies that feel the same. While I've won small battles to get them to listen, it never lasts longer than 2 weeks.

To me, yelling and getting fired / quitting is the right option. Just prep a back up job first.

Dealing with that shit is not worth the high blood pressure.

@practiseSafeHex this is atypical an MY management is behind me. The business just believes that people = throughput.

@yamatoman so dev and sales are two independent "command chains" and the sales top manager just wants to flood your departure with man power?

@yamatoman yep, and 6 months from now they will hand you a job that should take 6 months, give you 3 and explain its fine because 4 new people are starting next week.

@practiseSafeHex There's a clue in your "several times" comment. So, so many companies operate on this principle - quicker solutions = more people. It is always the job of the few to change perspective of the many. It'll take time to become the norm because whilst there are commission driven salespeople involved in any project, the workers will be the ones who are asked to perform miracles.

@vringar Internal customer. We don't sell software.
It's a time crucial exceptional situation that I agree with. I just don't believe there is value in wasting my time by questioning my reasoning based on their lack of experience. I've got a job to do and it's not explaining software development them. :)

@samk 2 years in, having a discussion about this every 2 - 3 weeks, with prior knowledge that the last guy did the same for the previous 3 years

= they will not understand or learn. As soon as the cheque book comes out, so do the "of course we can" 's.

If they don't get it, time and time again, you have to be realistic.

@yamatoman then let's wait for Monday ( never thought I would say smt like that :P) and see how they react. If they are somewhat competent and descent human beings you should have no problems convincing them.

@practiseSafeHex meh, I've been dealing with these people for 15 years. They have a hard time differentiating between directing hourly workers who use the systems and cooperating with the skilled professionals who create the systems.

Questioning my professionalism won't win them extra brownie points and we certainly won't be moving faster if I'm focusing on explaining this to them instead of designing the solution.

However, I've decided to use the opportunity to redirect back at them. They can do a better job of refining the requirements so I can stop burning time on that. 😂

@vringar Fingers crossed. 😁

Say exactly that and you'll get promoted for possession of cohones!

@Eror130 gotta lay low a little. Already had an "open and honest" meeting where I gave feedback to their ilk.