If you follow the ”MSF for Agile Software Development Process Guidance”, you will find one point that says this:< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
Project Manager->Plan an Iteration->Estimate Scenario->2 Create Implementation Estimates
”Work with the developers to do a rough order of magnitude estimate of the time needed to implement each scenario. All estimates should be made in ideal person days.”
So I thought you should specify this in the field “Rough Order of Magnitude”. I instructed the developers to go through the scenario list (from Visual Studio) and estimate the time on some scenarios.
Now, as a Project Manager, you would like to se these estimations in MS Project so I thought that this value would be “refreshed” into MS Project and entered in the “Duration” filed, but it wasn’t.
So I thought I could do this manually instead. I tried to add the column “Rough Order of Magnitude” to MS Project to make this manual work a bit easier, but I’m unable to add that column to MS Project. I can add a lot of other columns, but not this one.
To sum it all up:
1. Shouldn’t the “Rough Order of Magnitude” field in some way affect the duration field in MS Project
2. Is it not possible to add the field “Rough Order of Magnitude” filed as a column in MS Project
Regards,
< xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" />
"Rough Order of Magnitude" and Microsoft Project 2003
YulinS
Thanks for the report. Thanks to you, we have fixed this in RTM and the upcoming refresh of the MSF for Agile Software Development process template as well. This new process template will be available early next week at http://www.microsoft.com/msf - you may wish to upload it. As for Rough Order of Magnitude, many of our pilot projects found making this estimate too hard. We have gone to a simpler complexity scale instead. I'd like you thoughts on this.
Cheers,
Randy
MSF
aurora123
If you're looking to change the mapping between MS Project and Team System, here is some helpful documentation:
When you connect a project plan to Team Foundation, you may need to define how the work item fields are mapped to fields in Microsoft Project. To change how the fields are mapped, you must edit XML files.
The mapping between work item fields and Microsoft Project is specific to a team project. You can change the field mapping at any point in the project.
If you change a column name in Microsoft Project, the column will be renamed when you refresh from Team Foundation. If you want to change a column name permanently, use the < XML:NAMESPACE PREFIX = MSHelp NS = "http://msdn.microsoft.com/mshelp" />TFSFieldMapping utility.
To view how work item fields are mapped to Microsoft Project
On the Team menu, click View Column Mappings.
The mapping between work item fields and Microsoft Project is specific to a team project. You can change the field mapping at any point in the project.
Review how work item fields are mapped to Microsoft Project and determine if you need to make changes. If you decide to make changes, see the following procedure, To change how work item fields are mapped to Microsoft Project.
To change how work item fields are mapped to Microsoft Project
Download the mapping file as follows:
Open a command prompt window.
Go to the folder where Visual Studio is installed (for example, drive:\Program Files\Microsoft Visual Studio 8), and in that folder, go to \Common 7\IDE. The TFSFieldMapping.exe utility program is in this folder.
Download the mapping file using the TFSFieldMapping.exe utility by typing the following at the command prompt:
TFSFieldMapping download http://Team_Foundation_Server team_project C:\MappingFile.xml
Where:
http://Team_Foundation_Server is the URL of your server.
team_project is the name of your team project.
C:\MappingFile.xml is the file name and location to which the mapping file will be downloaded.
Edit the mapping file as follows:
Open the mapping file you downloaded (for example, C:\MappingFile.xml) in an XML editor.
Add new mappings or edit existing mappings in the following format:
For example:
Where:
Microsoft.VSTS.Common.Priority is an existing field in the MSF for Agile Software Development process.
pjTaskWBS is the Microsoft Project field WBS for Tasks
For a full list of all the Microsoft Project field values for the ProjectField attribute, see Field Mappings in Microsoft Project.
If you want a field to be published to Team Foundation Server, but not refreshed from Team Foundation Server, add the
PublishOnlyattribute to the mapping section for that field and set the attribute to True. The default value is False, where a field is both published and refreshed from Team Foundation Server. This attribute can be used to allow team members to see a field value but not be able to change it in Team Foundation.Save the mapping file.
Upload the mapping file as follows:
Open a command prompt window.
Go to the folder where Visual Studio is installed (for example, drive:\Program Files\Microsoft Visual Studio 8), and in that folder, go to \Common 7\IDE. The TFSFieldMapping.exe utility program is in this folder.
Upload the mapping file using the TFSFieldMapping.exe utility by typing the following at the command prompt:
TFSFieldMapping upload http://Team_Foundation_Server team_project C:\MappingFile.xml
Where:
http://Team_Foundation_Server is the URL of your server.
team_project is the name of your team project.
C:\MappingFile.xml is the file name and location from which the mapping file will be uploaded.