Integration with Scrum for Team system
-
jueves, 15 de septiembre de 2011 20:01
Hi,
We are customizing a mix of Agile and CC approach. Hence, we have applied the TFS-Pserver feature pack.
I am having problems with the intregration. I want TFS to send Product Backlog item, and Sprint Task.
When marking a Product Back Log item as "Send to Project Server = Yes"
I get the following error:
TF20012: Assigned To can not be empty.
thanks,
Santiago
Todas las respuestas
-
jueves, 15 de septiembre de 2011 20:46
We are venturing down the same path, but we are starting out with the SCRUM 1.0 Process Template provided by Microsoft (http://visualstudiogallery.msdn.microsoft.com/59ac03e3-df99-4776-be39-1917cbfc5d8e/).
So far, we have added the Original Estimate Field to the PBI, Task and Bug Work Item Templates so that we can enter Estimates in the Work items and have them show up in the Baseline Work filed in Project Server.
We have also modified the Work Item templates for these Work Item types so that the Project Server tab shows up where we want it (see thread: http://social.msdn.microsoft.com/Forums/en-US/tfsprojectsrvint/thread/20dc78b7-5964-415f-b1ec-8e30573284e8/).
Everything is working great so far, but we haven't attempted synchronizing the Sprint Work Item Type yet.
We do want to sync the Sprint types for scheduling purposes so we will be attempting that next. I know that it doesn't include the Assigned To field so we might see the same error as you. If so, I will let you know (and also the 'fix' if there is one).
string fakeEmail="jim.duncan@sharesquared.spam.com"; string realEmail=fakeEmail.Replace(".spam","") -
jueves, 15 de septiembre de 2011 22:08
We were able to get the Sprint Work Item Type to successfully sync with Project Server. In order to do so, we had to edit the Layout form for the Sprint Work Item to include the Assigned To and Title fields as these are required by Project Server.
Changes we made to the Sprint Work item Type:
- Added a REQUIRED rule to the System.Title field
- Added a ALLOWEXISTINGVALUE and VALIDUSER rule to the System.AssignedTo field
- Added the Title field to the Work Item Form (above Iteration)
- Added the Assigned To field to the Work Item Form (but labled it "Development Lead")
Here's what the modified form now looks like:
The only problem we see so far is that the Start and Finish Dates are set so that the value specified in Project Server wins. this doesn't really work for us since we want our SCRUM Master to set the dates for a Sprint and NOT our Project Manager. The way things are now, if we set Start and Finish on the Sprint Work Item it is overwritten with whatever dates are specified in Project.
We're looking into removing the onConflict="PSWins" from the mapping for these fields but that might introduce more issues than it's worth and we may just end up scheduling Sprints in Project instead.
More to come...
string fakeEmail="jim.duncan@sharesquared.spam.com"; string realEmail=fakeEmail.Replace(".spam","")- Propuesto como respuesta Federico Kolliker Frers - MS jueves, 22 de septiembre de 2011 20:52
-
martes, 20 de septiembre de 2011 19:17
thanks for your answer.
Without any customization, we´ve worked arround my initial problem by defining the direction of the Sync.
If PBI are first created by Pserver, there doesn´t seem to be any Issue.
- Propuesto como respuesta Federico Kolliker Frers - MS jueves, 22 de septiembre de 2011 20:52
- Marcado como respuesta Mata jueves, 22 de septiembre de 2011 22:27

