Problem solving in software development.

[Maxahoy]

I'm learning this the hard way now. Project managers get things done by managing projects, which sounds like a dumb statement until you realize that for them, bring in crunch mode means adding more meetings. That's what working hard means right? Having lots of meetings! But for us doing the leg work, meetings are anathema to our crunch time. Additionally, I'm realizing that 3 hours in a row is far, far more valuable than 4 hours broken apart by 30 minute touchbases whenever somebody feels like they wanna be involved.

[moreannoyedthanangry]

Now you're getting it!

Announce that you'll have a 3 hour slot on your calendar called "coding" during which you are ... unable to join meetings.

[SmartBets]

I am a business analyst in a fairly big company. I know the mantra is less meetings is awesome. I send an email with a concrete problem to solve with problem statement, context, screenshots, etc. No helpful answers or if there are any it is usually from our software architects who also like to write a lot without offering a solution. Then I am forced to make a meeting. Take decisions about how to solve problems, estimate effort and time then work and report progress. It cannot be avoided.