Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

DevOps > Module 2 > Flashcards

Module 2 Flashcards

1
Q

Is a method to frequently deliver apps to customer by introducing automation into the stages of app development.

A

CI/CD
Continuous integration, continuous delivery and continuous deployment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

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.

A

CI (Continuous Integration)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

CI/CD Tools what are they?

A

Jenkins
CircleCI
TeamCity
Bamboo
GitLab
Buddy
Travis CI
Codeship

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Is an open-source automation server in which the central build and continuous integration process take place.

A

Jenkins

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Is a CI/CD tool that supports rapid software development and publishing

A

CircleCI

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

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.

A

Continuous Integration (CI)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Two types of Board

A

Kanban and Taskboards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

support visualizing the flow of work and monitoring metrics to optimize that flow.

A

Kanban and Taskboards.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q
  • Track requirements, are sprint independent, and you monitor the flow through the cumulative flow chart.
A

Kanban Boards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q
  • Track tasks defined for a sprint and you monitor the flow via the sprint burndown chart.
A

Taskboards.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

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

A

Basic Process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

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.

A

Agile Process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

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

A

Agile Process WITs & Workflow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

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.

A

Scrum process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

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

A

Scrum Process WITs & Workflow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

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.

A

CMMI Process

17
Q

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

A

CMMI Process WITs & Workflow

18
Q

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)

A

Azure DevOps

19
Q

Delivers a suite of Agile tools to support planning and tracking work, code defects, and issues using Kanban and Scrum methods

A

Azure Boards

20
Q

is the container for several projects that share resources

A

Organization

21
Q

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

A

Process

22
Q

Defines the building blocks of the work item tracking system as well as other sub-systems you access through Azure Boards.

A

Process template

23
Q

Is the most lightweight and is in a selective Preview

A

Basic

24
Q

is the next most light-weight.

A

Scrum

25
Q

stands for Capability Maturity Model Integration, provides the most support for formal processes and change management.

A

CMMI

26
Q

Are use to track significant features or requirements.

A

Epics

27
Q

Are use to track user stories, bugs, or other smaller items of work.

A

Issues

28
Q

Are use to track even smaller amounts of work for which you want to track time either in hours or days.

A

Tasks

29
Q

Represents your project plan, the roadmap for what your team plans to deliver. Your backlog also provides a repository of all the information you need to track and share with your team.

A

Product Backlog

30
Q

track high-level features, scenarios or epics.

A

Portfolio Backlogs

31
Q

Prioritized list of user stories, deliverables or work you plan to build or fix

A

Product Backlog

32
Q

Contain just those items that each team is working on during a scheduled sprint or iteration period

A

Sprint Backlogs

33
Q

Are used to calculate velocity and to forecast sprints.

A

Effort

DevOps (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions