Abstract
Now that you’ve looked at the capabilities of the professional DevOps environment and a mix of tools that can be a part of it, we’ll drill down into each product within the Azure DevOps family and set it up in the proper way. You’ll certainly want to customize the configuration, but your suggested configuration works great in 80% of the cases. If you’ve already read the book The Phoenix Project by Kim, Spafford, and Behr, you’ll recognize the principles we implement in this chapter. You might want to create a new project so that you can test different configurations as you read. Once you have your Azure DevOps project created, take a glance at your project settings, and select the products that you’d like enabled.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Pit of success: start new process templates inheriting from Basic
- 2.
Kim, Behr, & Spafford, 2013
- 3.
Beck, et al., 2001
- 4.
Microsoft to acquire GitHub for $7.5 billion, n.d.
- 5.
Adopt a Git branching strategy, n.d.
- 6.
Azure Boards Documentation, n.d.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2019 Jeffrey Palermo
About this chapter
Cite this chapter
Palermo, J. (2019). Tracking Work. In: .NET DevOps for Azure. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-5343-4_4
Download citation
DOI: https://doi.org/10.1007/978-1-4842-5343-4_4
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-5342-7
Online ISBN: 978-1-4842-5343-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)