Question: Question 14: Why is it important to evaluate and prioritize high-risk features (tricky bits) during early iterations in the Construction phase? High-risk features also have
Question 14:
Why is it important to evaluate and prioritize high-risk features ("tricky bits") during early iterations in the Construction phase?
High-risk features also have high value to stakeholders
High-risk features are the responsibility of the architecture team
It's important to prove that the architecture can support nonfunctional requirements such as performance and stability
High-risk features take the most time to address and should be handled early in the project
You can always wait until later to deal with high value features
Question 15;
Which of the following practices help ensure a smooth transition to the operations and maintenance team?
Making sure that the operations and maintenance team are included in sprint reviews
Continuous documentation
Deployment testing in a production-like environment
All of these answers are correct
Training the operations staff
Question 16:
The release burndown chart indicates that it will take 5 more two-week sprints to finish the project, assuming no change in the team's productivity. This means the project will end later than the release date previously announced to stakeholders. What is the best option for the product owner?
Send an announcement to stakeholders informing them of the delay
Negotiate with customers to accept lower-quality work
Reduce the scope by moving low-priority user stories to the next release with the approval of key stakeholders
Reduce the sprint length to one week
Increase the work schedule by using overtime and weekends
Question 17:
After a demonstration at a sprint review a key stakeholder realizes that they don't want a feature that's already been coded and tested. What's the best option for the team?
The feature has already been integrated into the build, so there's no reason to remove it
Add a task "remove this feature" to the product backlog
Immediately remove the feature in the next sprint
Ask the product owner to persuade the stakeholder to keep the feature
Ask the development team to evaluate the risk of keeping the feature
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
