Save
Upgrade to remove ads
Busy. Please wait.
Log in with Clever
or
show password
Forgot Password?
Don't have an account?  Sign up 
Sign up using Clever
or
Username is available taken
show password


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account. Your email address is only used to allow you to reset your password. See our Privacy Policy and Terms of Service.

Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.
focusNode
Didn't know it?
click below
 
Knew it?
click below
Don't Know
Remaining cards (0)
Know
0:00
edit
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how

LinearB Terminology

Engineering Metrics Key Terminology for Engineering Managers

TermDefinition
Cycle Time The total amount of time it takes for code to go from the first commit to production deployment. Cycle Time = Coding + Pickup + Review + Deployment Times
Coding Time Is tracked from when a Jira issue linked to a git branch is moved from "To Do" to "In Progress" to when a pull request is opened
Pickup Time The time it takes from when a PR is issued until the first review has started.
Review Time The time it takes to complete a code review and get a pull request merged.
Deployment Time The time it takes to release code to production
Pull Request Size The average code changes (in lines of code) of a pull request
Merge Frequency The number of PRs successfully merged by the team or the individual in all the repositories within the timeframe
Deploy Frequency The total number of deployments to production in a given period
MTTR (Mean Time to Restore) The average time it takes to recover from a production failure. LinearB measures MTTR as the time between: * The moment a production issue enters the In Progress state * The moment it exits the In Progress state
Change Failure Rate (CFR) CFR measures the percentage of deployments that result in a failure in production. LinearB calculates CFR based on the number of production incidents divided by the number of deployments over the same period.
Review Depth The total number of comments provided by a reviewer on a specific pull request (PR). This includes general comments, suggestions, or requests for changes.
Refactor Updates made to legacy code—that is, any code that hasn’t been modified in the past 21 days.
Rework Changes to recent code, defined as any code modified within the last 21 days. Rework is expected during the iterative development process—for example, when code is updated after peer reviews or internal testing
New Work Brand new code added to the codebase.
PR Maturity How refined and well-prepared a pull request (PR) is when it is submitted for review. How much work was required post-submission to address feedback, fix issues, or improve the PR.
Created by: L!fetouch
 



Voices

Use these flashcards to help memorize information. Look at the large card and try to recall what is on the other side. Then click the card to flip it. If you knew the answer, click the green Know box. Otherwise, click the red Don't know box.

When you've placed seven or more cards in the Don't know box, click "retry" to try those cards again.

If you've accidentally put the card in the wrong box, just click on the card to take it out of the box.

You can also use your keyboard to move the cards as follows:

If you are logged in to your account, this website will remember which cards you know and don't know so that they are in the same box the next time you log in.

When you need a break, try one of the other activities listed below the flashcards like Matching, Snowman, or Hungry Bug. Although it may feel like you're playing a game, your brain is still making more connections with the information to help you out.

To see how well you know the information, try the Quiz or Test activity.

Pass complete!
"Know" box contains:
Time elapsed:
Retries:
restart all cards