[PaulHoule]

Triple constraints: schedule, cost, scope.

The typical software team (not great at project management) would do best to attempt "least cost" development which is mostly attained by "squeezing risk" with effective planning to avoid wasted work.

Compressing the schedule past that adds risk and cost, often sharply.

Think of these things:

Is there some way you can simplify the deliverable to shave time off?

Can you outsource some of the work?

These work at the margin. If you doubled the team size you would waste time getting people up to speed. Feed 10% of work to a wizard, find 10% you can skip, so are having an impact.

Crazy work arrangements work if you have a tiny team (say 5 people) and strong morale (100% consensus that this isn't just OK but it's a gas gas gas). If anybody on the team is going to be resentful about it, however, it won't work.

How about going into a reply reduced interruption environment during the week?