This week I received some great news.  The session I gave my colleague Peter Doomen @ XPDays Benelux 2010 (All info here) is selected as one of the 12 best session.  We now going to redeliver our session @ the Mini XP Day on April 1st 2011, In Mechelen (Belgium).

More info will follow.

This year, the 8th edition of the XP Days Benelux takes place on November 25-26th 2010.  The location is Kapellerput in Heeze (The Netherlands).

Together with my colleague Peter Doomen, I'm selected as a speaker.  The session we are going to deliver is the Frog Factory. Read more about this session here and here.

All the info about the XpDays can be found here.

May we have your vote please? Together with 3 colleagues, I participate on the PMI Agile contest on YouTube. Have a look at our presentation Agile @ SD Worx YannicHelsen and give us your vote! How to? Sign in on YouTube, become a member of the PMIAgile group on http://lnkd.in/BpXYNP  , click on our video (“Agile @ SDWorx” YannicHelsen) and vote for use by clicking I love it! Tnx in advance!

This is the video:

Mattias Skarin aka Crisp posted a nice small article with a case study about a team that is transformed from Scrum to Kanban.  He also put a few things he learned from this process, but also mentioned that they still have a way to go.

So if you are interested in this, read it here: http://blog.crisp.se/mattiasskarin/2010/04/27/1272362964756.html

Yesterday evening, my work hosted an event for the Belgium Agile Usergroup.  The main stream of this is evening was "Using Kanban Beyond Software Development".  Together with 2 colleagues (Peter Doomen and Sofie) I was one of the presenters.

There were 3 presentations and one open space:

1. Kanban in a complex administrative world (Sofie)
2. Kanban for support of development teams (Sven)
3. Kitchen Kanban - Cooking 13 different plates for 1600 people with Kanban (Peter)
4. Kanban is better than Scrum because... (Open discussion)

Afterwards we had a small break out session with following topics:

1. Discuss the result of the Open Discussion
2. Presentation of the Kanban Game
3. Evaluation: What did we learn today?

In total, we had 4 time slots (of 20 minutes).  Each presentator has given his presentation twice in one of the timeslots, so he could follow one of the other sessions.

It was a no slide presentation, but we made one A0 poster for each presenter. Here's my poster

 

As promised in my previous post about the Kanban Experience, now all the info about the game with played.

You can find everything on the blog of colleague Peter Doomen. In this article he explained the game and offers everything as a free download (read the rules for downloading it). So go here and enjoy: http://www.aboriginemundi.com/index.php/2010/04/the-frog-factory-a-kanban-experience-game/.

If you have feedback to the game, you can always contact me or Peter.  So we hope you enjoy it and can give us some great feedback.

Yesterday, I gave a two hour introduction about Kanban together with a colleague of me (Peter Doomen).  We had a group of 9 people, not only IT people, but also a few from the business itself.

The introduction to Kanban was in a game format: The Frog Factory.  During and after this game there was time to do some groups discussions.  At the end we gave a short theoretical overview about Kanban.

During the discussions, it was clear that the problems they had during the game, were a good reflection of what they encountered during there daily job.

More about the game and a few pictures later.

A nice article about Kanban for managers.  Read it here: http://www.kanbandistilled.com/

You always want to know what the ScrumMaster is doing in your team/company?  Well now it's the time you will find out.  Scrum Alliance has posted a nice article with the task of a SM.  Little remark, this list varies per company. So read it here: http://www.scrumalliance.org/articles/160-what-does-a-scrummaster-do.

You want to use Kanban or you are already using it.  But you also have used Scrum or know Scrum.  Both are the buzz words at this moment in the Agile world.  But still you don't know which one is the best in common or the best for you?  Are they related to each other? Could you easily adapt both together?  Is it easy to make a switch form one to the other?

Henrik Kniberg and Mattias Skarin from InfoQ have writen a book to clear this fog for you.  the book includes following chapters:

• Kanban and Scrum in a nutshell
• Comparison of Kanban and Scrum and other Agile methods
• Practical examples and pitfalls
• Cartoons and diagrams illustrating day-to-day work
• Detailed case study of a Kanban implementation within a Scrum organization

You can download it for free or buy the paper book.  Read everything here: http://www.infoq.com/minibooks/kanban-scrum-minibook.

When you use Scrum, most people think it's not compatible with Process Improvement Models like CMMI.  At my work CMMI is used by the testers for structured testing. So we have a Lova and Hate situation.

Well, the following article proves that we are wrong and the there's a Love and Marriage situation: http://www.stsc.hill.af.mil/crosstalk/2010/01/1001Glazer.html

(Thanks to my colleague Tom Vercauteren for the link)

A little psychology.  Michael Dubakov has wrote a nice blog post about saying no when using Kanban.  especially for your WIP limit.  Read it here : http://www.targetprocess.com/blog/2009/12/kanban-psychology-can-you-say-no.html

Limitedwipsociety.org has provided a list of usefull Kanban and Lean Agile tools.  Some are still under construction.  So if you're into this go here and find out the tool that suits you the best: http://www.limitedwipsociety.org/resources/tools/

I must say, a difficult question, as both methodologies have a different audience and way of use.  Although Kanban is of the same family as Scrum.  in fact, in my opninion it's a light weight Scrum with a more dynamic area.  I'm going to setup Kanban for our team here after my holiday (somewhere around mid november).

But about our question, Doug Shimp has wrote a nice blog article about it.  You can read it here: http://doug-shimp.net/scrum-faq/will-kanban-replace-scrum/

You don't know anything about Scrum, but want to know more about it, well here's some help.

Mike Cohn has made a nice presentaiton "Introduce Scrum to your team, ScrumMaster and Product Owner".  The nice thing is that this presentation is already availlable in 14 languages.

Read more here: http://www.mountaingoatsoftware.com/scrum-a-presentation

• Has Agile lost it's spirit?
• The Agile Playground
• Leading Views: Leadership Isn't a Reward

Roy Osherove has blogged an interesting article on his Team Leadership blog Five Whys.  In this article he talks about how many time a team lead should be with his team to be an effective teamlead for his team.

So if you're a teamlead reaad this article : http://5whys.com/blog/spend-at-least-50-of-your-time-with-your-team.html

After two years, the Microsoft Scrum template for TFS is maintained.  You can read all info on Brian Harry's blog : http://blogs.msdn.com/bharry/archive/2009/06/10/the-future-of-escrum.aspx

If your are looking for the Scrum template of Conchango, well read their announcement about the template : http://blogs.conchango.com/stuartpreston/archive/2009/05/19/scrum-for-team-system-v3-0-plans.aspx

The Patterns&Design team released some new eBooks.  This time it are 6 pocket guides.

1. Agile Architecture Method Pocket Guide
2. Web Application Architecture Pocket Guide
3. Mobile Application Architecture Pocket Guide
4. RIA Architecture Pocket Guide
5. Rich Client Application Architecture Pocket Guide
6. Service Architecture Pocket Guide

So happy reading for the end of this year.

Microsoft has released 2 new P&P guidelines.

The first one is about Distributed Agile Development.

This guideline contains a white paper and an Agile Development Showcase.

Agile Development Showcase: http://msdn.microsoft.com/en-us/dd128747.aspx

PDF: http://download.microsoft.com/download/4/4/a/44a2cebd-63fb-4379-898d-9cf24822c6cc/distributed_agile_development_at_microsoft_patterns_and_practices.pdf

The second one is about Acceptance Test Engineering.

This guideline is still in beta1.

Codeplex site: http://codeplex.com/TestingGuidance

Project Announcement: http://www.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=TestingGuidance&DownloadId=40458

Community: http://www.codeplex.com/TestingGuidance/Thread/List.aspx

Finally a new weekly links list.  The previous one was more then a month ago :-(.  One of the reasons is that I hadn't much time and I'm also having troubles with my knee.  In about 4 weeks I'm going to have an operation and then I'm out for at least 3-4 weeks.

Agile:

Applying agile practices in still-waterfall processes : http://blogs.msdn.com/architectsrule/archive/2008/04/08/applying-agile-practices-in-still-waterfall-processes.aspx

Office:

Outlook SMS Officer :/http://blogs.msdn.com/outlook/archive/2008/04/07/introducing-smsofficer.aspx

TFS:

CTP Team System Web Access 2008 SP1 - What's new : http://blogs.msdn.com/hakane/archive/2008/04/09/what-s-new-in-tswa-2008-sp1.aspx
CTP Team System Web Access 2008 SP1 - Download : http://www.microsoft.com/downloads/details.aspx?FamilyId=A06ED577-DE38-426F-9341-3F78E46DA09A&displaylang=en
CTP Work Item Web Access 2008 - What's WIWA : http://blogs.msdn.com/hakane/archive/2008/04/09/what-is-work-item-web-access-wiwa.aspx
CTP Work Item Web Access 2008 - Download : http://www.microsoft.com/downloads/details.aspx?FamilyId=FAED8359-F54D-480E-8A86-F154D3DEA07E&displaylang=en
Richt text in work items : http://blogs.msdn.com/teams_wit_tools/archive/2008/04/09/rich-text-in-work-items.aspx
March TFS Times newsletter : http://www.tfstimes.com/news/
March '08 Team Foundation Server Power Tools Released : http://blogs.msdn.com/bharry/archive/2008/04/21/march-08-team-foundation-server-power-tools-released.aspxv
TFS Sticky Buddy from Martin Hinshelwood : http://www.codeplex.com/TFSStickyBuddy

Visual Studio:

A new place for the Visual Studio hotfixes : http://code.msdn.microsoft.com/

As I'm a big fan of using Scrum in your project, I came aware about the Softhouse site.  They have some interesting material about Scrum to download.

But the most interesting part is the PDF that explains Scrum in five minutes.  You can use this info to give people, who don't Scrum, a high level overview about this Agile method.

This is the last part of the series posts about scrum under TFS.  We'll end this story by taking a look into the future by having a sneak preview at the Scrum templates for Visual Studio 2008.  Read our previous parts here:

• Part one: Introduction
• Part two: The installation
• Part three: User experiences
• Part four: Feature overview
• Part five: Conclusions

This article is also cross posted on the Ordina blog.

What about Team System 2008 ?

We looked at each of these templates in 2 ways:

1. Does the template still works after an inplace upgrade to TFS 2008?
2. Is there a new (upgraded) version available specifically for TFS 2008?

Microsoft eScrum

After an inplace upgrade, the template was still up and running. Only the website suffered a painful dead. Brian Harry was so friendly to post a solution on his blog. Go check it out!

VSTS Scrum Process Template

Everything keeps working after the inplace upgrade. A newer version is available here.

Conchango Scrum for Team System

No problems occured after the inplace upgrade. Scrum for Team System v2.0 is now available. Don't hesitate and download this template here.

Conclusion

Microsoft did a good job in terms of backward compatibility. After using the upgraded versions of the templates for some time, I did not encounter any problems. If we look at the new releases, we'll find a range of improvements. But this will be a story for a future series of blog posts.

So stay tuned for an updated version of these posts where we'll dig deeper into the new features of the updated Scrum templates for Team System 2008.

Your TFS Scrummasters

Bart Wullems and Sven Cipido

The fifth part of the series posts about scrum under TFS.  This time we will give a final review and our conclusion about the Scrum templates under TFS2005.  Read our previous parts here:

• Part one: Introduction
• Part two: The installation
• Part three: User experiences
• Part four: Feature overview

This article is also cross posted on the ordina blog.

Final review

eScrum

Advantage:

• Much SCRUM functionality on board
• Easy to use
• Lot of reports specific Scrum
• Has web front end

Disadvantage:

• Scrum à la Microsoft
• First version contains lots of bugs
• Extra libraries needed if you want to use the site also.
• Difficult installation, it’s a pain in the ass
• No help in Visual Studio
• Sometimes slow.  But the test was under a VPC, but you still need a heavy server.

CodePlex

Advantage:

• Easy installation
• Guidance Explorer
• Very easy, very common as working with the standard TFS, just some renaming. 

Disadvantage:

• Not a many extra’s like reports
• No daily scrum
• In fact doesn’t follow the Scrum guidelines

Conchango

Advantage:

• Implements mostly the Scrum guidelines
• Easy in use, and very low learning curve
• Several skillfull tools added
• Very good reporting

Disadvantage:

• No web interface

Conclusion

If you want to use Scrum in TFS, Conchango is for the moment the best (free) solution.  The very good reporting with the skillfull tools makes it a pleasant experience.
eScrum has a lot of potential, but sometimes drops a stitch.  A very good point is the web interface.
Codeplex in its current form has too many limits to use in practice.  Although there is a final version (since September 2007) which seems to go on the good way.

So this was the fifth part.  In the next part, we'll talk about the Scrum templates under TFS2008. 

Your TFS Scrummasters

Bart Wullems and Sven Cipido

 

The fourth part of the series posts about scrum under TFS.  This time we will give a complete overview of all the features of the Scrum templates.  Read our previous parts here:

• Part one: Introduction
• Part two: The installation
• Part three: User experiences

This article is also cross posted on the ordina blog.

We'll start by explaning the different criteria we looked at:

• Licensing: What are the licensing conditions? Is it free to use?
• Installation: Which format has the provided setup? Are there any installation guidelines?
• Web Interface: Is there a separate web interface available?
• Real Scrum: Does the template follows all the Scrum principles?
• Process Guidance: Is there any form of process guidance available?
• Workitems: Which workitems are available?
• Custom reports: Which custom reports are available?
• Custom queries: Which custom queries are available?
• Overall quality: How did we rate the overall quality of the template? 
• Bugs found: Did we found any bugs while testing?

 

	Microsoft eScrum	VSTS Scrum Process Template	Conchango Scrum for Team System
Licensing	Free	Free	Free
Installation	MSI	Zip	MSI
Web Interface	Y	N	N
Real Scrum	N	N	Y
Process Guidance	Y	Y	Y
Workitems	Bug eScrum Product Backlog eScrum Product Details eScrum Sprint Details eScrum Sprint Retrospective eScrum Sprint Task	BackLogItem Defect Impediment Review User Story	Product Backlog Item Release Sprint Sprint backlog item Sprint Retrospective Item
Custom reports	Product Summary Sprint Burndown Sprint Cumulative Flow Sprint Metrics Sprint Retrospective Sprint Totals	Burn Down chart Tests Failing without Active Defects Tests Passing without Active Defects	Bug Count Bug History Chart Bug Priority Chart All Product Backlog Items All Sprint Backlog Items All Sprints Delta Report Impediment Report Product Backlog Composition Product Burndown Chart Product Cumulative Flow Retrospective Report Sprint Burndown Chart Sprint Cumulative Flow Sprint Overview Chart Sprint View Version
Custom queries	All eScrum Product Backlog Items All eScrum Product Details All eScrum Sprint Details All eScrum Sprint Retrospectives All eScrum Sprint Tasks My eScrum Product Backlog Items My eScrum Sprint Tasks	Active Defects All backlog Items Impediments My backlog items My defects My impediments My reviews Project checklist Resolved defects Untriaged defects	All impediments All product backlog items All sprint backlog items All sprint backlog tasks All sprint retrospective items All sprints My impediments My sprint backlog items My sprint backlog tasks My sprint retrospective items Recycle bin
Overall Quality	**	*	***
Bugs found	Y	N	N

 

So this was the fourth part.  In the next part, we'll do a final review and make some conclusions. 

Your TFS Scrummasters

Bart Wullems and Sven Cipido

The third part of the series posts about scrum under TFS.  This time we will focus on the usage of the Scrum templates.  Read our previous parts here:

• Part one: Introduction
• Part two: The installation

This article is also cross posted on the Ordina blog.

Use the Scrum templates

Common

Create your Team Site with the correct Template.  Once you have chosen a template, you can’t change to another template only make minor changes to the chosen template.

eScrum

Learning eScrum from within TFS is very difficult as there is no guidance.  So there is a lot of searching what everything means. For example: product backlog details, area, sprint backlog details.

The best way to learn this product is by using the web interface.  Here you can find a context sensitive help for each part which explains you very well what it means.

You can group several product items by using the areas.  There can be several areas’ which can contain several products.

A sprint is the same as iteration in TFS and the product backlog details in Scrum is the description in TFS.
Sprint information (Scrum master, start and end date of the sprint, goal,…) can be filled in the Sprint details

When using TFS to add your sprint items you have to connect manually the backlog ID.  This is done automatically when using the web interface.

In common we can say that the web interface is more handy and user friendly to use than TFS.  Although that the web interface has a few issues.  There are times that items disappear in the web interface.  But when you restart they’re back.  Also it seems that the page refresh after a post back not always work.  And in some cases you need a full refresh trigger (F5) before everything will be showed again.

Also viewing some reports seems to give problems, but after you rebuild the data warehouse this is solved.
The biggest disadvantage of eScrum is that not all the Scrum guidelines are followed.  Microsoft shouldn’t be Microsoft if they haven’t give it their own interpretation.  For example the burn down chart doesn’t give an overview of the complete sprint, but only to the current date.  This doesn’t give you a complete overview of the sprint.  Also when you want to book more hours than initial planned on a sprint task, eScrum gives sometimes strange results.

CodePlex

Codeplex has the less connection with Scrum.  There is no product backlog only the sprint backlog.  Making sprint items is equal to making work items.  During this phase you also include the item to an iteration.  There are 3 reports and the rest are just the standard reports.

Most of the changes are just a rename of the standard VSTS items.

The name Lightweight is well chosen.

Conchango

Using this template gives us a very nice user experience because it’s totally converted to Scrum

When creating product backlog items or sprint items, you have to fill in the manually the sprint number, which is defined separately.

There is no direct connection between the product backlog items and the sprint items, but you can link them through the Links tab.  This is the best solution, because you can’t create a hierarchical structure in VSTS 2005.

They have integrated a recycle bin, so if you “delete” (which means status is set to deleted) a Work item, you can recover it from here.

There are a few administration modules available which gives us extra possibilities.

It’s easy to maintain the users through the separate Administration tool “Listmanager”.  Through the Administration module “Report installer” you can choose which reports are available per project.

If you want a direct update of for example the burn down charts, you can use the “Warehouse manager” to push a direct update.

So this was the third part.  In the next part, we will give a complete overview of all the Scrum templates. 

Your TFS Scrummasters

Bart Wullems and Sven Cipido

The last 2 days I followed a Scrum Master training to become a certified Scrum Master given by Joseph Pelrine.  As I'm already using scrum for almost 3 years now, it was nice to have some course around it.  I must say even after 3 years, you still learn new things.  I will just give some interresting points about this course, but the whole 2 days were interresting (and yes Joseph I don't want to give too much info, just make people warm for your course).

1. Joseph's rules about Scrum (and I totally agree with them)
   • We don't make mistakes, we learn
   • If you don't have fun, there's something wrong (I can say we had some great fun during this course)
2. Scrum is a system of 3's
   • 3 Roles
   • 3 types of Meetings
   • 3 types of documents
3. "Turn up the heat" of your team so they come out of their daily routine
4. Although in my previous blogpost about Scrum (written in 2005) I have talked that a good sprint length would be 30 days, but it's better to find a spint length where have a good feeling.  And don't talk ind ays or months but in weeks.
5. Also I wrote down that the meetings should be taken 4 hours max, I must say let's downsized it till 90 minutes with a max of 2 hours.  BTW Joseph will give you some more great tips.
6. Very interresting was the part about Multiple Teams/Multiple Projects
7. We got some great tips for doing the Daily Scrum Meeting
8. And last but not least : You can setup several rules for your team and for the Product Owner

I learned a lot of new features, and I hope I can follow som other courses from Joseph (Particuly I'm interrested in the "Coaching of self organising teams" as I see this as a follow up of the Scum course).

So if you are interrested in this and want to follow a course just contact Joseph, and he will tell you more.

BTW : The chickens and pigs are still alive in Scrum .

BTW 2 : I had great time of fun with Joseph and Maddalena the first evening in Leuven and the second evening before I drove them back to the airport.  Txs you two.

As I'm posting with my colleague Bart a serie of 6 posts about Scrum templates in TFS2005, we also will cover TFS2008.

But just too make you warm you can download the new beta of Scrum for Team System v2 from Conchango.

They had a lot of new improvements.  Read more here.

Remark: if you upgrade form beta 1, read this forum post how to do it. (You must login to read it).

In this next post, we focus on the installation of the 3 Team Foundation Scrum templates we're gonna test. If you want to know more about Scrum or TFS, read our first blogpost here. This article will also be crosspost on the Ordina Blog.

Installation of the templates

Microsoft eScrum

1. Download the necessary files
2. Before you start installing the MSI, make sure you have following programs installed:
   • ASP 2.0 Ajax Extensions 1.0
   • Microsoft Anti-Cross Site Scripting Library 1.5 installed
3. Install the MSI.
4. After the installation Read The F***ing Manual, because from here you have to do a lot of configuration work like security, IIS, and so on...
   • Our experience :
     Bad luck first... our installation failed. After some searching, we found that removing the Sharepoint templates and reinstalling them back by hand solved the problem. After this step the installation succeeded.
   • Remark: Microsoft has taken care of the several complains and bugs during the installation of the first eScrum version. Meanwhile they have released a new version (still called version 1.0) with a much better installation experience.
5. Create a project in TFS based on the installed eScrum template.
6. After the creation of an eScrum project, you still need to add the project to a config file in the directory where the eScrum website is installed. If you don’t do this, the project will not be available in the website.
7. The pain is over. We're done!

VSTS Scrum Process Template

1. Download the process template here.
2. Unzip the downloaded file
3. Read the readme.txt file! You'll regret it when you skip this step
4. Next install the SharePoint template(more info in the readme.txt 
5. Upload the process template to the team foundation server (If you have no idea how to start uploading templates, here is the answer.
6. Done!

Conchango Scrum for Team System

1. Surf to the Conchango website and  register to start downloading the necessary files.
2. After the short registration process, download the MSI files.
3. Run the MSI's and follow the installation instructions. There is one MSI for the template and one for the administration utilities.
4. The project guidance can be viewed online, but can also downloaded separately and added to TFS. Allthough we used version 1 of this guidance, a second edition is available.
5. Don’t forgot to install the reports through the Administration module “Report installer”. At first we did not do that. The reports were visible in Team Explorer, but we've got an error when calling one. After reinstalling the reports throught the Report Installer, the problem was solved.
6. After the installation, you'll find following administration utilities at your service:
   • Migration Utility: Migrate your current TFS Scrum projects to the newer version
   • Report Installer: Choose which reports you want to install additionally in your project.
   • Warehouse Manager: One of the problems in TFS is that changes to workitems are not directly visible in reports. The reason for this is that the datawarehouse only runs one time each hour(by default) to collect all info. This could be a problem because a lot of developers wait till just before the Daily Scrum Meeting to update their information. During the meeting this information isn’t up to date and the burndown chart doesn’t match the current situation.With the warehouse manager it is possible to start the update directly or even to regenerate the warehouse from scratch.You can achieve the same functionality with the command line tools of TFS, but this manager gives you a much nicer experience.
     • Remark: Depending on the number of projects and the amount of date, rebuilding  the warehouse could be a time consuming task. Keep that in mind before you start clicking the rebuild button.
   • Teams & Enviroments: Manage the environments and teams in your TFS projects.

Conclusion about the installation process

As a conclusion we could say that installing the different templates wasn't a big problem. One precaution must be made. Always start by reading the available documentation, this will save you a lot of time(I know that IT guys normally don't read manuals, but please make an exception. You will be thankful).

So this was the second part.  In the next part, we will talk about our usage experiences with the different templates. 

Your TFS Scrummasters

Bart Wullems and Sven Cipido

In our company lately I'm busy with TFS and Scrum.  Also my colleague Bart is busy with these items.  So we decided to joined together for a serie of posts about the different Scrum templates in TFS. This article will also be crosspost on the Ordina blog. So let's start with the first post of this serie.

What is Scrum?

A definition by ControlChaos.com:

Scrum is an iterative, incremental process for developing any product or managing any work. It produces a potentially shippable set of functionality at the end of every iteration. It's attributes are: 

• Scrum is an agile process to manage and control development work. 
• Scrum is a wrapper for existing engineering practices. 
• Scrum is a team-based approach to iteratively, incrementally develop systems and products when requirements are rapidly changing 
• Scrum is a process that controls the chaos of conflicting interests and needs. 
• Scrum is a way to improve communications and maximize co-operation. 
• Scrum is a way to detect and cause the removal of anything that gets in the way of developing and delivering products. 
• Scrum is a way to maximize productivity. 
• Scrum is scalable from single projects to entire organizations. Scrum has controlled and organized development and implementation for multiple interrelated products and projects with over a thousand developers and implementers. 
• Scrum is a way for everyone to feel good about their job, their contributions, and that they have done the very best they possibly could.

Scrum naturally focuses an entire organization on building successful products. Without major changes -often within thirty days - teams are building useful, demonstrable product functionality. Scrum can be implemented at the beginning of a project or in the middle of a project or product development effort that is in trouble.

Scrum is a set of interrelated practices and rules that optimize the development environment, reduce organizational overhead, and closely synchronize market requirements with iterative prototyes. Based in modern process control theory, Scrum causes the best possible software to be constructed given the available resources, acceptable quality, and required release dates. Useful product functionality is delivered every thirty days as requirements, architecture, and design emerge, even when using unstable technologies.

What is TFS?

Visual Studio Team System Team Foundation Server is an integrated collaboration server for Visual Studio Team System. It combines team portal, version control, work item tracking, build management, process guidance, and business intelligence into a unified server. It allows everyone on the team to collaborate more effectively and deliver better quality software.

Scope.

This document describes the advantages/disadvantages between several Scrum templates that can be used on VSTS 2005.

Used Scrum templates.

Template	Version	Download link
eScrum (Microsoft)	1.0	http://www.microsoft.com/downloads/details.aspx?FamilyID=55A4BDE6-10A7-4C41-9938-F388C1ED15E9&displaylang=en
Codeplex Scrum Process	1.0	www.codeplex.com/vstsscrum/
Conchango Scrum For Team System	1.2	http://www.scrumforteamsystem.com/en/default.aspx Remark : You have to register before you can download.

So this was the first part.  In the next part, we will talk about the installation process of the different templates.  So stay tuned.

Your TFS Scrummasters

Bart Wullems and Sven Cipido

If you are using Scrum as methodology this can be interesting.  Microsoft has released its first version of eScrum. 

What’s eScrum?
eScrum is a web based tool for Scrum projects on the Microsoft Visual Studio Team Foundation Platform.  Read more at Mark Brown’s blog.

You can download the template here: http://www.microsoft.com/downloads/details.aspx?FamilyID=55A4BDE6-10A7-4C41-9938-F388C1ED15E9&displaylang=en

Agile Development

The last years one of the new buzzwords is Agile development.  It's a new formal software development methodology.  Several methodologies to use Agile are:

1. Scrum: Agile Project Management.
2. eXtreme Programming
3. Crystal
4. Adaptive Software Development
5. Feature Driven Development

We won't talk about agile itself, but about one of the agile methods called Scrum.  But before doing this we have a little note: Agile creates a mentality shift.  This will be explained when we talk about Scrum.

Why Scrum?  The project that I'm doing at this moment for a customer is a pilot for Scrum within this customer.  We have a good feeling with Scrum and our project is going in high-speed.

Now let's talk a bit about Scrum.

Scrum principles:

1. As soon as there is a problem, identify it.  This is important, because the faster a problem is identified, the easier it will be to pick up.  Problems can be logged on the "Impediments" tab in the Sprint backlog (More of this later).
2. Analysts know how to analyse and the developers know how to develop.   So just leave them alone and let them do their work.  In case you need something to ask, go to the Scrum master (see Scrum roles).  Important is that the analysts also need to need to have basic to medium knowledge of programming language and the developers need to know how to analyze or read an analysis.  Actually, you don't speak anymore of analysts or developers but of a team that works together.
3. Make iterations that are not too short or too long.  A theoretical/practical good iteration is 30 days.  Keep the length for every sprint (see later for an explication) the same.  The advantage is that everyone (the team and the customer) has the feeling at the end of a sprint that they end a real product. 
4. The team must be self-organising
5. Try to work on one theme each sprint
6. There must be one team room, not 4 rooms for all team members.  Communication is very important

Scrum activities:

1. Sprint planning: This is the first day of an iteration.  It takes 4 hours maximum.  The customer sits together with the team, shows the product backlog (see later for an explication) and explains it.  Also he gives his priorities to the items on the product backlog.  Then the team discusses everything and makes an agreement on what they will deliver within this iteration.  Best is that each sprint is centered around one theme (e.g. Database Application, Financial Services,...)
2. Sprint planning part 2: In the afternoon, the team sits together to discuss everything and to expand the product backlog items in smaller tasks of maximum 16 hours for each task.  The manager (product owner) doesn't assign tasks to individuals, doesn't make decisions for the team.
   
   
   
3. Sprint itself.  During this period the team does the analysis, the programming, testing and documentation.  At the end the team will deliver a Potentially Production Ready Product.
4. Daily Scrum: This daily meeting is held in the beginning of the day.  It takes only 15 minutes during which the team tells what they have done the previous day, are there problems and what are they going to do during that day. Cannot be used to solve problems.  The chickens and pigs (The pigs are the team themselfs, the chickes are people who are just interested in what's going on) are invited.  This will help to avoid unnecessary meetings.  Only the pigs can talk.  The advantage is that the team sees the whole picture every day and it creates a pressure to do what you have said you will do.  It can't be replaced by emailed status reports.
5. Sprint Review: This is the last day of the iteration.  The preparation time needed by the team can be maximum 2 hours (the day before).  In this meeting, the team will demonstrate the new functionality to the customer (and all the people who are interested).  Typically it takes the form of a demo of new features or underlying architecture.
6. Sprint retrospective: This meeting is held only by the team leaded by the scrum master (see later for an explication).  During this meeting they will make a review of what happened during the last sprint.  What was good, what could be done better,...?
7. Sprint Stabilization: This is a short sprint around 2 weeks to stabilize the product and implement it in test or production.
   
   
   
8. Sprint Refactoring: Almost the same as the Stabilization Sprint.  Only that this sprint is needed to refactor the code.

Scrum practices:

1. During the project identify the Impediments and remove them as soon as possible.  These Impediments are written down in the sprint backlog.
2. Identify the Product backlog
3. Define the Sprint backlog
4. Be sure that no one can disturb the team.  The Scrum master must ensure this
5. Product is designed, coded and tested during a sprint.
6. No Changes are allowed to the product backlog during a sprint.

Scrum products:

1. Product backlog: Is created by the customer (product owner).  This backlog defines everything to cover his needs.  Every item has a priority.  This product backlog is explained on the Sprint planning meeting.  The team itself can also add tasks during a sprint for the next sprints, when they have the need that this must be written down to be sure that will be done (impediments).  There are two kinds of product backlogs : We can have a functional or a technical product backlog.

2. Sprint backlog: the scrum master defines this after the sprint-planning meeting.  It contains all the 16-hour tasks divided in sub categories.  Also the hours a team member can work during this sprint is written down.  Further included is also the team burn down and the individual burn down graphic is added.  With burn down can be explained as a graph wich tells us how fast or how slow we go on a all our tasks.  A good thing is to use a team member anonymous on which all task are defined.  When a team member takes a task for him he changes the anonymous user to his name.  This way you don't have to delegate the task before to the team members and everyone can decide every moment what he wants to do (Of course, at regular times the sprint backlog needs to be reviewed to ensure that all tasks are performed before the end of the sprint.).  The sprintbacklog can only updated by the team. 

Scrum roles:

1. Scrum master: The facilitator of the project.  He's one of the succes factors for the project.  He must work together and support the next 2 roles.  Typically this role is filled in by a Project manager or Team leader.  He is also responsible for enacting Scrum values and practices.  His major job is to remove the impediments.
2. Product owner: he is the customer.  Acts like one voice (even if it's not one voice).  Typically this is a product manager, someone from marketing or similar.  The major responsibility is that he knows what needs to be build and in what sequence this should be done.
3. Scrum team: the team itself.  Typically the size is about 5 - 10 people.  Must be cross-functional and those people must work together.  Members must be available full-time for each sprint.  Some exceptions to this full-time availability are possible, e.g. System Admin,...).  Team members can only be added or leave the team between Sprints.  The team is self-organizing, so in principle no project leader (like in a standard project development) is in role, but it could (although this job can be done by the scrum master). 

Burn Down:

You must be aware that the scrum team has a good burn down.

•  No work: 
  
  
  
• Work but not fast enough 
  
  
  
• Work but too fast 
  
  

What covers Scrum:

As you can see, every meeting type has it's own coverage.  The only link that is missing is between the Product Level and the Development Level.  But this is solved by the needs of tasks.

Conclusion:

Comparing tradition approaches versus agile we could say:

Traditional:

Traditional methodologists are a bunch of process dependent stick-in-the-muds who’d rather produce flawless documentation than a working system that meets business needs.

Agile:

Lightweight, er, “Agile” methodologists are a bunch of glorified hackers who are going to be in for a heck of a surprise when they try to scale up their “toys” into enterprise-level software.

1. If you want to use agile, try to brew your own cocktail:
   Inception: Develop in pairs (Analyst architect + user) and remember your backlog.
2. Elaboration: Develop in pairs (analyst/architect + lead developer) and continue to make the use cases
3. Construction: Multiple XP teams developing different parts of the architecture.  Scrum Master for each team – with Project Manager over all and cross-team pairing for interface and infrastructure issues
4. Transition: Integration of different parts of the architecture, but also pairing for fixing bugs and integration
5. Start with XP: Use 1-month iterations
6. Add other Scrum practices: Scrum master a protection/insulation of the team
7. Add use cases from RUP: Architects pairs with marketing staff.  Marketing sells use cases to the world, while architects converts those use cases to the developers.

Scrum in a few words:

1. Is an agile, lightweight process
2. Can manage and control software and product development
3. Uses iterative, incremental practices
4. Has a simple implementation
5. Increases productivity
6. Reduces time to benefits
7. Embraces adaptive, empirical systems development
8. Is not restricted to software development projects

Still remember:

1. There's no ideal development process
2. Always tailor your process and methodology based on following requirements:

1. Scale of project (small team, > 100 developers,...)
2. Type of project (real-time, medical,...)
3. Experience and type of resources
4. ...

Scrum and Visual Studio Team System 2005:

In Team System Microsoft has added the templates to use agile methodologies.  It's Microsoft's own definition.  A part of it is likely Scrum, but you have to recreate your own templates.  Or you can go to http://www.conchango.com/Web/Public/Content/NewsRoom/PressReleaseDetails.aspx?PageID=270.  It's still in development

My experience:

When people are leaving on holiday during a sprint, especially in the beginning or at the end, the Scrum Community gives us a  good solution :

When folks can't attend sprint planning, reviews, or retrospectives, I suggest they provide proxies
that can fully represent their interests. This keeps the rhythm going and has the added benefit of
cross-training (pairing of sorts for the proxies).

We are going to try this principle during the sprint of December.

Another thing we discover is that at the end, sometimes people don't know in detail what 's done by the other team members.  We have proposed a few solutions to the scrum master about this.

1. We do intern sprint reviews in between (max 2).
2. Every monday morning we will create the tasks for that week.

A scrum team is minimum 5 people and maximum 9 people.  Our experience is that 7 team members is the maximum in one team.  If you have more than 7 people, you must divide them in more teams.  For each team there will be a kind of Scrum master who discusses the overall picture with the other team scrum masters and the scrum master.

The anonymous teammember only is not good enough.  It could happens that some important tasks are not picked up by someone.  So we decide that the main blocks are not assigned to the user anonymous, but to a teammember.  This doesn't mean that he has to do this task, but he has to follow up that the tasks defined in this main block are getting done at the end of the sprint.

And last but not least (at this moment).  Several team members still think that the sprint backlog is a kind of time registration tool.  This is not the case.  Every morning you have to fill in the Sprint backlog with the time still needed for the tasks you picked up.  This means that when for a task of 20 hours you have worked 8 hours, you still can fill in 16 hours to go.

Links :

http://www.controlchaos.com
http://www.scrumalliance.org
Scum user stories : http://www.mountaingoatsoftware.com
Scrum Community : http://groups.yahoo.com/group/scrumdevelopment/
Short description by William Wake : http://xp123.com/xplor/xp0507/Scrum-dev.pdf
Howard van Rooijen : http://blogs.conchango.com/howardvanrooijen/archive/category/32.aspx
Conventional Software Testing on a Scrum Team : http://osnews.com/comment.php?news_id=12067
Scrum in Project 2003 : http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_pj2003_ta/html/OfficePJScrumToolSolStarter.asp
Scrum Solution Starter : http://www.microsoft.com/downloads/details.aspx?FamilyId=81DAAB54-6701-4FBC-B3D0-7F261383F371&displaylang=en

Thanks to Diederik Krols, My Scrum  master at this moment for extra information.

Update :

Danube Technologies has an automation tool for Scrum.  Although still in trial period, you can already download it and use it.  You just have to fill a few questions about the usage of Scrum.  Click here for more info.