Forums

By posting to our forums you are agreeing to the Forum terms of use.
While under development the environment in which a product will be used changed
Last Post 22 Jul 2013 11:06 AM by Mark. 4 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Resolved
Mark
New Member
New Member
Posts:8
Mark

--
22 Jul 2013 08:30 AM
    Please help me with the following question:

    While under development the environment in which a product will be used changed. What is the effect on the product backlog?

    A: a. It is archived and a new Product Backlog is created to take its place.
    B: There is no effect, because it has to stay the same until the end of the project.
    C: It evolves to reflect what the product needs to be most valuable
    D: It is converted into a requirements specification to ensure stability

    I would tend to C or D.
    Philipp Eisbacher
    New Member
    New Member
    Posts:32
    Philipp Eisbacher

    --
    22 Jul 2013 08:56 AM
    Hello Mark.

    To clarify, what do you mean with "requirements specification" and where do you see the difference to a product backlog? Where do you see benefits in evolving or in in converting? And what leads you to your tend?

    BR,
    Philipp
    randyh
    New Member
    New Member
    Posts:35
    randyh

    --
    22 Jul 2013 10:42 AM
    Perhaps this thread will be helpful to you:

    https://www.scrum.org/Forums/aft/383
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:562
    Ian Mitchell

    --
    22 Jul 2013 10:46 AM
    By a process of elimination:

    - It can't be A, because that answer is wrong. You don't archive a Product Backlog because of a change in a product environment
    - It probably isn't B, because that answer implies that a Product Backlog stays unchanged until the end of a project, which is incorrect

    That leaves C or D, as Mark suggests.

    D is a poor answer for at least two reasons. Firstly Scrum does not prescribe the format of a Product Backlog, other than to say each item has a description, size, and order. The notion of converting it to a "requirements specification" is therefore meaningless. Secondly, there is nothing to indicate that the "requirements specification" alluded to will be more stable.

    That leaves C as the best answer, since it is true that a Product Backlog should evolve to reflect the greatest possible product value.
    Mark
    New Member
    New Member
    Posts:8
    Mark

    --
    22 Jul 2013 11:06 AM
    Thank you very much for your answers. This helped me much.

    Greetings,
    Mark
    You are not authorized to post a reply.


    Feedback