Module 2 Flashcards
Is a method to frequently deliver apps to customer by introducing automation into the stages of app development.
CI/CD
Continuous integration, continuous delivery and continuous deployment.
Is the practice of automating the integration of code changes from multiple contributors into a single software project. It’s primary DevOps best practice, allowing developers to frequently merge code changes into a central repository where builds and tests then run.
CI (Continuous Integration)
CI/CD Tools what are they?
Jenkins
CircleCI
TeamCity
Bamboo
GitLab
Buddy
Travis CI
Codeship
Is an open-source automation server in which the central build and continuous integration process take place.
Jenkins
Is a CI/CD tool that supports rapid software development and publishing
CircleCI
Is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.
Continuous Integration (CI)
Two types of Board
Kanban and Taskboards
support visualizing the flow of work and monitoring metrics to optimize that flow.
Kanban and Taskboards.
- Track requirements, are sprint independent, and you monitor the flow through the cumulative flow chart.
Kanban Boards
- Track tasks defined for a sprint and you monitor the flow via the sprint burndown chart.
Taskboards.
Issues and Tasks are used to track work, while Epics are used to group work under larger scenarios. As works progresses from not started to completed, you update the State workflow field from TO DO, DOING AND DONE
WORK ITEM TYPES
-EPICS
-ISSUE
-TASK
Basic Process
This process works great if you want to track user stories and (optionally) bugs on the Kanban Board, or tracks bugs and tasks on the taskboard.
Agile Process
User stories and Tasks are used to track work, Bugs track code defects, and Epics and Features are used to group work under larger scenarios. As works progresses from not started to completed, you update the State workflow field from NEW, ACTIVE, RESOLVED, AND CLOSED
WORK ITEM TYPES
-EPIC
-FEATURE
-USER STORY
-TASK
ISSUE TRACKING
-ISSUE
CONFIGURABLE
-BUG
-TASK
Agile Process WITs & Workflow
This process works great if you want to track product backlog items (PBIs) and bugs on the Kanban Board, or break PBIs and bugs down into tasks on the taskboard.
Scrum process
Product Backlog Items and Tasks are used to track work, Bugs track code defects, and Epics and Features are used to group work under larger scenarios. As works progresses from not started to completed, you update the State workflow field from NEW, APPROVED, COMMITED, and DONE.
WORK ITEM TYPES
-EPIC
-FEATURE
-PRODUCT BACKLOG ITEM
-TASK
ISSUE TRACKING
-IMPEDIMENT
CONFIGURABLE
-BUG
-TASK
Scrum Process WITs & Workflow
When your team follows more formal project methods that require a framework for process improvement and an auditable record of decisions. With this process, you can track requirements, change requests, risks, and reviews.
CMMI Process
Requirements and Tasks are used to track work, Bugs track code defects, and Epics and Features are used to group work under larger scenarios. As work progresses from not started to completed, you update the State workflow field from PROPOSED, ACTIVE, RESOLVED, and CLOSED.
WORK ITEM TYPES
-EPIC
-FEATURE
-REQUIREMENT
-TASK
ISSUE, CHANGES & RISK MANAGEMENT
-CHANGE REQUEST
-REVIEW
-ISSUE
-RISK
CONFIGURABLE
-BUG
-TASK
CMMI Process WITs & Workflow
Provides developer services to support teams to plan work, collaborate on code development, and build and deploy applications. Developers can work in the cloud using this Services or on-premises using this server. It was formerly named VISUAL STUDIO TEAM FOUNDATION SERVER (TFS)
Azure DevOps
Delivers a suite of Agile tools to support planning and tracking work, code defects, and issues using Kanban and Scrum methods
Azure Boards
is the container for several projects that share resources
Organization
defines the building blocks of the work item tracking system and supports the inheritance process model for Azure Boards. This model supports customization of projects through a WYSIWYG user interface
Process
Defines the building blocks of the work item tracking system as well as other sub-systems you access through Azure Boards.
Process template
Is the most lightweight and is in a selective Preview
Basic
is the next most light-weight.
Scrum
