I see these main areas where Project Server 2010 would be of benefit:
If you’re already using Timesheets, you can piggyback on the significant effort you put into getting there. If you don’t, you can manually update Actual Work directly in your Project Plans.
Based on my limited experience with Scrum, I’d expect to do some configuration work on the Project Server side, and learn some new habits on the Project Professional side.
Project Server Configuration
Define custom Task fields for:
Develop Excel pivot tables in the BI center for
Modify the Timesheet view to include the Deliverable and Sprint fields (read-only).
To define a Sprint:
You can develop reports specific to managing a Scrum by selecting only those project tasks that have the Scrum Task flag set to “Yes”.
You will need to develop burn-down reporting that will show:
After each Sprint, refer to the burn rate reports and modify the resource allocations in the remaining Backlog tasks, to refine the predicted completion date for the Scrum.
This is the approach I’d take, but I’m hoping there are folks out there who are currently using Project Professional (and maybe Project Sever) to manage a Scrum effort.
Let’s see if we can correct / refine / expand the above.
A note about moving Tasks in a Project Plan.
In Project Server 2010, when a Timesheet is created, it links each timesheet line to a Project Plan Task using the Task’s UID. If you move that Task’s location in the Project Plan by dragging it, you’ll be OK. If you “move” that Task using Cut and Paste, you’ll delete the old Task and create a new Task, with a new UID, breaking the link to the Timesheet!
As long as no Actual Work has been done, that’s not an issue; once Actual Work has been logged, you can be in trouble. To be safe, avoid using Cut and Paste with Tasks in Project Professional.