We Were Hired For A Hidden Agenda
Ever been on a software development project where a scrum team is putting pressure on another because of a hidden agenda?
I was once asked to investigate two teams that worked together to build a software product for doing taxes.
The first team contacted us and 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 did't like the second team.
The second team wasn't following scrum, while the first team was.
The first team was convinced the problem was with the second team.
However after interviewing many people on both teams, we realized the 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 the story of how I had to avoid being used as a pawn in corporate politics at my client.
I hope it helps you avoid being put into a situation where you're pressured to side with a group of people to force another to change unwillingly!
Subscribe for more healthy software development videos!
https://bit.ly/2I0sXay
#programming #stories #career
Видео We Were Hired For A Hidden Agenda канала Healthy Software Developer
I was once asked to investigate two teams that worked together to build a software product for doing taxes.
The first team contacted us and 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 did't like the second team.
The second team wasn't following scrum, while the first team was.
The first team was convinced the problem was with the second team.
However after interviewing many people on both teams, we realized the 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 the story of how I had to avoid being used as a pawn in corporate politics at my client.
I hope it helps you avoid being put into a situation where you're pressured to side with a group of people to force another to change unwillingly!
Subscribe for more healthy software development videos!
https://bit.ly/2I0sXay
#programming #stories #career
Видео We Were Hired For A Hidden Agenda канала Healthy Software Developer
Показать
Комментарии отсутствуют
Информация о видео
16 июня 2018 г. 4:25:23
00:07:50
Другие видео канала
A Tale Of Software Development Culture Change - Gone Wrong!Why Do Managers Treat Programmers Like Children?I Quit My Software Project To Get Healthy!Why Do People Take Credit For Your Ideas?How Agile Teams Grow Toxic! Ep. 4 CommitmentsDaily Scrum Meeting: A Status Meeting In Disguise?I Fired a $100,000+ Web Development Client !!!How to Choose a Freelance Niche - for CodersScrum Got 3 People Fired From A Software Project!My Recovery From Programmer AngerLead Software Developers Better By Letting Go!Why Do So Many Programmers Lose Hope?5 Signs Your Software Business Is Led By Amateurs!Should You Really Measure Progress On Software Projects?Intro: Types of CMS - Traditional CMS, Headless CMS, DXPWhat Is DevOps REALLY About? (Hint: NOT CI/CD)How To Spot A Person With A Hidden AgendaThey Watched Us With Webcams And Rewrote Our Code!Is Your Software Development Leader A Narcissist?It’s Hard To Keep A New Team Doing Continuous Delivery