Waterfall
Scrum 1
Scrum 2
Misc
100
True or False: It is possible to speed up the time it takes for a baby (9 months) by adding people to the project.
False
100
This is the term for the meeting happens every day for the software development team.
What is the Daily Scrum
100
This is term for an item that appears in an agile board (describes a task).
Story
100
Does software age?
Yes!
200
Yes or No: According to Brook is it possible to measure software project in man-months?
No
200
These are the 3 questions that you answer in a daily scrum meeting
What did i do? What am i going to do? What is in my way?
200
This is the name of the meeting that you have at the end of a sprint.
Sprint Review
200
Give one of the many costs caused by software aging
1. software bloated, 2. more difficult to change, 3. customers switch products, 4. more bugs being introduced.
300
In the waterfall model, this is the name of the document that describes what the developers must build.
What is the Software Requirement Specification
300
This is the name for the part of the agile board that contains task that you want to do one day but are not currently scheduled to be worked on
product backlog
300
True or False? The Agile Manifesto was created in the 1980s?
False
300
This is the term for improving code that you've already written.
Refactoring
400
These are the 1st four stages in the waterfall model
Requirement Definition Design Implementation Testing
400
Which of these numbers is the ideal size for a scrum team? 2, 7, 12, 18
7
400
This is the name of the meeting that occurs at the end of sprint in which you discuss how the sprint went (people, relationships, processes) and how to make the sprints go better
Sprint Retrospective Meeting
400
This is the name of development technique where you write the test BEFORE you write the code.
Test Driven Development
500
What was the point of the no silver bullet article?
There's no silver bullet to making complex software easier to write. High-level programming languages have helped
500
What do you discuss at the Sprint Retrospective.
you discuss how the sprint went (people, relationships, processes) and how to make the sprints go better
500
One reason for code reviews is to catch mistakes. What's another season?
You learn a section of the code that you might not have been familiar with.
M
e
n
u