Monte Carlo Analysis.

Portfolio Management.

DelphiTechnique.

Progressive Elaboration.

Relative measure of the size of a user story.

Duration it takes to complete a user story.

Priority of the user story in the backlog.

Business value of the user story.

Attempt to resolve the problem directly and immediately during a Daily Scrum meeting.

Schedule a meeting with them after a Daily Scrum meeting to explore and resolve the issue.

Ignore the friction because a self-organizing team must sort out team conflict issues.

Ask for new resources to replace them before the friction undermines the team’s productivity.

Fast-Flexible-Flow

Optimize the Whole

Deliver Early and Often

Eliminate Waste

sponsor

team

project manager

methodology

Lines of code.

Function points

Story points.

Use-case points.

Review stories planned for the next sprint and provide estimates,

Demonstrate completed user stories to the Product Owner.

Discuss what went well, what didn't, and ways to improve.

Individually provide status updates on user stories in progress.

Right after iteration planning

Just before iteration planning

At the start of the next release

During the iteration review/demo

At the beginning of the iteration.

Every day.

In sequence.

Without documentation.

Customer at the start of the iteration.

Customer as late as possible during the iteration.

Tester after the team has finished the coding.

Development team at the start of the iteration.

the business requirements are vague or inadequate for an iteration.

a technology is understood well and has been used for a while, but needs a problem to be debugged.

there is insufficient time to refactor, but there is a need to resolve a specific problem.

a specific technicalQUESTION NO:needs to be answered, stopping work on the spike as soon as it answers that question.

Regression

Pareto

Qualitative

Monte Carlo

Work was removed from the Product Backlog.

Work was added to the Product Backlog.

The team's velocity increased.

The team's velocity decreased.

total number of Product Backlog hours completed in an iteration divided by the number of developers.

measured rate at which teams turn Product Backlog items into running, tested features.

measured rate at which the project manager turns the Product Backlog into tested features.

total number of Product Backlog hours completed when developers work in pairs.

Testing the daily increments of the software developed

Writing the stories and acceptance tests for each story

Planning and task allocation for the developer and tester

Interacting closely with users and representing the XP team

Task

Iteration

Product

Release

Earned value system.

Fully integrated backlog.

Cumulative flow diagram.

Progressive elaboration.

Testing, requirements, and adaptation

Testing, requirements, and change

Visibility, review, and testing

Visibility, inspection, and adaptation