As Charles joined this team, all seemed to be working perfectly. The team really got Agile, and they were following the ceremonies and producing high-quality software. But something was off. With time it became clear that there was a gap between the team and the stakeholders. Finally, the team realized that their project was about to be canceled. What happened? How could this team’s amazing work be canceled? The lessons Charles learned from that story are a critical warning for all of us. Listen in to learn what happened, and why you should start looking at your own team (even if successful) to look for possible early signals of the same pattern.
About Charles Rodriguez
Charles has been working in software development for 16+ years with roles ranging from a database developer to manager to agile coach all in an effort to 'try to make things better' for future generations joining the IT industry.