|
-
Jul 2nd, 2009, 02:08 AM
#1
SCRUM Methodology and Team Foundation Server
Hello,
As a Development Team we are away to start using Team Foundation Server and the SCRUM Methodology. Specifically, we are going to be using the Team Foundation Server Templates from here:
http://scrumforteamsystem.com/en/default.aspx
- Has anyone used this?
- Thoughts/Impressions?
- Things to look out for?
- Best Practices?
Any feedback welcome.
Thanks!
Gary
-
Jul 31st, 2009, 03:40 PM
#2
Re: SCRUM Methodology and Team Foundation Server
Hey,
Nobody using this?!?!
Gary
-
Jul 31st, 2009, 04:37 PM
#3
Re: SCRUM Methodology and Team Foundation Server
- Has anyone used this?
** Not specifically.
- Thoughts/Impressions?
** There's no one do-it-all system out there.
- Things to look out for?
** Again. same as above. Don't be afraid to customize.
- Best Practices?
** Keep what works, dump what doesn't. Evolve the process as you go.
-tg
-
Jul 31st, 2009, 04:46 PM
#4
Re: SCRUM Methodology and Team Foundation Server
Hey,
Thanks for responding!!
So far, we are actually really liking the SCRUM Methodology. We have just finished our first sprint, and have demoed to the client.
The whole concept is a bit of a step change, and has taken a bit of getting used to, but on the whole, really liking it.
Also loving TFS. That has taken a bit of setting up, especially surrounding Code Analysis, and StyleCop, and then getting the AutoBuild working, but on the whole, it really seems to be paying off as well.
Gary
-
Aug 1st, 2009, 04:30 PM
#5
Re: SCRUM Methodology and Team Foundation Server
Has anyone used this?
- Thoughts/Impressions?
- Things to look out for?
- Best Practices?
We've been using it for the past 2 years.
I like it, it covers a lot of aspects of scrums from start to finish, things to keep everyone happy - business priority, bugs associated with work items/tasks, attaching files, web-based scrum dashboard with DHTML post-it notes, export-reimport from Excel, email alerts for bugs.
Things to look out for + best practices: it's tempting to get really lazy and not fill out a lot of the details. Many developers will break the task down with a simple title like "Do the code" and nothing else inside it. It's a good idea to make the check in comments mandatory as well as assigning to a work item mandatory, again, developers are a lazy bunch
Watch out how you set up the TFS server - the transaction log grows at an astronomical rate.
To get a good idea of your velocity, you need to remind everyone to update their scrum dashboard. It's easy to keep forgetting when you're very busy.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|