Freigeben über

TFS Version Control team's mission

  • Artikel

Twice a year the entire version control team meets in a big conference room, full of breakfast goodies, to talk about our current strategy, release execution and market challenges. The meeting lasts for around 1.5 hours and it gives us a chance to step back and see how our day to day activities and decisions are aligned with the bigger picture.

What I want to do today is tell you a bit about our mission and the high level principles which control a lot of what we do as a team. Lets first start with sharing our mission statement, not to be confused with our vision which can be a topic for a later blog post.

Mission: Transforming Version Control

Our mission is short and centered on the fact that version control tools and the SCM field are due for a significant shift. We say this because if you look at the last twelve or so years we have only seen incremental innovation on the market with no radical blue ocean changes. Looking into the future we believe that version control will transcend from predominantly versioning source code items to being a service on an integrated server which is able to version any type of asset and with enough smart to track and enable workflow's that provide rich and immersing experiences on the "right" consumer scenarios. If you read a lot about the SCM market you might say that we share a similar view with one of our competitors, as evidence by this published article: https://www.ddj.com/architect/188500238 . I would say partly yes and the part that separates our views is that for us is not only about versioning items and understanding their extension semantics, but really about versioning, recording and tracking the behavior/ interaction of these items with outside entities and integrating those worlds together.

Lets provide a simple example to make this a bit clearer: take a service that keeps track of the routes you have taken between two points (e.g. your house to a restaurant of a new friend's house).  A normal version control system will version the routes from the different origination points and allow the user to retrieve that information with a request. For us that information is not not enough, so we would want our system to understand why you took that route and then attach that behavioral metadata automatically. Was it because there was an accident and you had to take a detour? Was it because it was raining and you felt the highway was faster? etc. We want to bring these outside entities into the picture so we really get the full picture of what we are versioning. This will take some time but we believe that is attainable and will be an integral part of the SCM shift that will take place over the next seven years.

With our mission statement briefly explained lets quickly go thorough our High Level Principles which are responsible for steering us in the right direction:

  • Innovation: this is the area where we need to lead and really show what you can do with a powerful version control service that is part of an integrated server experience. The first release of Team Foundation Server I think showed the market the potential of that strategy, now we need to continue to execute and bring the most innovative features to market with each release
  • Ease of Use: this principle speaks to the fact that we can put a lot of features and technology in the product but if people cannot use them effectively there might as well not be there. This is an area where we have increased our focus so I can't wait to see what you guys think of our progress when we release our next version.
  • Collaboration: no significant amount of work or big accomplishment gets done by only one individual, hence team and team collaboration are an integral part of the version control experiences. This principle is about leveraging the current systems available (Sharepoint sites, Wikis, IM, email) and building rich experiences on top of architectures (i.e. Office Unified Communications) in order to allow all members of the team to effectively collaborate on the project
  • Community: Open Source showed and proved on a mass scale the power of communities. For us to succeed we need a healthy community that is not only providing great feedback to us but also contributing value to the SCM industry; only like this would we increase healthy competition and drive up innovation
  • Enterprise Ready : This is really about scale / performance and in today's world compliance

There you have it, a short detailed look at our mission and principles. You will see our team executing on them on different levels throughout the course of the next release and hopefully at the end we can look back and see how much closer we are from fulfilling the mission.

-- Mario

Comments