Object Oriented Principles
SCRUM
Usability / Beyond SCRUM
Git
Unit Testing
100

This OO principle states that the object performing some action should be the one with the most amount of information needed to perform said action.

What is Information Expert?

100

This is when engineers vote on "points" to give a story, which determine the level of effort for that task.

What is Planning Poker?

100

This is a measurement of how easy and straight forward an application is to use.

What is simplicity?

100

This is where all the code is stored on Github.

What is a repository?
100

This is the annotation that must go above every function that tests something.

What is @Test

200

This OO principle assigns responsibility to receive and coordinate a system operation to a class outside of the UI tier, thus ensuring separation between the UI tier and the other system tiers.

What is a controller?

200

This is a meeting between the end of a Sprint between engineers that determines what went well, what went wrong, and what to change for future sprints.

What is the Sprint Retrospective?
200

This is a measurement of how often similar elements are in the same place.

What is consistency?
200

This is a git feature where users can deviate off of main's code, and begin working in their own space independent from main. Developers make one for each story.

What is a branch?

200

This is a percentage of how much of your code is checked by unit tests.

What is code coverage?

300

This OO principal refers to how connected two objects are, and therefore how much each module relies on others.

What is Coupling?

300

This is the stage a story is in on the Trello board when the story will be worked on in this sprint, but development hasn't been started yet.

What is the Sprint Backlog?

300

This is a measurement of how open the application is to a wide array of users.

What is accessibility?

300

This is created by a developer when they want their branch to be merged with main.

What is a pull request?
300

This is a model that shows how entities interact with each other in your problem statement without using any references to code.

What is a domain model?

400

This OO principle states that modules should only talk to their immediate friends, and never talk to "friends of friends."

What is the Law of Demeter?

400
This is an estimated number of story points that the team can take on in one Sprint.

What is Velocity?

400

This is a project management model where specialized tasks completed in one phase need to be reviewed and verified before continuing.

What is the Waterfall model?

400

This is done on pull requests, where other developers leave feedback on the engineers code and determine whether it can be merged or not.

What is a code review?

400

This is an illustration of how classes interact with each other, and what classes has what functionality.

What is a UML diagram?

500

This OO principle states that high-level modules should not depend on low-level modules. Both should depend on abstractions.

What is dependency inversion?

500

This is a meeting where the development team looks at each story, defined acceptance criteria, and estimates each story point.

What is "backlog refinement"

500

This is the name of a Agile system that's similar to SCRUM however Sprints are not used. Instead, developers pick off any story from the backlog.

What is Kanban?

500

This is the act of merging changes made to main with your current working branch.

What is back-merge?

500

This is a visual of one specific functionality in your program. (Usually a story).

What is a sequence diagram?

M
e
n
u