Vocabulary R

Question 0

The reorganization of working code to bring the organization in line with its functionality and make it more maintainable. We factoring should not have noticeable effects on functionality or performance.

Answer 0

Re-factoring

Question 1

Estimating the size of functionality or user story based on the size of another one. This exercise of ordering a group of user stories from most difficult to lease difficult without actually estimating duration is an example of this concept what is it?

Answer 1

Relative sizing

Question 2

A packaged group of iteration outcomes designed to be delivered to end user and customers. The working software delivered in each of these is expected to be highly stable. What is this package group of outcomes called?

Answer 2

Release

Question 3

The percentage that shows what return an organization makes by investing in something is called what?

Answer 3

Return on Investment ROI

Question 4

A chart where the risk of project success associated with each feature is displayed. The project risk will lessen as the project progresses and functionality is completed what type of chart is this?

Answer 4

Risk Burn Down Chart

Question 5

The way in which an individual interfaces with an agile project. What are these examples of this may include customer, product owner, stakeholder, sponsor, team member, tester, tracker, ScrumMaster, and coach?

Answer 5

Role

Question 6

A chart also called Ishikawa diagram or Fishbone diagram and a cause-and-effect diagram. What is this type of diagram? It is used to illustrate how different factors might relate together and identify the root of a problem.

Answer 6

Root Cause Diagram

Question 7

A technique designed to look beneath the symptoms of a problem to understand the fundamental problem that causes it. This type of analysis is sometimes aided by root cause diagrams and by the five whys technique. What type of analysis is this?

Answer 7

Root Cause Analysis