In Agile risk management, a risk burndown chart is best used to:

• A.Illustrate the project risk profile and new and changing risks.
• B.Track progress on risk reduction of technical risks.
• C.Document the external risks that could impact the project.
• D.Qualitatively analyze the probability of a risk occurring.

Comment: *

Name: *

Email: *

Verification: *

The ScrumMaster and the Product Owner disagree on the value of a Product Backlog item. In order to resolve the disagreement, the first step the ScrumMaster should take is to ask:

• A.The Product Owner to clarify the requirement.
• B.The business owner to resolve the problem.
• C.The business analyst to research the product value.
• D.Another project manager how to resolve the problem.

Comment: *

Name: *

Email: *

Verification: *

Who creates the Sprint Goal?

• A.The entire Scrum Team
• B.The Development Team
• C.The Scrum Master
• D.The Product Owner

Comment: *

Name: *

Email: *

Verification: *

A development team for a small company experiences long delays between product completion and release for validation and testing. The company is concerned that this will impact its ability to compete in the marketplace.
What analysis should the team use to understand the issues?

• A.Risk management
• B.Variance and trend
• C.Kano model
• D.Fishbone diagram

Comment: *

Name: *

Email: *

Verification: *

The purpose of a project burndown chart is to:

• A.Identify and communicate upcoming milestones.
• B.Display the level of effort and resources utilized.
• C.Identify dependencies between sprints or iterations.
• D.Display the remaining work across time.

Comment: *

Name: *

Email: *

Verification: *