TFS: Scary


First time I have seen something like that! ok maybe no space left on TMS, but don’t put that in the Description, come on Smile.




Task estimation for web-development made easy

A lot of web-developers have no idea how to estimate an assigned task in TFS, this is a Quick guide what to think about, when you have to ESTIMATE a task for your projects…

  1. Read carefully the task description and linked scenario
    1. Ask more details if you need, often it happens
  2. Check the which code area are affected
    1. Check for similar web control/code doing the same
  3. Check if you need to new/update storeproc for the data layer
  4. Check if you need to update the installer solution to include new elwmnts
  5. Plan what you need having a global view of the solution
  6. Figure out the Coding effort based on what you need to implement at this point
    1. New code to be added
    2. Refactoring any affected code
    3. Trying to keep all consistent across the project
      1. Code styles
      2. Put code in the BL/ Ux properly
      3. Contingency on undocumented code
  7. Testing in different browser

And don’t forget that software development is “A cooperative game of communication and invention” so quite often, the only way we know everything we need to do is to actually do it.

From Requirement to Coding made easy

I was thinking about how to start a simple workflow to deliver … requirements, in a company that does not do it properly, this it’s a nice try, please send me your idea, but of course it’s very basic 😎

1. The scenario [small one] is kept in a SharePoint doc

2. People involved [Business Requirement analyst, Coder, QA ,Prj Mng] will subscribe email change alert

3. Each change and discussion will be kept in the SharePoint doc by the Business Requirement analyst [the only responsible for maintaining the doc – one single responsibility rule]

@ each email alert coming from SharePoint [that means the Requirements are changed]

  • The Coder will create a new task on tfs related to the Scenario changes [small one]
  • The QA will raise bugs [if any] putting as link the tfs task
  • The Prj Mng will have a review at free-bug completed task

Current Implementation

Based on my experience in a lot of companies what happens 😦

  • A scenario is wrote [big one] and not maintained
  • No small / testable / etc.. tasks are created
  • QA rises changes directly to me, instead of going through BA to give him the possibility to consolidate any change
  • At the end QA and BA spend time on talking on issue that have been already discussed and implemented
  • There is no changes history to the Scenario and the current implementation so for QA is hard to understand what is a bug and what is just not a requirement
  • etc

MSF Agile v5.0 vs Visual Studio 2010 Scrum 1.0 and intro

As I am think a common agile approach to work is very important to reach objectives and to deliver results [without stress] I  was looking to the Visual Studio 2010 Scrum 1.0, for a brief note on difference with the MSF Agile v5.0 read

Here the highlighted version


I uploaded to Vimeo 2 intro of using the

Scrum Process Template for TFS

found on