 

Home Study tools  My courses  My books My folder Career Life

home / study / engineering / computer science / computer science questions and answers / 1)... 

Find solutions for your homework

Question: 1) Using MoSCoW model prioritization, assume that
we have
an MH story that depends on an SH ...

1) Using MoSCoW model prioritization, assume that we have an MH

story that depends on an SH story.
Before doing hybrid release
planning, we should:

  

Set the MH story to SH, because of the need to align stories to

the same, lower priority.

   

Leave the priorities of the two stories unchanged, and instead

switch the agile release planning.

   

Switch to numerical rankings, because that will allow

unambiguous sorting of the stories.

   

Return the product backlog to the product owner to resolve the

discrepancy.

   

Promote the SH story to MH, because it is needed to deliver the

MH story.

2) With respect to prioritizing large numbers of user stories

using numerical rankings:

  

Numerical rankings have generally replaced the MoSCoW

prioritization model.

   

Numerical rankings are typically less precise than MoSCoW

prioritization.

   

The difference in value between two user stories adjacent in the

rankings may not be meaningful.

   

Numerical rankings of individual stories are most useful when

thinking in terms of multiple epics.

   

All of the above are true.

Expert Answer
 Anonymous
answered this

Hi dear,

1.) Promote the SH story to MH, because it is needed to deliver

the MH story.

MH story depends on SH story and in hybrid project management,

you take two (or more) different project
management methodologies
and create an entirely new method by combining them

2.) All of the above are true

Numerical rankings have generally replaced the MoSCoW

prioritization model.Numerical rankings are
typically less precise
than MoSCoW prioritization.The difference in value between two user
stories adjacent
in the rankings may not be meaningful.Numerical
rankings of individual stories are most useful when
thinking in
terms of multiple epics

0 Comments

Was this answer helpful? 0

0
Questions viewed by other students

In agile release planning, the product backlog is allocated:

Only for configuration projects.
To multiple
sprints, into a sprint-by-sprint plan that creates
an agile release plan.
Sprint-by-sprint, but only one
sprint at a time.
None of these are true.
See answer

Compared to a house construction project from an existing

blueprint, systems projects generally
involve:
Question 3 options:
A. Higher design risk and lower replication risk.
B. Lower design risk and
higher replication risk.
C. Higher design risk and higher replication risk.
D. Lower design risk and lower
replication risk.
E. It is not possible draw any such...
See answer

Show more 

COMPANY

LEGAL & POLICIES

CHEGG PRODUCTS AND SERVICES

CHEGG NETWORK

CUSTOMER SERVICE

© 2003-2022 Chegg Inc. All rights reserved.