Wednesday, February 28, 2018 / CSharp
"Scrum is an Agile framework for completing complex projects." That definition is generic enough to mean almost anything or nothing and in practice that is often how it turns out.
This blog is to explain our starting point with the VSTS templates.
The Scrum and Agile templates have a bunch of attributes. Do we need them to start our project? No.
Will we need them later? Maybe.
The following is how we modify the templates.
Go to your VSTS site.
Click on the Visual Studio Icon in top left of the page to get to the root of the site if you are not there already.
Select the gear icon from the menu then select
... menu at the right of the Scrum template select
Create inherited process:
Give it a name:
Click on the new process.
We hide everything to do with estimates. In a future post we will build our
Definition of Ready, but we attempt to make
User Stories/Product Backlog Items small. We consider every story the same. We will use our history over time to determine how many stories we can do in a sprint, thus allowing for planning and decision making.
For thoughts on #NoEstimates or just google it.
Definition of Ready is a higher priority. So to start a greenfield project I recommend you don't bother estimating and spend more time focusing on proper user stories, automation and coding.
The resulting layouts are:
Commited states and add a
Draft: I am just creating this Item. Everyone else can ignore it until I am done. At which time I will move it to
Submitted: The original author of the item believes the item meets the
Definition of Ready, and is requesting the item to be triaged. If the Product Owner agrees that the item is ready they will move it to the
Ready state if not they will move it back to the
Draft state with comments as to why it is not ready.
Ready: The Item meats the
Definition of Ready and can now be prioritized and put into a Sprint.
There is a nice extension component that adds a checklist control. Checklists are simple control mechanisms that produce great return for the effort. I suggest using this for the
Definition of Done and any other "sub tasks" one needs.
So there you go quick minimal Scrum. Build your own so your next project is ready to go.