XP | Quizerry

XP >> Agile Software Development

*Please Do Not Click On The Options.

* If You Click Mistakenly Then Please Refresh The Page To Get The Right Answers.

1 point

Write a test
Make sure the test fails
Write enough code so the test passes
Refactor as necessary

Write code
Write a test
Make the test pass
Refactor as necessary

Write code
Refactor as necessary
Write a test
Make the test pass

Design
Write code
Write a test

1 point

Peer Programming

Pair Programming

Buddy Programming

Twin Programming

1 point

All the skills necessary to deliver the software product should be present on the team.

The whole team should be energized and passionate about the product they are building.

The whole team should always sit together in a room.

The whole team should be working together to meet the team’s commitment

1 point

No action required; keep the story with no estimates.

Skip that story and exclude that story from the release.

Create a spike story—a new story under which the team will do some research or other work to gain a better understanding of the original story.

Provide their best guess based on what they know.

1 point

As a team, update the acceptance test so the test passes.

Create a bug report so it can be fixed.

Release the software without fixing; a few bugs are ok.

Extend the iteration’s duration so the bug(s) can be fixed in the same iteration.

1 point

Breaking stories into smaller tasks.

Reviewing the previous week’s progress.

Selecting the next week’s work.

Planning who is going to facilitate meetings for the rest of the week

1 point

The team members never change. Once a team member is part of the team, that team member always remain part of the team.

All of the skills the team needs to be successful should be in the team.

If the team finds out that they need a particular skill in the team, they can add a person with that skill to the team.

It is not recommended for a team member to be part of multiple teams.

1 point

Slow down the frequency of feedback.

Further increase the frequency and quantity of feedback.

Ignore the extra feedback.

Work extra hours each day to address all of the feedback.

1 point

No matter what you are building, just choose a simple design even if it only partially solves the problem.

Select the simplest design that could possibly work.

Generalize your solution so it can work for unanticipated future requests.

The software design for each component should fit on a single page.

XP >> Agile Software Development

XP

Related Questions & Answers:

Leave a Comment Cancel reply