Question

Help me with these questions, please.

1. The Pareto principle is seen in many project management methodologies. Why is it important in determining cause and effect?

Select one:

a. 80% of all effort produces 20% of the result

b. 80% of all effort produces 20% of the result

c. 80% of problems are a result of 20% of the causes

d. 20% of problems are caused by 80% of the causes

2.

Feature Driven Development is an iteration or sprint 0, during which

Select one:

a. Initial project activities occur and a plan is created to prove direction

b. Confirmation management is used to identify features

c. Visual progress is decided on to keep everyone on track

d. Programmers / developers decide on the code to develop

3.  

Stories should be written in such a way as to minimize reliance on other items.

Choose...

Estimatable

Testable

Valuable

Sized Appropriately

Independent Negotiable

4. Capture the essence of desired functionality but leave room for adding details.

Choose...

Estimatable

Testable

Valuable

Sized Appropriately

Independent Negotiable

5. Good stories explain how important they are to the customer, the user, or to both.

Choose...

Estimatable

Testable

Valuable

Sized Appropriately

Independent Negotiable

6. Teams should be able to determine how large a story is.

Choose...

Estimatable

Testable

Valuable

Sized Appropriately

Independent Negotiable

7. Higher priority stories need to be smaller and more detailed than lower priority stories.

Choose...

Estimatable

Testable

Valuable

Sized Appropriately

Independent Negotiable

8. Stories either pass or fail and have good acceptance criteria.

Choose...

Estimatable

Testable

Valuable

Sized Appropriately

Independent Negotiable

Answer 1

1. The Pareto principle is seen in many project management methodologies. Why is it important in determining cause and effect?

Answer: c. 80% of problems are a result of 20% of the causes

2. Feature Driven Development is an iteration or sprint 0, during which

Answer: a. Initial project activities occur and a plan is created to prove direction

3. Stories should be written in such a way as to minimize reliance on other items.

Answer: Independent

4. Capture the essence of desired functionality but leave room for adding details.

Answer: Negotiable

5. Good stories explain how important they are to the customer, the user, or to both.

Answer: Valuable

6. Teams should be able to determine how large a story is.

Answer: Estimatable

7. Higher priority stories need to be smaller and more detailed than lower priority stories.

Answer: Sized Appropriately

8. Stories either pass or fail and have good acceptance criteria.

Answer: Testable