<b>Eduard Kabrinskiy - Azure devops sharepoint - Кабринский Рдуард
<h1>Azure devops sharepoint</h1>
<p><youtube></p>
Azure devops sharepoint <a href="http://remmont.com">News websites</a> Azure devops sharepoint
<h1>Azure DevOps Best Practices: Process and Overview (1 of 6)</h1>
<p style="clear: both"><img src="https://miro.medium.com/fit/c/56/56/2*kHZZj2ns2Hfhfk0zEIr6MA.jpeg" /></p>
<h4>Jason Nadrowski</h4>
<h4>Sep 30, 2019 В· 5 min read</h4>
<p style="clear: both"><img src="https://miro.medium.com/max/60/1*ufz1-ED69SSID21w1TCnRg.jpeg" /></p>
<h1>Introduction</strong></h1>
<p>Microsoft and its community has done a great job explaining the features of Azure DevOps, but I don’t think they’ve done a great job explaining how to best use it.</p>
<p>Part of the problem is the flexibility Azure DevOps provides. Instead of one process, it allows the DevOps admin to customize the project management processes around Basic, Scrum, Agile or CMMI. Further, each process can be customized providing an almost limitless array of choices. Limitless choices breeds confusion in direction.</p>
<p>I’ve spoken to many D evOps teams that are struggling to maximize Azure DevOps. In many cases, teams have trouble with the sheer magnitude of the information on Azure DevOps coupled with the limitless customization afforded to them. These articles focus on how to get up and running with Azure DevOps. They provide recommendations, warnings and commentary on how your team should be using Azure DevOps. It also seeks to provide Goldilocks</em> level of detail that are not too superficial nor too verbose — hopefully they are just right.</p>
<p>The series is primarily organized into the various subsections of Azure DevOps:</p>
<p><ol>
<li>Process and Overview (this article)</strong></li>
<li>Boards</li>
<li>Repos</li>
<li>Pipelines</li>
<li>Testing</li>
<li>Artifacts</li>
</ol>
</p>
<p>Although these articles focus on the Agile process, almost all of the recommendations can be applied to Basic, Scrum and CMMI customization Azure DevOps affords the team.</p>
<p>These articles assume the reader has a basic understanding of Azure DevOps and Agile.</p>
<h1>The Agile Process</h1>
<p>I prefer an Agile process. Accordingly, this series speaks to implementing Agile in Azure DevOps.</p>
<p>With that said, let’s underscore that Agile is flexible. Therefore, don’t feel you have to use every feature of Azure DevOps immediately. Remember the Agile Manifesto states “Individuals and interactions over processes and tools”. Focus on what works for your team.</p>
<p>If you are new to Agile, I highly recommend Mike Griffiths Book “PMI-ACP Exam Prep”. Not only it is a great start to your Agile journey, but it is all you need to prepare for the PMI-ACP exam.</p>
<h1>Project Portfolio Management</h1>
<p>Azure DevOps is designed to follow an Organization/Project hierarchy. Specifically, your DevOps projects are defined by the following URL: https://dev.azure.com/OrganizationName/ProjectName.</p>
<p>Avoid combining unrelated</strong> projects into one project (i.e. https://dev.azure.com/OrganizationName/Project1AndProject2) as a means to provide consolidated reporting. Instead, you should leverage Project and organization</strong>-scoped queries.</p>
<p>Azure DevOps allows you to create dashboards with pre-built and/or custom widgets. Your custom widgets could provide organization-scoped queries.</p>
<p>You should look to PowerBI to report on your portfolio of projects. PowerBI integrates with Azure DevOps through Azure DevOps Analytics.</p>
<p>With that said, Azure DevOps supports Scaled Agile. With scaled agile, you have break up a large project across several agile teams. Azure DevOps uses areas</em> to create a hierarchy of projects. An example Fabrikam hierarchy is shown below. I suggest you view Microsoft’s video walk-through of Agile at Scale to get started.</p>
<p style="clear: both"><img src="https://miro.medium.com/max/60/1*UlMkFzybBifqGMWV5bOcZg.png" /></p>
<p style="clear: both"><img src="https://miro.medium.com/max/60/1*Dad_5CIy5x5m7PClDEq8Ow.png" /></p>
<p>B ut, a word of warning</strong> before you go down this path with Azure DevOps areas. One of the tenants of the Twelve-Factor app <and>Beyond the Twelve-Factor Application] is “One codebase, one application”. When you use areas, you are essentially using one codebase with several applications. Although you can leverage security to separate the areas, I have found this to be a weak barrier with substantial potential to blend the application codebases.</p>
<h1>Overview — Summary</h1>
<p>As mentioned in the Wiki section below, I recommend creating a wiki page for the Project Charter and embedding it within the About this project</em> widget.</p>
<h1>Overview— Dashboards</h1>
<p>Dashboards provide an enormous amount of flexibility to showcase the state of your project. I view them as personalizations and I feel its inappropriate to specify a rigid design. However, I recommend that your organization have a consistent, but flexible, dashboard experience across all the projects. That consistency allows others — less familiar with the project — to quickly view the state of the project.</p>
<p>Currently, Microsoft provides a little over 30 widgets. These widgets can be augmented with your own custom widgets or from the extensions gallery (not a lot of widgets there yet).</p>
<p>Make sure to check out the DevOps Demo Generator. The Generator can create a number of sample projects in your Azure DevOps tenant that you can experiment with. On such example is SmartHotel360. SmartHotel360 is one of the more complete examples. Its dashboard is shown below.</p>
<p style="clear: both"><img src="https://miro.medium.com/max/60/1*iHUhwlNBs6jsdUor5y7fiw.jpeg" /></p>
<h1>Overview— Wiki</h1>
<p>I strongly recommend using the Azure DevOps wiki. Its a great way to share project information. Azure DevOps provides processes to support sophisticated wikis. However, I prefer the simpler Provisioned wikis</em> over the published code as a wiki</em>. I find that choice makes it easier to create and update project information.</p>
<p>In addition, to the wiki, you might leverage SharePoint, Teams, Slack and a whole host of other mediums for project communications and documentation. That is perfectly fine. But, you should ensure these are clearly listed and linked-to in the wiki.</p>
<p>Even if it exists, on another medium, I put the Agile Project Charter (or Vision depending on your process) on the wiki home page. I then use that wiki home page to populate the “About this project” for the Summary.</p>
<p>There are a lot of great resources online to help you with the project’s Agile Project Charter, but I prefer Mike Griffiths template shown below.</p>
<blockquote><p>For: Target customers<br />Who: Need (opportunity or problem)<br />The: Product/service name<br />Is a: Product category<br />That: Key benefits / reason to buy<br />Unlike: Primary competitive alternative(s)<br />We: Primary differentiation</p></blockquote>
<p>In addition to the Project Charter, I recommend posting and/or linking-to the following artifacts on the wiki.</p>
<p><ol>
<li>Product Roadmap</li>
<li>Release Plan</li>
<li>Sprint Planing Summaries</li>
<li>Sprint Retrospective Summaries</li>
<li>Release Retrospective Summaries</li>
<li>Product Backlog (if not automatically generated by Azure DevOps)</li>
<li>Sprint Backlog (if not automatically generated by Azure DevOps)</li>
</ol>
</p>
<h1>Summary</h1>
<p>This article is the first in a series of 6 articles about Azure DevOps best practices. We talked about Agile, Project Portfolio Management, and the Overview section for Azure DevOps.</p>
<p>The other series articles detail my best practices for Azure DevOps Boards, Repos, Pipelines, Testing and Artifacts.</p>
<h2>Azure devops sharepoint</h2>
<h3>Azure devops sharepoint</h3>
<p><youtube></p>
Azure devops sharepoint <a href="http://remmont.com">Latest headlines</a> Azure devops sharepoint
<h4>Azure devops sharepoint</h4>
Microsoft and its community has done a great job explaining the features of Azure DevOps, but I don’t think they’ve done a great job explaining how to best use it. Part of the problem is the…
<h5>Azure devops sharepoint</h5>
Azure devops sharepoint <a href="http://remmont.com">Azure devops sharepoint</a> Azure devops sharepoint
SOURCE: <h6>Azure devops sharepoint</h6> <a href="https://dev-ops.engineer/">Azure devops sharepoint</a> Azure devops sharepoint
#tags#<replace> -,-Azure devops sharepoint] Azure devops sharepoint#tags#</b>
<b>Эдуард Кабринский</b>
<a href=http://remmont.com>news</a>
Имя: LansingNeax
|
