The Azure DevOps Services: Essentials – Git with Visual Studio WorkshopPLUS is an instructor-led training course that provides participants with the fundamental knowledge that is required to use Git with Visual Studio. It provides detailed guidance for working with version control, work items, automated builds, and deployments.
In this post, App Dev Managers Bernard Apolinario, Sujith Nair, and Latha Natarajan gives a thorough overview of GitHub Actions.
Agile’s approach to balancing capacity against demand starts from the principal of embracing change. Adaptability is Agile’s superpower. Waterfall projects will have a place for the foreseeable future. The most important thing that an organization can do is define when and how to apply each of the strategies.
Azure DevOps provides features that enable your organization and teams adopt modern software engineering practices, such as InnerSource using features like forks and pull requests. Thus, enabling and encouraging code sharing and reuse thereby reducing engineering costs, facilitating faster time to market, and additional feature enablement.
One of the biggest mistakes I see in any project is the development team failing to get outside feedback. Whether project teams wait until the very end of a project to reach our or they don’t get feedback at all, these teams are missing out on one of the best sources of information to help build a better solution.
In this post, App Dev Manager Chris Westbrook explores scenarios for Azure Artifacts upstream sources.
With GitHub and Azure DevOps you have a powerful combination of tools to help you develop world class applications where you are an open source or enterprise developer.
In this post, App Dev Manager Andy Moore shows how to create cross-organizational reports for Azure DevOps with Power BI. When using Azure DevOps to manage teams, backlogs, work items and bugs there are tools available for quick reporting and understanding of the current state of the project. Dashboards provide an easily digestible view...
Successfully delivering valuable functionality in the first sprint or three can be difficult, and for some, simply impossible. But the lessons learned from the attempt are invaluable! Taking an early hit, failing in the short term is unimportant if it improves the chance of success in the long run.
Asking these questions during sprint planning is a great way to start a conversation that will both achieve the principles of collaboration and engagement, and ensure a greater understanding of the value that the product is expected to deliver to its users.