I’ve observed three things about the current state of the tech industry. First, it has laid foundational knowledge of best practices for software development with Agile. Second, it has focused on enhancing technical knowledge across all roles, including business roles. Finally, it’s searching hard for “What’s next?”
Is “What’s next?” a new framework? That answer is 20 years coming, built on the foundation of what I’ve spent my entire career watching: processes, training, and improvements for developers that are in service to some other role’s requirements instead of seen through the lens of their own viewpoint.
What happens when a company puts 14 years of effort into a developer tool that includes business processes like planning and status checks? What happens when the business uses the language of engineering and software development instead of CEO-speak? Most importantly, what happens when that same team builds automation and AI tools that accelerate their development speed by ~ 40%?
That’s the GitHub story from the Agile point of view. It’s a good one, but it is also one that will tell a story about the actions that we all should be taking with our careers. Change is constant! Be prepared.
Learning Outcomes:
- Why it is important for us to think from a developer-centric viewpoint
- How did the developer-centric viewpoint already change the Agile industry
- How to take a developer-centric viewpoint when approaching business problems
- How automation and AI will impact repetitive business processes
- How to prepare for these coming disruptions by uncovering better ways of developing software by doing it and helping others do it
