This document provides instructions for using key features of Azure DevOps, including how to add team members, manage security, create teams, configure sprints and releases, create epics, features, user stories and tasks, customize dashboards and boards, integrate with Excel, and more. It outlines the Scrum lifecycle in Azure DevOps and how to plan work using epics, features, stories and tasks to track progress.
The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.
Getting Started - Introduction to Sprint ReviewsEasy Agile
Overview
- What is a sprint review?
- Benefits of sprint reviews
- Anatomy of a sprint review
- Guidelines for effective sprint review meetings
- conducting sprint reviews using Easy Agile User Story Maps
Backlog refinement is not a Scrum event, but instead is an ongoing activity during the Sprint required to decompose, describe, estimate, and order backlog items in the Product Backlog.
This material is divided into two sections. The first section reviews the basics of backlog refinement, covering various options for conducting the activity. The second section covers tips for maintaining a healthy backlog and potential anti-patterns.
This material was presented at Agile New England in July and August 2022 as "101" introduction and "202" advanced sessions.
The document discusses several agile ceremonies that originate from scrum methodology, including sprint planning, backlog grooming, daily stand-ups, iteration reviews, and retrospectives. It provides details on the purpose and structure of each ceremony, such as typical attendees, duration, and topics covered. The ceremonies are presented as regular meetings that facilitate communication within agile teams and help ensure continuous improvement.
Git 101 Presentation
The presentation introduces Git version control system including:
[1] An overview of version control systems and the basics of Git such as snapshots, local operations, and three main states of files.
[2] A comparison of features between Git and SVN such as distributed development and branching workflows.
[3] Instructions on setting up Git locally and with GitHub, and basic commands for creating and managing repositories, branches, commits, and merges.
This document provides an outline for a course on learning Git version control. The course covers getting Git setup, the basic concepts and workflow of Git, branching and merging, resolving conflicts, working with remote repositories, and various Git commands. The document lists several modules that will be covered, including getting started, everyday Git usage, branching, merging and rebasing, additional tools and concepts, and advice on applying the skills learned. The goal is to teach participants how to install and use Git for version control on individual, local, and distributed projects.
Scrum is an agile process for managing software development projects using empirical process control with inspection and adaptation cycles. The scrum process consists of monthly sprints resulting in potentially shippable increments and daily scrum meetings. A product backlog is prioritized and items are selected for each sprint backlog. The scrum team works during sprints to complete items and demonstrate progress at sprint reviews.
The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.
Getting Started - Introduction to Sprint ReviewsEasy Agile
Overview
- What is a sprint review?
- Benefits of sprint reviews
- Anatomy of a sprint review
- Guidelines for effective sprint review meetings
- conducting sprint reviews using Easy Agile User Story Maps
Backlog refinement is not a Scrum event, but instead is an ongoing activity during the Sprint required to decompose, describe, estimate, and order backlog items in the Product Backlog.
This material is divided into two sections. The first section reviews the basics of backlog refinement, covering various options for conducting the activity. The second section covers tips for maintaining a healthy backlog and potential anti-patterns.
This material was presented at Agile New England in July and August 2022 as "101" introduction and "202" advanced sessions.
The document discusses several agile ceremonies that originate from scrum methodology, including sprint planning, backlog grooming, daily stand-ups, iteration reviews, and retrospectives. It provides details on the purpose and structure of each ceremony, such as typical attendees, duration, and topics covered. The ceremonies are presented as regular meetings that facilitate communication within agile teams and help ensure continuous improvement.
Git 101 Presentation
The presentation introduces Git version control system including:
[1] An overview of version control systems and the basics of Git such as snapshots, local operations, and three main states of files.
[2] A comparison of features between Git and SVN such as distributed development and branching workflows.
[3] Instructions on setting up Git locally and with GitHub, and basic commands for creating and managing repositories, branches, commits, and merges.
This document provides an outline for a course on learning Git version control. The course covers getting Git setup, the basic concepts and workflow of Git, branching and merging, resolving conflicts, working with remote repositories, and various Git commands. The document lists several modules that will be covered, including getting started, everyday Git usage, branching, merging and rebasing, additional tools and concepts, and advice on applying the skills learned. The goal is to teach participants how to install and use Git for version control on individual, local, and distributed projects.
Scrum is an agile process for managing software development projects using empirical process control with inspection and adaptation cycles. The scrum process consists of monthly sprints resulting in potentially shippable increments and daily scrum meetings. A product backlog is prioritized and items are selected for each sprint backlog. The scrum team works during sprints to complete items and demonstrate progress at sprint reviews.
Git is a version control system that allows developers to have multiple versions of codebases and easily revert changes. Github is a website that hosts git repositories on remote servers, facilitating code sharing among teams through a graphical user interface. The document provides instructions on configuring git and connecting it to Github repositories, as well as describing basic workflows for branching, merging, rebasing, and resolving conflicts when integrating changes.
Git is a distributed revision control system that is widely used in the software development industry. The presentation was used in a lecture delivered in BITS-Pilani, India. The lecture served as a basic crash course on Git.
First, it sets off with a guide to install and configure git on various platforms.
Then, the basic working concepts of Git are explained.
This is followed by a detailed step-by-step guided demonstration of a sample workflow in Git.
Afterwards, Some auxillary commands that are frequently used are discussed briefly.
Finally, basic concepts of branching and merging are detailed.
The presentation ends with a few possible merge conflicts that occur in Git.
Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
Git-flow is a Git workflow that advocates using separate branches for features, releases, and hotfixes. It uses a master branch for production-ready code and a develop branch as the main branch where features are integrated. Feature branches are created from develop and merged back after completion. Release branches are created from develop for final testing before merging to both master and develop. Hotfix branches are directly created from master to quickly patch production releases. Pull requests are recommended to communicate changes between branches.
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
Many projects implicitly use some kind of risk-based approach for prioritizing testing activities. However, critical testing decisions should be based on a product risk assessment process using key business drivers as its foundation. For agile projects, this assessment should be both thorough and lightweight. PRISMA (PRoduct RISk MAnagement) is a highly practical method for performing systematic product risk assessments. Learn how to employ PRISMA techniques in agile projects using risk-poker. Carry out risk identification and analysis, see how to use the outcome to select the best test approach, and learn how to transform the result into an agile one page sprint test plan. Practical experiences are shared and results achieved employing product risk assessments. Learn how to optimize your test effort by including product risk assessment in your agile testing practices.
Description about agile practices in details for agile team members, agile practitioners, leaders and scrum coaches. This will help in understanding the agile practices better.
This guidebook can help team members to know what is expected out of Agile Transformation
PLEASE DOWNLOAD FROM HERE:https://drive.google.com/file/d/10ZXTbrhnl5CFQO_z_Ms2ZlGgCVap4lvg/view?usp=sharing
This document provides an overview of Scrum methodology. It defines Scrum as an agile framework that can help address complex problems and deliver high value products. The document outlines Scrum roles like Product Owner and Scrum Master. It also describes Scrum artifacts like Product Backlog and Sprint Backlog and events like the Daily Scrum. Finally, it provides a high-level overview of the Scrum process where a product backlog is created, sprints are planned and executed, and work is reviewed and improved upon iteratively until the product is complete.
This document provides an overview of an advanced scrum master workshop. It discusses the role and responsibilities of a scrum master, facilitation of scrum ceremonies like the daily scrum and retrospectives, navigating conflict, and growing as a leader. The scrum master is responsible for ensuring the team follows scrum principles and practices, removing impediments, and helping those outside the team understand how to best interact with the scrum process. Effective facilitation of meetings and retrospectives requires setting guidelines, using the right activities, and focusing discussions on problem-solving and continuous improvement.
This document outlines a story mapping approach for organizing an email client project. It breaks the project down into requirements, features, epics, and stories. The features are organized horizontally to map the correct business process sequence. The epics and stories are broken down vertically with priority indicated by their placement. The stories are further separated into separate releases.
Git is a version control system for tracking changes to files, while GitLab is a web-based Git repository manager with additional features. The document discusses Git and GitLab workflows including continuous integration, continuous delivery, and continuous deployment using GitLab. It also provides examples of common Git commands like add, commit, push, pull, branch, tag, and undo.
The document provides an overview of Git and its usage. It introduces Git as a source code management and distributed version control system. Key topics covered include setting up Git, creating local and remote repositories, tracking changes using commits, and collaborating through branches and by pushing to remote repositories. The document also includes exercises for readers to practice common Git commands.
Trunk-based development is a workflow where developers work directly on a main branch called the "trunk". The trunk is always in a deployable state. Short lived branches are used for developing new features which are then merged into the trunk after passing tests. Releases are cut from the trunk periodically. This allows for continuous integration and deployment while maintaining a stable release.
An Introduction to Scaled Agile Framework (SAFe)CA Technologies
To compete in today’s application economy, organizations have adopted agile execution techniques. But is that enough? Learn about SAFe and how to leverage this methodology to elevate your agile teams to deliver quality outcomes and align at the enterprise level.
For more information, please visit http://cainc.to/Nv2VOe
O documento apresenta os princípios e práticas do Extreme Programming (XP), abordando sua filosofia de abraçar a mudança e valorizar as pessoas. Descreve como o XP envolve ciclos curtos de desenvolvimento, planejamento incremental, testes automatizados e colaboração constante entre times e clientes.
Preguntas tipo examen Scrum Foundation Professional Certificate_SFPC_CertiPro...Giannina Costa
1. El documento presenta preguntas tipo examen sobre los principios y eventos de Scrum. 2. Scrum es un marco de trabajo liviano que permite el desarrollo de productos complejos mediante entregas incrementales. 3. Los cinco eventos de Scrum son: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective y Sprint.
This document provides a summary of common Git commands for setting up and working with repositories, saving changes, inspecting history, undoing changes, rewriting history, syncing with remote repositories, branching, and merging. It discusses initializing and cloning repositories, adding and committing changes, viewing logs and checking out commits, reverting and resetting changes, amending commits and rebasing, fetching and pushing to remote repositories, branching, and merging branches. It also cautions against amending shared commits or force pushing to avoid overwriting others' work.
The document discusses various metrics that can be used to measure progress on agile software development projects. It describes metrics like running tested features, earned business value, velocity, burn charts, and cumulative flow diagrams. It explains how these metrics can provide information on outcomes, identify areas for improvement, and influence team behavior in agile projects.
This document provides instructions for deploying the necessary environments and tools for a data analytics lab. It includes setting up a Hortonworks sandbox cluster on Azure, creating an Azure data science virtual machine, and optional configurations for Azure Data Lake and SQL Data Warehouse. Completing these steps ensures students have all required software and access installed prior to the lab. The document estimates completion of the prerequisite setup should take less than 30 minutes.
A selection of short stories where Azure DevOps saved the baconMatteo Emili
Session I held at MK.NET, where I introduced the services of Azure DevOps starting from real-world stories of usage or uncommon scenarios where it proved massively beneficial
Git is a version control system that allows developers to have multiple versions of codebases and easily revert changes. Github is a website that hosts git repositories on remote servers, facilitating code sharing among teams through a graphical user interface. The document provides instructions on configuring git and connecting it to Github repositories, as well as describing basic workflows for branching, merging, rebasing, and resolving conflicts when integrating changes.
Git is a distributed revision control system that is widely used in the software development industry. The presentation was used in a lecture delivered in BITS-Pilani, India. The lecture served as a basic crash course on Git.
First, it sets off with a guide to install and configure git on various platforms.
Then, the basic working concepts of Git are explained.
This is followed by a detailed step-by-step guided demonstration of a sample workflow in Git.
Afterwards, Some auxillary commands that are frequently used are discussed briefly.
Finally, basic concepts of branching and merging are detailed.
The presentation ends with a few possible merge conflicts that occur in Git.
Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
Git-flow is a Git workflow that advocates using separate branches for features, releases, and hotfixes. It uses a master branch for production-ready code and a develop branch as the main branch where features are integrated. Feature branches are created from develop and merged back after completion. Release branches are created from develop for final testing before merging to both master and develop. Hotfix branches are directly created from master to quickly patch production releases. Pull requests are recommended to communicate changes between branches.
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
Many projects implicitly use some kind of risk-based approach for prioritizing testing activities. However, critical testing decisions should be based on a product risk assessment process using key business drivers as its foundation. For agile projects, this assessment should be both thorough and lightweight. PRISMA (PRoduct RISk MAnagement) is a highly practical method for performing systematic product risk assessments. Learn how to employ PRISMA techniques in agile projects using risk-poker. Carry out risk identification and analysis, see how to use the outcome to select the best test approach, and learn how to transform the result into an agile one page sprint test plan. Practical experiences are shared and results achieved employing product risk assessments. Learn how to optimize your test effort by including product risk assessment in your agile testing practices.
Description about agile practices in details for agile team members, agile practitioners, leaders and scrum coaches. This will help in understanding the agile practices better.
This guidebook can help team members to know what is expected out of Agile Transformation
PLEASE DOWNLOAD FROM HERE:https://drive.google.com/file/d/10ZXTbrhnl5CFQO_z_Ms2ZlGgCVap4lvg/view?usp=sharing
This document provides an overview of Scrum methodology. It defines Scrum as an agile framework that can help address complex problems and deliver high value products. The document outlines Scrum roles like Product Owner and Scrum Master. It also describes Scrum artifacts like Product Backlog and Sprint Backlog and events like the Daily Scrum. Finally, it provides a high-level overview of the Scrum process where a product backlog is created, sprints are planned and executed, and work is reviewed and improved upon iteratively until the product is complete.
This document provides an overview of an advanced scrum master workshop. It discusses the role and responsibilities of a scrum master, facilitation of scrum ceremonies like the daily scrum and retrospectives, navigating conflict, and growing as a leader. The scrum master is responsible for ensuring the team follows scrum principles and practices, removing impediments, and helping those outside the team understand how to best interact with the scrum process. Effective facilitation of meetings and retrospectives requires setting guidelines, using the right activities, and focusing discussions on problem-solving and continuous improvement.
This document outlines a story mapping approach for organizing an email client project. It breaks the project down into requirements, features, epics, and stories. The features are organized horizontally to map the correct business process sequence. The epics and stories are broken down vertically with priority indicated by their placement. The stories are further separated into separate releases.
Git is a version control system for tracking changes to files, while GitLab is a web-based Git repository manager with additional features. The document discusses Git and GitLab workflows including continuous integration, continuous delivery, and continuous deployment using GitLab. It also provides examples of common Git commands like add, commit, push, pull, branch, tag, and undo.
The document provides an overview of Git and its usage. It introduces Git as a source code management and distributed version control system. Key topics covered include setting up Git, creating local and remote repositories, tracking changes using commits, and collaborating through branches and by pushing to remote repositories. The document also includes exercises for readers to practice common Git commands.
Trunk-based development is a workflow where developers work directly on a main branch called the "trunk". The trunk is always in a deployable state. Short lived branches are used for developing new features which are then merged into the trunk after passing tests. Releases are cut from the trunk periodically. This allows for continuous integration and deployment while maintaining a stable release.
An Introduction to Scaled Agile Framework (SAFe)CA Technologies
To compete in today’s application economy, organizations have adopted agile execution techniques. But is that enough? Learn about SAFe and how to leverage this methodology to elevate your agile teams to deliver quality outcomes and align at the enterprise level.
For more information, please visit http://cainc.to/Nv2VOe
O documento apresenta os princípios e práticas do Extreme Programming (XP), abordando sua filosofia de abraçar a mudança e valorizar as pessoas. Descreve como o XP envolve ciclos curtos de desenvolvimento, planejamento incremental, testes automatizados e colaboração constante entre times e clientes.
Preguntas tipo examen Scrum Foundation Professional Certificate_SFPC_CertiPro...Giannina Costa
1. El documento presenta preguntas tipo examen sobre los principios y eventos de Scrum. 2. Scrum es un marco de trabajo liviano que permite el desarrollo de productos complejos mediante entregas incrementales. 3. Los cinco eventos de Scrum son: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective y Sprint.
This document provides a summary of common Git commands for setting up and working with repositories, saving changes, inspecting history, undoing changes, rewriting history, syncing with remote repositories, branching, and merging. It discusses initializing and cloning repositories, adding and committing changes, viewing logs and checking out commits, reverting and resetting changes, amending commits and rebasing, fetching and pushing to remote repositories, branching, and merging branches. It also cautions against amending shared commits or force pushing to avoid overwriting others' work.
The document discusses various metrics that can be used to measure progress on agile software development projects. It describes metrics like running tested features, earned business value, velocity, burn charts, and cumulative flow diagrams. It explains how these metrics can provide information on outcomes, identify areas for improvement, and influence team behavior in agile projects.
This document provides instructions for deploying the necessary environments and tools for a data analytics lab. It includes setting up a Hortonworks sandbox cluster on Azure, creating an Azure data science virtual machine, and optional configurations for Azure Data Lake and SQL Data Warehouse. Completing these steps ensures students have all required software and access installed prior to the lab. The document estimates completion of the prerequisite setup should take less than 30 minutes.
A selection of short stories where Azure DevOps saved the baconMatteo Emili
Session I held at MK.NET, where I introduced the services of Azure DevOps starting from real-world stories of usage or uncommon scenarios where it proved massively beneficial
Leveraging Azure DevOps across the EnterpriseAndrew Kelleher
In this presentation we exploring how teams across the enterprise can leverage Azure DevOps' by diving into its different capabilities and services. Specifically in the context of Azure platform teams that can leverage agile and DevOps practices when deploying and supporting services within Azure.
Azure DevOps Services is a cloud-hosted platform that provides scalable and globally available services with a high SLA. Azure DevOps Server is installed on-premises and runs on SQL Server, allowing customers to keep their data within their network. Key differences include simplified management and automatic updates with Services, while Server provides access to SQL Server reporting and on-premises data storage. Customers should consider their data security, management, and reporting needs to determine which platform best fits their requirements.
This document provides instructions for a hands-on lab on using Azure DevOps deployment groups. It describes how deployment groups can be used to deploy an application to multiple servers in a sequenced manner. The steps show how to set up target Azure virtual machines, configure the necessary service connections in Azure DevOps, create deployment groups, and configure a release pipeline to deploy to the deployment groups. Prerequisites for the lab are also provided.
This document discusses implementing a CI/CD pipeline for UiPath projects using Azure DevOps. It covers setting up Azure DevOps and configuring the necessary prerequisites. It demonstrates integrating UiPath with Azure DevOps using tasks that allow packaging, deploying, running jobs and tests. The demo shows creating a sample YAML pipeline to build and package a UiPath project. Best practices for continuous deployment strategies and QA for UiPath solutions are also discussed.
This document provides an introduction to Azure DevOps. It discusses the goals of DevOps including accelerating time to market, adapting to market changes, and maintaining system stability. It also outlines some key aspects of adopting a DevOps culture. The document then describes several Azure DevOps services including Azure Boards for tracking work, Azure Repos for source control, Azure Pipelines for continuous integration and delivery, Azure Artifacts for package management, and Azure Test Plans for testing. It provides overviews and benefits of each service.
Azure DevOps is a DevOps platform that provides tools to help teams plan work, collaborate on code development, and implement continuous delivery pipelines. It includes Azure Boards for tracking work items, Azure Repos for version control, Azure Pipelines for builds/releases, Azure Test Plans for testing, and Azure Artifacts for package management. These tools work together to help teams deliver value faster through practices like continuous integration, deployment, and monitoring. The document provides an overview of each tool and how they integrate as part of an end-to-end DevOps solution. It also shares customer stories about how companies like GEICO have been able to reduce release cycles and engage customers more through use of Azure DevOps.
Microsoft recently released Azure DevOps, a set of services that help developers and IT ship software faster, and with higher quality. These services cover planning, source code, builds, deployments, and artifacts.
One of the great things about Azure DevOps is that it works great for any app and on any platform regardless of frameworks.
In this session, I will give you a quick overview of what Azure DevOps is and how you can quickly get started and incorporate it into your continuous integration and deployment processes.
DevOps is an approach that combines people, processes, and products to enable continuous delivery of value to end users. It brings together development and operations teams, automates the software delivery process, and provides continuous software updates and monitoring. Key technologies for DevOps include continuous integration (CI), continuous deployment (CD), and continuous monitoring. Azure DevOps provides tools like Azure Pipelines, Azure Boards, Azure Repos, and Azure Test Plans to support DevOps practices and workflows in the cloud.
DevOps (Continuous Integrations, Continuous Delivery & Continuous deployment using Jenkins and Visual studio team services, setting up VTST build Agents, Integrating VSTS with SonarQube, NDepend,) , Complete automation of pushing code into VSTS from Visual Studio, Building Code by a Jenkin Server hosted on Azure and pushing that successful build on to Azure Web App via Release Pipeline or directly from Jenkins,VSTS Default agents, Setting up local agent from scratch, Setting up agents for code build, VSTS, Visual Studio Online Agents, Agent Pools, Hosted Agents, Hosted VS2017. Hosted Linux Agents, Setting up agent on VS Dev Test Labs, Setting up Template Parameters for Continuos Pipeline, Build Agent Creation Dynamically, Random Machine Name, Random Passwords, Dynamic Agent creation in VS Dev Test labs, Sonarcube, Code quality, Code Analysis, MSBuild, Integrate VSTS Build with NDepend, Package manager, Monolithic Architecture, Nuget, Package management, Npm js.com, Semantic versioning, Creating a nuget package, nuspec file, GitVersion Plugin, FeedURL, Chocolatey for package management, Chocolatey, chocolatey workflow,
Pyramid is a flexible Python web framework that allows applications to start small and grow as needed without enforcing specific technologies or patterns. The document provides suggestions for structuring larger Pyramid projects, choosing persistence mechanisms, assembling toolkits, using traversal vs URL dispatch, testing, documenting, and deploying applications using buildout, supervisor, and Nginx/mod_wsgi. Project layout, tools, and deployment options depend on each application's specific needs and scope.
Azure Artifacts is an extension that makes it easy to discover, install, and publish NuGet, npm, and Maven packages in Azure DevOps. It's deeply integrated with other hubs like Build so that package management can become a seamless part of your existing workflows
The document discusses Google Cloud Platform (GCP), which provides a set of cloud computing services including computing, storage, databases, networking, big data, machine learning, and IoT. Some key benefits of GCP include running applications on Google's global infrastructure, focusing on product development rather than system administration, mixing and matching different cloud services, and scaling applications easily to handle millions of users in a cost-effective way. GCP offers both fully managed platform services and flexible virtual machines. It also provides storage, database, and networking services to store and access data.
Zure Azure PaaS Zero to Hero - DevOps training dayOkko Oulasvirta
This document provides an overview of Azure DevOps and related Azure services for continuous integration, delivery, and monitoring. It discusses DevOps practices including source control with Azure Repos, work tracking with Azure Boards, continuous integration and deployment pipelines with Azure Pipelines, infrastructure as code with ARM templates, and application monitoring with Application Insights. It also covers security practices like role-based access control and use of Azure Key Vault for secrets management. Live demos are provided for many of the Azure DevOps features and services discussed.
The document provides an overview of Azure DevOps and why JavaScript developers should use it. It discusses features like source control, boards for tracking work items, pipelines for continuous integration and delivery, and testing. It also includes a demo of setting up a sample Create React App project in Azure DevOps, including configuring a pipeline to build and deploy the app to an Azure App Service. Resources for learning more about Azure DevOps, using it with JavaScript projects, and understanding Git are also provided.
Azure News Slides for October2017 - Azure Nights User GroupMichael Frank
James Rooke presented on Azure Stack at Microsoft HQ in Melbourne. The presentation included an overview of recent Azure announcements, a deep dive session on Azure Stack, and a meet the team segment. Key announcements included the general availability of the Azure Managed Applications service, PowerShell support in Azure Cloud Shell, and new features for Azure services like SQL Database, Stream Analytics, and Machine Learning.
This is an overview of Azure Artifacts and how you can add a fully integrated package management to your continuous integration/continuous delivery (CI/CD) pipelines with a single click. Azure Artifacts allows you to share your code effortlessly by creating and sharing Maven, npm, and NuGet package feeds from public and private sources.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
3. 2
PatrickVideos.com
Contents
What is Azure DevOps?.................................................................................................................................4
Getting Started..............................................................................................................................................5
Preview the latest features.......................................................................................................................6
How to Add Team members? .......................................................................................................................7
Manage Team member security...................................................................................................................8
Create a new Team.......................................................................................................................................9
Scrum Lifecycle ...........................................................................................................................................10
How to configure Release and Sprint cycles...............................................................................................11
Setting up Iteration paths – Project Configuration.................................................................................11
Setting up Area paths – Project Configuration .......................................................................................12
Team Configuration ................................................................................................................................13
Epics, Features, User Stories, Tasks ............................................................................................................14
Creating Work Items...................................................................................................................................15
Create an Epic .........................................................................................................................................15
How to Create a Feature?...........................................................................................................................16
How to Create a User Story?.......................................................................................................................17
Follow a User Story .................................................................................................................................17
Attach a document .................................................................................................................................18
History of User Story...............................................................................................................................18
Mass update to user stories....................................................................................................................19
How to create a Task?.................................................................................................................................20
Customize column options .........................................................................................................................22
Tracking work using Task board..................................................................................................................23
Customize Board columns and swim lanes.................................................................................................23
Tracking Bugs ..............................................................................................................................................24
Query Work Items.......................................................................................................................................25
Tree Query ..............................................................................................................................................26
Run Queries and Email the results..............................................................................................................27
Create charts out of queries .......................................................................................................................28
Customize Dashboard.................................................................................................................................30
Manage your notifications..........................................................................................................................31
4. 3
PatrickVideos.com
Using Filters.............................................................................................................................................33
Create a Wiki for your project ....................................................................................................................34
Integrating with Excel Trouble shooting.....................................................................................................35
Integrating with Excel .............................................................................................................................35
Opening from Excel.................................................................................................................................35
Custom Process...........................................................................................................................................37
5. 4
PatrickVideos.com
What is Azure DevOps?
Azure DevOps Services is a cloud service for collaborating on code development. It
provides an integrated set of features that you access through your web browser or IDE
client, including the following:
• Git repositories for source control of your code
• Build and release services to support continuous integration and delivery of your
apps
• Agile tools to support planning and tracking your work, code defects, and issues
using Kanban and Scrum methods
• A variety of tools to test your apps, including manual/exploratory testing, load
testing, and continuous testing
• Highly customizable dashboards for sharing progress and trends
• Built-in wiki for sharing information with your team
6. 5
PatrickVideos.com
Getting Started
Azure DevOps (VSTS / TFS) access via the Web browser.
A project provides a repository for source code and a place for a group of people to plan, track
progress, and collaborate on building software solutions.
** Always use the Create project button to create a project, so that we can select the scrum
process.
8. 7
PatrickVideos.com
How to Add Team members?
When you create your project, a team of the same name is automatically created. For small
teams, this is sufficient. However, for enterprise-level organizations, it may be necessary to scale
up, to create additional teams and/or projects.
9. 8
PatrickVideos.com
Manage Team member security
Open the web portal and choose the project where you want to add users or groups.
Choose Project Settings and then Permissions.
Additional details
https://docs.microsoft.com/en-us/azure/devops/organizations/security/add-users-team-
project?view=vsts&tabs=new-nav
10. 9
PatrickVideos.com
Create a new Team
Additional details
https://docs.microsoft.com/en-us/azure/devops/user-guide/project-admin-tutorial?view=vsts
11. 10
PatrickVideos.com
Scrum Lifecycle
With Scrum, teams plan and track work at regular time intervals, referred to as a sprint
cadence. You define sprints to correspond to the cadence your team uses.
Many teams choose a two or three week cadence. However, you can specify shorter or
longer sprint cycles. Also, you can create a release schedule which encompasses several
sprints.
12. 11
PatrickVideos.com
How to configure Release and Sprint cycles
To create or modify areas or iterations, you must be a member of the Project
Administrators group
Setting up Iteration paths – Project Configuration
Iteration paths allow you to group work into sprints, milestones, or other event-specific or time-
related period.
Additional details
https://docs.microsoft.com/en-us/azure/devops/organizations/settings/set-iteration-paths-
sprints?view=vsts&tabs=new-nav
13. 12
PatrickVideos.com
Setting up Area paths – Project Configuration
**Creating a team, creates an area path with that name.
Most teams are using area paths to group work by team and grouping by product/feature area through
use of epics or features.
Area paths allow you to group work items by team, product, or feature area.
14. 13
PatrickVideos.com
Team Configuration
**Once you create Iterations and Areas under project configuration, you need to add it under
Team configuration, else it will not show up while creating user stories.
15. 14
PatrickVideos.com
Epics, Features, User Stories, Tasks
The first step in planning your sprint is to assign work from your backlog to a sprint. Your team
builds the sprint backlog during the sprint planning meeting, typically held on the first day of
the sprint. Each sprint corresponds to a time-boxed interval which supports your team's ability
to work using Agile processes and tools. During the planning meeting, your product owner
works with your team to identify those stories or backlog items to complete in the sprint.
18. 17
PatrickVideos.com
How to Create a User Story?
Click on the + sign next to the feature to create user stories.
**Tags are discussed and created by the Team. Tags help in search.
Follow a User Story
You can choose to follow a User Story is you are interested in updates to the story.
21. 20
PatrickVideos.com
How to create a Task?
You add tasks to backlog items when you want to track the work required to implement them
and to estimate the work assigned to individual team members and the team. The capacity tool
tells you how much work your team can commit to. However, to compare capacity with actually
planned work, you need to define and estimate tasks for each backlog item.
22. 21
PatrickVideos.com
You can create a Copy of the work item & Email the work item.
When you create copy of work item, select include existing links if you want the work item to have the
same parent.
24. 23
PatrickVideos.com
Tracking work using Task board
Your task board provides a visualization of flow and status of each sprint task. With it, you can
focus on the status of backlog items as well as work assigned to each team member.
Customize Board columns and swim lanes
Additional details
https://docs.microsoft.com/en-us/azure/devops/boards/sprints/task-board?view=vsts&tabs=new-nav
26. 25
PatrickVideos.com
Query Work Items
A query lists a filtered set of work items. You can initiate a query using the query editor.
Optionally, you can perform an adhoc search using the search box.
To find work items assigned to you or your team, run a query. A number of work item queries
are predefined with your process. Also, members of your team may have created shared queries
that you can view and run. Oftentimes, it's easier to define a new query by building on the query
definition that's already available to you.
32. 31
PatrickVideos.com
Manage your notifications
As changes occur to your code base, builds, work items, and other operations, you can receive
email notifications. For example, you can set an alert to be notified whenever a bug that you
opened is resolved or a work item is assigned to you.
Turn on or off notifications and create custom notifications.
35. 34
PatrickVideos.com
Create a Wiki for your project
Each team project can be provisioned with a wiki. Use it to share information with your team to
understand, use, and contribute to your project.
Additional details:
https://docs.microsoft.com/en-us/azure/devops/project/wiki/wiki-create-repo?view=vsts&tabs=new-
nav
36. 35
PatrickVideos.com
Integrating with Excel Trouble shooting
If you are unable to see the Team menu or open in excel please see below link.
https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/office/tfs-office-integration-
issues?view=vsts
Integrating with Excel
**In Excel Team menu you can connect to VSTS and run a query.
Opening from Excel