-
Notifications
You must be signed in to change notification settings - Fork 174
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated rule - fleshed it out a little, made it more approachable
- Loading branch information
1 parent
ba8e00c
commit 3b3bcdd
Showing
1 changed file
with
20 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,25 +1,39 @@ | ||
| --- | ||
| type: rule | ||
| title: Do you use the Scrum template when creating a project in Azure DevOps? | ||
| title: Do you use the Scrum template with Azure DevOps? | ||
| uri: use-devops-scrum-template | ||
| authors: | ||
| - title: Manu Gulati | ||
| url: https://www.ssw.com.au/people/manu-gulati/ | ||
| - title: Gordon Beeming | ||
| url: https://www.ssw.com.au/people/gordon-beeming/ | ||
| - title: Matt Wicks | ||
| url: https://www.ssw.com.au/people/matt-wicks/ | ||
| created: 2023-10-05T05:38:23.907Z | ||
| guid: 8fefac19-a746-4ce9-903b-e18b52ce1cf2 | ||
| --- | ||
| When you create a new project in Azure DevOps you have the option to select a template. You should always select the Scrum template. The 2 figures below show how to do so. This has a few benefits. | ||
| When initiating a new project in Azure DevOps, selecting the right template is crucial as it sets the groundwork for project management and collaboration. The Scrum template is a recommended choice due to its adherence to widely recognized Scrum terminology and practices. This rule guides you on how to select the Scrum template and elaborates on the benefits of doing so. | ||
|
|
||
| * Work item types adhere to the Scrum terminology | ||
| * Work item states adhere to the Scrum terminology | ||
| * Consistency across SSW | ||
| <!--endintro--> | ||
|
|
||
| 1. Go to Azure DevOps | New Project. | ||
| 1, Fill in the Name, Description, Visibility. | ||
| 1. Click Work item process | Scrum. | ||
| 1. Click Create. | ||
|
|
||
| ::: img-small | ||
|  | ||
| ::: | ||
|
|
||
| ::: img-small | ||
|  | ||
| ::: | ||
| ::: | ||
|
|
||
| Using the Scrum template has its fair share of cool perks: | ||
|
|
||
| **Terminilogy:** The work item types and states are all in Scrum-speak, which helps everyone on the team get on the same page quickly. | ||
| **Consistency:** It keeps things uniform across projects, so jumping in and out or teaming up is a breeze. | ||
|
|
||
| Azure DevOps does have other templates like Agile and CMMI, but the Scrum template has a special spot. It sticks to the Scrum playbook, making it a go-to for teams keen on keeping the Scrum spirit alive. It's all about boosting agility, making chats flow easily, and letting new folks blend in without a hitch. | ||
|
|
||
|
|