Azure DevOfsdfsdfsfasfsdfasfsdfsdfsdps.pdf
- 1. Azure DevOps
- 2. • Introduction to Azure DevOps • Getting Started with Azure DevOps – Create and Configure a New Development Project • Using Agile/Scrum Features in Azure DevOps • Source Code Control (SCC) with Azure DevOps • Bug Tracking with Azure DevOps Contents
- 4. • Tool for Software Engineering –Planning, Collaboration, Source Code Control, Bug Tracking, etc. • Developed by Microsoft • https://dev.azure.com • Free for 5 Developers + Stakeholders Azure DevOps
- 5. • Integrated with Visual Studio • Agile/Scrum Tools –Product Backlog –Sprint Backlog and Taskboard • Source Code Control (SCC) • Bug Reporting and Tracking • ++ (Not covered in this tutorial) Features
- 6. Getting Started with Azure DevOps
- 7. Create New Project Note!!! Select“Advanced”Settings Version control = Git Work item process = Scrum Enter a meaningful Name for your Project Enter a meaningful Description for your Project https://dev.azure.com Note! (Aug. 2024)!“Team Foundation Version Control (TFVC)” is no longer supported for New Projects Git
- 8. Invite/Add Members By adding users here, you will only get“Read” rights (“Stakeholder”). To get full access (“Administrator” access) go into “Organization setting”. Select“Users”and then “Add users”.
- 9. Give Users“Full Access” in Organization Settings To get full access (“Administrator”access) go into “Organization setting”. Select “Users”and then “Add users”. Then Access level = Basic and the proper Project. Make sure to select “Send email ..” as well
- 10. Project Settings • In Scrum we divide the work into different Iterations • An Iteration is called a Sprint • A Sprint is typically 2-4 weeks long Show/Hide Features
- 11. Agile/Scrum Features in Azure DevOps
- 12. Product Backlog
- 13. Product Backlog • The Scrum Product Backlog is simply a list of all things that needs to be done within the project. • It replaces the traditional requirements specification. • So basically, The Product Backlog is a List of all the Requirements for a given Software System. Product Backlog Items (PBI)
- 14. Work Items 3 important Work Item Types related to Product Backlog • Product Backlog Item (PBI) • Feature – Can be used to group PBIs that belong together • Task – Divide a PBI into doable Tasks. Each PBI needs to be broken down into a set of Tasks. A Task is something that should be done by the developer
- 15. Feature → PBI → Task • Feature X – Product Backlog Item A ✓ Task A.1 ✓ Task A.2 – Product Backlog Item B ✓ Task B.1 ✓ Task B.2 • Feature Y – Product Backlog Item C ✓ Task C.1 ✓ Task C.2 etc. Each Product Backlog Item is broken down in one or more Tasks by the Developer Features makes in easier to structure all the Product Backlog Items
- 16. Example
- 17. Sprints/Taskboard A Taskboard in Scrum has 3 columns • To Do • In Progress • Done Within a Sprint you move the Tasks from left to right as the status changes Illustrative Example:
- 19. Source Code Control with Azure DevOps
- 20. Configure .gitignore File Select“VisualStudio” and click “Initialize”
- 21. .gitignore
- 22. Local Clone Project URL: https://usn24@dev.azure.com/usn24/ProjectHPH/_git/ProjectHPH
- 23. Visual Studio – Clone a repository “Repository location” – If it is not filled out automatically, copy the URL from Azure DevOps Path: local Path on your hard drive where you want to store your local version (clone) of the source code
- 24. Clone a Repository Either enter the URL directly, or if you don’t know the URL, select “Browse a repository”and “Azure DevOps”
- 26. Git Terms Git maintains a local copy of the entire repository, so you need now and then to sync your local activities with the server. • Fetch - It's important to fetch and pull before you push. – Fetching checks if there are any remote commits that you should incorporate into your local changes. If you see any, pull first to prevent any upstream merge conflicts. • Pull - Always pull before you push. When you pull first, you can prevent upstream merge conflicts. • Push - When you create commits you save local snapshots of your code. You then need to use Push to push the commits to the server. • Sync - Use this operation to both Pull, then Push, sequentially.
- 27. Git Tools in Visual Studio Git menu Git Changes window Git Repository window
- 28. Commit Changes Commit Changes: When you create commits you save local snapshots of your code. You then need to use Push to push the commits to the server
- 29. Push Changes When you have committed the changes, you then need to use Push to push the commits to the server.
- 30. Bug Tracking with Azure DevOps
- 31. Work Items
- 32. Bug Reporting
- 33. Queries Queries are used to get a list of specific Work Items