Blog

Upgrade your Sprint Retrospective Meetings

Aug 14, 2012  •  Richard Hundhausen


Tired of asking each other "how the Sprint went"?

Try one of these alternate Sprint Retrospective activities to change the pace a bit:

Check them out and give them a try at your next Sprint Retrospective meeting. If I’m missing one, please let me know.

Scrum

TFS #loc.MinimumNetFXVersion and Windows 2012 0x0000005D

Jul 3, 2012  •  Simon Reindl


A tale of two error in the path to RC install.

I wanted to install the RC of TFS2012 to do some upgrade proving. To  keep up to date the target is Windows Server 2012, running SQL 2012, and TFS2012 on VMWare Workstation 8.0.

To keep it light to start with – no SharePoint.

So I rolled out my Windows 2012 Server Beta and got the error:

image

Misc TFS Windows

Implementing Scrum Using Visual Studio 2012

Jun 11, 2012  •  Richard Hundhausen


Updated 6/12/2012 : Since my breakout session today was on the same topic, I thought I would just hitchhike onto this post from Sunday. My presentation and an updated ScrumRobot are available for download below.

Wow. What a great pre-conference yesterday at Microsoft TechEd in Orlando. Thanks to David Starr and the 80+ folks who were interested enough in the topics to hang out for the all day conversation.

image
Photo: Teams self-organizing to build a Product Backlog. You can find more photos here.

Conferences Scrum TFS Visual Studio

Which Scrum Team member should set PBI and Bug work item states?

Jun 8, 2012  •  Richard Hundhausen


This is a fairly common question, usually by teams new to Scrum. The Scrum Guide clearly identifies the roles and their responsibilities. Team Foundation Server does not. It only identifies security groups and permissions.

Teams that have been using Scrum for a while should answer: "Let the team decide". I’m good with that answer.

For team members that don’t yet know where the rules of Scrum stop and self-organization begins, I provide the following guidance on who should "flip the switch" at each state transition of a PBI or Bug work item type:

Scrum TFS

Scrum Fundamentals Workshop in Boise

May 2, 2012  •  Richard Hundhausen


Thank you for attending the workshop yesterday. You can find the presentation link below.

It was three hours of packed information (and a packed room). I believe we had around 90 people in the workshop.

image

The workshop focused on five primary topics:

  • Scrum is popular (because it works)
  • Scrumdamentals (the fundamentals of Scrum)
  • Using Scrum
  • Continuous Improvement
  • Next Steps

As I mentioned, there are some good resources for you to bookmark:

Conferences Scrum

Running nUnit in a TFS11 build on 64 bit server

Apr 30, 2012  •  Simon Reindl


Overview

In TFS/VS 11, frameworks other than MS Test are supported, which is cool. Peter Provost mentions them here.

OK, so you start to use this great new feature, queue up a team build and the tests aren’t run.

Assem Bansal has a great article here, so you do that, and no tests are run either. Confusing. The issue is that the 64 bit version is not picking up the reference to the test extension even when it is installed. Hey, it is a beta!

Development TFS Visual Studio Visual Studio ALM

Reporting Waste with TFS

Apr 11, 2012  •  Simon Reindl


Tracking waste in TFS

Overview

Tracking waste and gathering the empirical data is one of the most effective ways of convincing people for the need to adapt.

This needs an Estimated Effort field, as in Scrum for Team System template.

This can be done with the MS templates, by adding this field in.

You need to use the estimated effort field, so that the burndown is not affected.

Steps

Within the area path of the team project, create a top level area called waste, under that add the key waste areas as you become aware of them

clip_image001

Whenever a team member encounters an issue that is causing them to lose time, they create a Task (Sprint Backlog Task in SfTS 3) and set the Area path (feature scope in SfTS 3) to be waste and the sub area if known.

Then update the estimated effort with the amount of time lost.

clip_image002

Set

Estimated Effort = time lost

Planning scope/Iteration Path = sprint

Work Remaining = 0

Feature Scope/Area Path = WasteSubArea

Description = Meaningful comment

Title = Meaningful Title

Create a separate work items or update the work item as and when further waste is identified.

Reporting

Create a new work item query, and save it with a meaningful name. I have used "Waste Query"

clip_image003

Add the columns that you want to report on, by editing the column options. I have added the Estimated Effort and Area Path columns

clip_image004

After saving the query, you can then open it up in excel and create a report with a pivot table and a chart to help create transparency regarding waste

clip_image005

Other Process Templates

For this to work with other process templates, you will need to add in an "Estimated Effort" field to the Task work item

Misc Preferred Practice Scrum TFS Visual Studio

Create Yesterday’s Work Items Today

Apr 8, 2012  •  Richard Hundhausen


Team Foundation Server 11 has made it even easier to create a work item with a date prior to today. Awesome. So, why would you want to do this? Work with me here …

Maybe you are importing requirements, test cases, or bugs from another tool. Maybe you want to back-fill a Sprint backlog with tasks you were tracking by hand. Maybe you want to create a utility to automatically populate several sprints of work in order to generate and study the burndown and velocity reports. Ok, maybe that last one is just interesting for me as I’m writing my latest book.

TFS Visual Studio

Upgrade TFS 2005 to TFS11 Beta

Mar 20, 2012  •  Simon Reindl


This is one journey to upgrade TFS 2005 to TFS11

Key points if you are in a hurry

You only get one chance at the upgrade, on the initial install. You need to do this as two upgrades TFS2005 –> TFS2008/2010 –> TFS11.

Two Step Warning

TFS2005 to TFS 11 is not supported in the documentation. Upgrades from TFS 2008 and 2010 are supported. You need to migrate to TFS 2010 first, and then to TFS11.

Preferred Practice TFS Visual Studio