Attachment with the sample: NugetPackageRestore.zip

Today I had a problem using nuget package restore in a quite complex project that has multiple projects and multiple solutions file located in different folders, so that nuget was restoring the packages in a wrong folder for some of my solutions.

For instance if you have a file structure like this:

AllMyProjects.sln simply contains all the projects (ProjectA.Model.csproj, ProjectA.Service.csproj, ProjectB.Model.csproj, ProjectB.Service.csproj).

When you run the build for all the 3 solutions, nuget by default will restores everything in a folder “packages” located at the same level of the solution file, producing something like this:

Now, if you first compile the ProjectA.sln and ProjectB.sln, also the AllMyProjects.sln will compile fine, but this just because the packages will be correctly restored by the two specific solution ProjectA.sln and ProjectB.sln, but if you try to clean up all the packages folder, and build the AllMyProjects.sln first, you…

Capacikill? What the … is that?

Actually it is a word I made up. To be honest it was a colleague who talked about capacity in a noisy room and I thought I heard him say it. I understood capacikill and the word had a meaning to me right away. As you can obviously see, it is a merge of the words capacity and kill but what do I mean by it?

This blog post is about giving meaning to this word to others besides me.

Scrum vs. Capacity planning

When doing Scrum in its purest form, capacity is the easiest thing to manage. There is a Scrum team consisting of a number of people. These people work full-time on sprint work. Capacity is simple. (Number of people in Scrum Team) x (Number of Days in Sprint) x (Number of Hours per Day)

The team maintains remaining work and this…