

I was once asked to investigate two teams that worked together to build a software product for doing taxes.
The first team said they needed help with releasing software better.
So I planned to use an interview I'd come up with over the years.
It had questions I could ask people about how they work together.
Things like how they gather requirements, test the software, and approve releases for example.
While interviewing the first team,it became clear that they didn’t like the second team.
The first team was following scrum, while the second team was not.
However after interviewing many people on both teams, we realizedthe second team was following kanban.
But they were doing it for a good reason - to respond to unpredictable changes in tax code.
So eventually we presented our findings, and though many people were pleased -our client was disappointed that we handn't found only issues with the second team!
In this video, I share some things to consider that might help you avoid being used as a pawn in corporate politics.
I hope it helps you if you're ever pressured to side with a group of people to force another to change unwillingly!
Visit my site to watch the full video (or listen as a podcast):
📺 Watch or 🎧 Listen
🔔 Subscribe for over 100 videos on healthy software development
Top comments(3)

- Email
- LocationE EU
- EducationBachelor of Economic Informatics
- WorkCloud Engineer at CrowdStrike
- Joined
Investigations, methodologies, blames, delays in delivery, yep..sounds corporate.

- LocationAustin, Texas
- WorkSoftware Development Career Coach at Jayme Edwards Coaching
- Joined
No problem Phil, glad you’re getting something out of this stuff. 👍🙂
For further actions, you may consider blocking this person and/orreporting abuse