I got this great question in my inbox and here's my answer to it - a 🧵 (1/6)
#SoftwareDevelopment #Management
#SoftwareDevelopment #Management
A healthy workplace environment would encourage early communication and expectation management. There would never be "unexpected delays" there will always be "expected and well communicated delays".
2/6
2/6
Unexpected delays, besides emergencies and force majeurs, happen (in my experience) because of fear of retaliation and backlash from inexperienced managers when engineers communicate a delay!
3/6
3/6
When delays occur (and they will happen), if they're communicated upfront, one of these 3 things has to change:
- Number of engineers working on the problem / feature
- The scope
- The timeframe
4/6
- Number of engineers working on the problem / feature
- The scope
- The timeframe
4/6
Tolerance for delays also depends on the situation. Delays in a startup could lead to killing it, but delays in an enterprise might be shrugged off as just another day of work.
5/6
5/6
I'll be going live to talk about the differences of working in a startup, scale-up and enterprise this weekend, you can set a reminder here:
6/6 (fin)
6/6 (fin)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
