public void Photograph()
public void Photograph()

A dad and a software architect with a passion for photography and music. These are my thoughts and opinions, sometimes accompanied by code and photos.

A proud father, enthusiastic guitarist and passionate software engineer, geeking out in the cloud. Briefly a Microsoft MVP for Azure before forfeiting the title when I joined Microsoft UK.

Share


Twitter


SWOT analysis of Visual Studio Online

Deciding to go with a tool like VSO, for a company, is not easy. There are several alternatives, including free ones, that give you just as much, maybe even mor…

Anže VodovnikAnže Vodovnik

Deciding to go with a tool like VSO, for a company, is not easy. There are several alternatives, including free ones, that give you just as much, maybe even more - in terms of pricing and/or flexibility. So, in order to get our team to use it (or not), I prepared a SWOT analysis (Strengths Weaknesses Opportunities Threats). I wanted to make it available so that it might help someone in a similar position make their case.

The Process

Visual Studio Online does not allow any major process customizations (yet), although it is by far one of the most requested features. Do note, however, that the feature is now planned, which means that it should see light of day in the semi-near future. Now, that said, it means that before you dive into SWOT analysis, you need to understand how your process is established in your development team. If you are using a fairly plain-old Agile process, like SCRUM, you should have no problems using the built-in template. Same goes for the classic template that was in Team Foundation System before.

In our case, we actually have two separate processes established. One is a content process and the other is the development process. They are formally separated, which gives the team a bit more options on which tools to use to support the process. We decided to opt for a simple, no modification, Agile/Scrum process.

Wishes

The team made a couple requirements/wishes before we set out to analyse different tools:

Strengths

WEAKNESSES

Opportunities

Threats

In the end, we decided to evaluate VSO for our team and are using it to see if our analysis proves correct. I hope the above points help someone from another company make their case, one way or another.

 

A proud father, enthusiastic guitarist and passionate software engineer, geeking out in the cloud. Briefly a Microsoft MVP for Azure before forfeiting the title when I joined Microsoft UK.

View Comments