Technical Jargon

Question 1

Waterfall

Answer 1

Project management methodology that is best used in projects that have predictable requirements.
There are a set amount of steps from beginning to end and the regulations and requirements are known upfront. Development happens in a step by step manner. (Most suitable for hardware based technological projects)

Any new requirements from the client will restart the development cycle

Ex: Building a house, waterfall would best suit this

Question 2

Regression Testing

Answer 2

Type of software testing where they are making sure the current overall software or application is functioning how its supposed to.

Ex: Your testers will have to test the application to see if any new code has negatively changes how an application was before. If there is a negative impact, the devs have to fix the change so that the application works as it did before

Question 3

Latency

Answer 3

The delay between a user’s actions and a web applications response to that action or LAG/LAGGING

Ex: Devs and testers may complain about their systems being slow or lagging. The DevOps team should be the team that addressed the matter to make the environment run as expected.

Question 4

Spike

Answer 4

[Type of enabler story] Research task aimed at answering a question or gathering information, rather than at producing working software.

Ex: Dev team may not know how to solve a particular problem, so you can allocate a specific type of user story, spike, to allow for them to do research. These stories are pointed high (8-20) because of the high degree of uncertainty.

Question 5

Devops

Answer 5

A set of practices, tools, and cultural philosophy that automate and integrate the process between software development and IT teams. It emphasizes team empowerment, cross-team communication and collaboration, and technology automation.

Question 6

Root Cause Analysis

Answer 6

A methodology use for analyzing problems in order to identify the main reason for that problem

EX: When a problem arises, you must ask your team members questions that will allow for exploration to resolve the problem

Question 7

MVP

Answer 7

Minimum Viable Product - features in a software that are smallest and most important/ the smallest thing you can build that delivers customer value

EX: The MVP designation is used to determine the most important features that are needed in software build

Question 8

Scope Creep

Answer 8

When extra work is being inserted that wasn’t initially planned

Question 9

Project

Answer 9

Temporary venture with a beginning and end conducted by people to meet established goals within the parameters of cost/schedule and quality

Unique in that is not a routine operation, but a specific set of operations designed to accomplish a singular goal

Found in many fields and industries; has a being and end date

Question 10

Quality Assurance

Answer 10

A systematic process that ensures product and service excellence

Question 11

Cycle Time

Answer 11

A measure of the elapsed time when work starts on an item (story, task, bug, etc) until its ready for delivery

Cycle time tells how long(in calendar time) t takes to complete a task

Question 12

Bug/Defect

Answer 12

An error or a flaw that requires a fix. It can be a code change, a documentation update, configuration change, etc.

Question 13

Cloud Environment

Answer 13

The delivery of different services through the internet

These resources include tools and applications like date storage, servers, databases, networking, and software

Question 14

UI/UX

Answer 14

User Interface(UI) -The series of screens, pages, and visual elements like buttons and icon that enable a person to interact with a product or service

User Experience(UX) - internal experience that a person has as they interact with every aspect of a company’s products and services

Question 15

Agile

Answer 15

Project methodology that is best used in projects that have uncertain requirements.

Agile solves the uncertainty of how something should be done, by taking an incremental approach to solving a problem.

Question 16

User Story

Answer 16

An informal, general explanation of a software feature written from the perspective of the end user

Each user story should be short, concise clear, and testable

As a user, I want, so that..

Question 17

Release

Answer 17

A bunch of code that has been put together to release out to the end user to ensure they have the latest code. This happens with the iterations by producing increments of the final product

Question 18

Epic

Answer 18

A body of work that can be broken down into specific tasks (called user stories) based on the needs/requests of customers or end-users

Epics usually represent a significant deliverable such as a new feature or experience on the software your team develops

Question 19

Scrum

Answer 19

A lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems

Best used on software development projects

Question 20

Backlog

Answer 20

Prioritized list of work for the development team that is derives from the roadmap and its requirements.

The most important items are shown at the top of the P.B so the team knows that to deliver first.

Question 20

Capacity

Answer 20

The number of hours a team/team members can dedicate to the work needing to be done

This allows you to know how much work your team can take on for the sprint

Question 21

Burndown Chart

Answer 21

Used to measure progress; shows the amount of work that has been completed in a sprint and the total work remaining.

Or shows total effort against the amount of work for each iteration.

Question 22

Timebox

Answer 22

Maximum duration of an event

Question 23

Sprint

Answer 23

A short, timeboxed period when a scrum team works to complete a set amount of work

Question 24

Requirement

Answer 24

Is a description of the service that the software must offer.

It describes a software system or its components.

Usually created by business owners, business analysts, POS, and technical architects. Used to solidify the business/technical need that needs to be developed

Question 25

Release/Build

Answer 25

Latest version of software or update OR
Deployable software package that is a culmination of several iterations

Question 26

Dashboards

Answer 26

Graphical representation on how you can manipulate data in JIRA

Question 27

Velocity

Answer 27

Measure of how much time it takes for the team to do work

Question 28

Dependencies

Answer 28

The relationships between work that determine the order in which the work items (features, stories, tasks)

Some user stories may have a situation that causes the inability to complete work as expected

Question 29

Legacy

Answer 29

An application system source code type that is no longer supported or older systems or applications.

In most cases, legacy code is converted to a modern software language/platform to accommodate current technology trends.

Question 30

Feature

Answer 30

Describes a specific solution to a requirement and deliver against a single or multiple stories

Question 31

Enabler

Answer 31

A type of user story or technical items which support the development of business

Question 32

Technical Debt

Answer 32

Concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer

Question 33

UAT

Answer 33

User Acceptance Testing(UAT) the last phase of software testing process that verifies whether the product or software is fit for the purpose it was built for in the first place;

Question 34

Burnup Chart

Answer 34

tool that’s used to track the amount of work that’s been completed and to represent the total amount of work that needs to be done for a sprint/project.