Skip to content

Latest commit

 

History

History
91 lines (63 loc) · 2.49 KB

Quiz.md

File metadata and controls

91 lines (63 loc) · 2.49 KB

Question 1

Advantages of Waterfall include...

  1. Flexibility
  2. Early validation
  3. Clear objectives
  4. Compliance with bureaucratic processes
Click to show the answer

3 & 4: Waterfall has little flexibility and validation happens at the end, but this provides clear objectives and makes it easy to comply with precise requirements known before the project starts.

Question 2

The "Scrum Master"...

  1. Decides who to assign to each task
  2. Communicates with customers
  3. Helps the team work smoothly
  4. Evaluates each team member
Click to show the answer

3: The role is only about facilitating teamwork, for instance by asking people if they are blocked, scheduling necessary meetings, and running standup meetings.

Question 3

In agile development, the product backlog...

  1. Includes user stories
  2. Includes bugs
  3. Is empty when the project is done
  4. Is empty when the project starts
Click to show the answer

1 & 2: The backlog includes both user stories and bugs, should contain at least some basic end-to-end user stories when the project starts, but may never be empty as customers suggest new stories that may never get done due to their low priority compared to other tasks.

Question 4

Which of the following are useful code review comments?

  1. "I think the user story you implemented is pointless."
  2. "Maybe this should be in a separate class?"
  3. "I don't think this works if the list is empty."
  4. "Is this needed because we support old browsers?"
Click to show the answer

2 & 3 & 4: Design comments, possible bugs, and clarification questions are all useful. So are positive comments, "This looks great!" helps with motivation if used sparingly. However, code reviews are not the time to discuss validation issues such as user stories.

Question 5

Which of the following make code review easier?

  1. One commit per 100 lines of code
  2. One commit for the entire code under review
  3. Copying user stories into commit messages
  4. Commented-out code for possible alternatives
Click to show the answer

None: Commits should reflect independent units of work, regardless of size, such as commits per refactoring and per bug fix. Copying information the reviewers already have into commit messages is not useful, and neither is including unnecessary code.