Skip to main content

Installing the Visual Studio Scrum Process Template

I blogged before about the Visual Studio Scrum 1.0 Process Template. But how do you get it installed?

Step 1 – Download the template

The process template is hosted at the Visual Studio Gallery. The easiest way to download the template is using the Extension Manager in Visual Studio 2010. Open Visual Studio 2010, and from the main menu, select Tools | Extension Manager. Select the Online Gallery tab on the left side of the window, and search for ‘Scrum’. Select the Microsoft Visual Studio Scrum 1.0 Process Template from the list and click the Download button. Once the file has finished downloading, click Close on the Extension Manager window to close it.

Step 2 – Install the template
You have to install the process template on your local machine before you can import it into Team Foundation Server 2010. To do that, doubleclick on the MSI and follow the installation procedure. If you left all the default settings, the Process Template is installed in the C:\Program Files (x86)\Microsoft\Microsoft Visual Studio Scrum 1.0 folder.

Step 3 - Importing the template

Importing the process template into Team Foundation Server 2010 is the same as for all other templates. Open the Process Template Manager in Visual Studio 2010 by selecting Team | Team Project Collection Settings | Process Template Manager. Click the Upload button and navigate to c:\Program Files (x86)\Microsoft\Microsoft Visual Studio Scrum 1.0\Process Template.

Step 4 - Installing the Scrum Dashboard Feature
As a last step you have to install the Scrum dashboard feature. Therefore you have to copy the Microsoft.TeamFoundation.Sharepoint.Scrum.wsp file found in the Project Portal folder to your Sharepoint server. Afterwards follow the procedure as described here to upload and install the wsp to your Sharepoint server.

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more