Skip to main content

Configuring the Scrum for Team System template correctly

I really like the Scrum for Team System template for Team Foundation Server. The only problem is that it’s kind of hard to configure correctly. Only of all parameters are set correctly, the template will work and the correct reports are generated.
To simplify my job as an TFS administrator, I customized the template a bit to get a head start. When you install this customized version, the correct iteration tree is created, some work items are added and the relationship between these work items is set. So no longer complaints by users who can not get this template working, and more time for me to do some useful stuff.
Until a developer(yes, I’m talking about you Dennis) decides immediately after the Team Project was created to remove all this preconfigured parts. Back to ‘No data available’ in all reports…
So just as a reminder to myself, what are the steps you need to take to configure the template correctly:
Iterations
This is the expected iteration tree(Release -> Work Stream -> Sprint -> Team Sprint):
Planning Scope
Workitems
Create the following work items and set the iteration path accordingly:
  • Release: Project\Release
  • Sprint: Project\Release\Work Stream\Sprint
  • Team Sprint: Project\Release\Work Stream\Sprint\Team Sprint
  • Sprint Backlog Items:Project\Release\Work Stream\Sprint\Team Sprint
Create the following links between these work items:
  • Release (implemented by ->) Sprint (implemented by ->) Team Sprint
More information here: http://consultingblogs.emc.com/colinbird/archive/2009/09/11/getting-started-with-scrum-for-team-system-v3-beta-1.aspx
Labels:

Popular posts from this blog

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

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

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