Create a Professional Scrum process

Visual Studio Team Services’ customization capabilities are to a point now where I can write this blog post … as a rebuttal to any earlier post of my own. As you may know, the Scrum Guideย has beenย updatedย more frequently than Microsoft’sย Scrum processย (template)ย which, when launched, was meant to be an exact implementation. It falls uponย the community (me and you) to update the Scrum process ourselves. Maybe that was Microsoft’s plan all along. ๐Ÿ™‚

Following the guidance here, I’ve documented my journey to create a Professional Scrum process.

First, I created an inherited process based on the Scrum template …

ProScrumProcess1

I named this inherited process “Professional Scrum” …

ProScrumProcess2

After setting Professional Scrum as the default process, I began customizing it. I started by disabling the Bug work item type, because the Product Backlog Itemย WIT works just fine) …

ProScrumProcess3

I customized the Product Backlog Item layout by hiding the Priorityย and Value Type fields …

ProScrumProcess4

Note:ย Ideally, I would have liked to remove these fields altogether, but that isnโ€™t allowed today.

Next, I added two new states: Readyย (which maps to the Proposed category) andย Forecastedย (which maps to the In Progressย category) …

ReadyState

I disabled the Approvedย and Committed states, replacing them with Readyย and Forecasted respectively …

States

Note: I could have created a similar state workflow for Epic and Feature, but didn’t. You could.

I made similar changes to the Epicย and Featureย work item type, hiding Target Date, Priority, Time Criticality, and Value Area fields …

ProScrumProcess7

I also hid the Priority and Activity fields from the Taskย WIT andย Priorityย from the Impediment WIT. I then went to Backlog Levels and renamed the Backlog items level to Stories

ProScrumProcess8

Note:ย Although epics, features, and stories are all considered PBIs in Scrum, most teams I coach prefer to call the lowest level (“sprintable”) backlog items as stories. Ideally, all backlog levels would just use the Product Backlog Item WIT and then we could ditch or ignore Epic and Feature WITs altogether.

I then created a new team project based on the Professional Scrum template and beheld the awesomeness, such as “Stories” instead of “Backlog Items” and the Bug WIT being unavailable …

ProScrumProcess9

“Forecasted” instead of “Committed” and a minimal Details section …

ProScrumProcess10

So, let’s revisit my checklist from my earlier postย and see what’s possible now …

ProScrumProcess11

Scrum on!

 


Comments

Leave a Reply