It has never been easy to change its development process for either an engineer or a team, because it is more than just a process. It is a change of culture, mindset, tools that the entire team, division or even the whole company needs to apply. I was in a fortunate position where I was able to observe and/or experience the big shift of software development processes happened within Microsoft in the past seven years. In this talk I am going to share my experiences as a software engineer in Microsoft, mainly focusing on 1) when I joined an agile team and 2) when a team transitioned from waterfall to agile.
Building a great software service needs to be customer-focused, data-driven, and fun-driven. This is culture that the management team is mainly responsible for. As software grows, it is more important to embrace collaboration rather than competition. But it does not mean that every team member can do the same things; it means everyone is different has different skill sets and the management team needs to direct them effectively.
There have been a number of learnings since I, a Japanese engineer moved to the U.S. regarding how to work as a software engineer. I am going to cover some of them which are highly related to the recent trend in Japan regarding working improvement.