After releasing its beta version of a travel assistance mobile application, a travel company has received feedback from a public survey proposing new features.
The company is struggling with the large number of ideas and would like to make a decision on which to consider in the next implementation cycle.
Which of the following considerations should be used first for filtering ideas?
When deciding which new features to implement, the first consideration should be the alignment with the solution scope. Ensuring that the proposed features align with the overall goals and purpose of the mobile application is crucial. Features that do not align with the solution scope should be eliminated or the future state re-evaluated, as they might not contribute to the desired outcomes. This alignment ensures that the development efforts are focused on delivering value to users and achieving the business objectives.
C. Alignment with solution scope
Ans C 7.3.4.3 A requirement can be of benefit to a stakeholder and still not be a desirable part of a solution. A requirement that does not deliver benefit to a stakeholder is a strong candidate for elimination. When requirements do not align, either the future state must be re-evaluated and the solution scope changed, or the requirement removed from the solution scope. If a design cannot be validated to support a requirement, there might be a missing or misunderstood requirement, or the design must change.
ANS is C BABOK V-3 3.4.6 pg 146 Evaluate Alignment with Solution Scope - A requirement can be of benefit to a stakeholder and still not be a desirable part of a solution. A requirement that does not deliver benefit to a stakeholder is a strong candidate for elimination. When requirements do not align, either the future state must be re-evaluated and the solution scope changed, or the requirement removed from the solution scope. If a design cannot be validated to support a requirement, there might be a missing or misunderstood requirement, or the design must change.
C. Alignment with solution scope A requirement can be of benefit to a stakeholder and still not be a desirable part of a solution. A requirement that does not deliver benefit to a stakeholder is a strong candidate for elimination. When requirements do not align, either the future state must be re-evaluated and the solution scope changed, or the requirement removed from the solution scope
It is A. This is solution evaluation. It is in beta stage, meaning a form.ofnthe solution exists and is being evaluated using survey. First filter will be highest customer satisfaction.
C. ensures that the selected features align with the overall purpose and goals of the mobile application, increasing the likelihood of delivering value to users and achieving business objectives.
keyword is 'beta version', the project is not officially delivered yet. need to consider solution scope prior to delivering additional features to increase client satisfaction.
I'll go with A. Typical factors that influence prioritization include: • Benefit: the advantage that accrues to stakeholders as a result of requirement implementation, as measured against the goals and objectives for the change. The benefit provided can refer to specific functionality, desired quality, or strategic goal or business objective.
A is correct : Benefits of a non-financial nature (such as improved staff morale, increased flexibility to respond to change, improved customer satisfaction, or reduced exposure to risk) are also important and add significant value to the organization.