I can highly recommended not adding a reason at all for rejecting a meeting request. If I feel I do not need to attend at all I will let the organizer know. If the time conflicts with my schedule / plans I will simply ask for a reschedule. (And no, I’m not the CEO).
To some extent, but this is beyond what is acceptable. Even if this is so support COVID notifications. Any install on an unmanaged device should be asking for permission to install something, unless you opt-in or something.
I think poetry is rally gaining traction. Poetry solves some problems in an easy way that are cumbersome to replicate with pip (like guarding against supply chain attacks with lock files) and teams are starting to realize that basic use of pip and requirements.txt no longer is enough to manage dependencies. I am starting to more an more projects adopting poetry and the uptake seems to look like the uptake I saw in FastAPI. Side note: I tried using pipenv, but is was just too slow for resolving dependencies. Curious what other people’s experience is on this with pipenv and poetry.
Just the thought of Google being able to do something like this scares the $&@*#% out of me. How on earth can you trust a company that does something like this?
Below is not just my experience, but also from other teams I have worked with over the past 10 years in an agile / scrum setting.
Sprints:
- pros
Helps to avoid continuous changing direction at request of stakeholders. 2 week sprint feel really good as planning horizon: not too long, not too short. Teams do not commit to anything beyond that timeline. Any roadmap commitments are based on stats and product owner responsibility. Team is not accountable for any missed deadlines.
- Cons:
It can feel like wash-rinse-repeat sometimes. Can be a killer for flow and feel inflexible when you are nearly there (getting it done) and the sprint review interrupts the flow. If the balance is bad you should probably look at kanban.
Daily’s:
- Pros
Excellent way to find out if team members need help or some syncing is needed. If done well team will “feel” if your getting closer to getting everything done. With work from home good to see everyone on the team at least once a day.
-Cons:
Hard to get right. Should be about inspection by the team to help adapt the plan and get to your goal, but this is often forgotten. Might become a way to “control” the team and put pressure on people and check for performance of individuals.
As for micromanagement: this is not exclusively found in agile / scrum. A micromanager will find a way to abuse any method to “control” their world. If you let go, set a clear purpose and direction, start helping team members to get more autonomous you will find that performance goes beyond what micromanagement can achieve.
Scrum (as defined in the scrum guide) can work, when it doesn’t: adapt and try again.