Talk:Scrum (software development)

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Software (Rated C-class, Mid-importance)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
C-Class article C  This article has been rated as C-Class on the project's quality scale.
 Mid  This article has been rated as Mid-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Software (marked as High-importance).

Product Backlog Items Aren't Needs[edit]

The section on the Product Backlog refers to backlog items as "requirements" and says a minimum viable product "needs" (all of) them. This is an overstatement; at most, every item in the backlog is thought to have some value to some customer or stakeholder. It is quite common for a product to be successful at the same time that items in the backlog either remain unimplemented or are dropped from the backlog altogether.

Would anyone like to take a crack at rewording the paragraph? (talk) 19:29, 6 March 2014 (UTC)

merge SCRUM in Marketing Department into this article[edit]

Absolutely. SCRUM in Marketing Department is poorly written, doesn't follow MoS. At the very least it should be cleaned-up. Walter Görlitz (talk) 05:40, 17 May 2014 (UTC)

Merge "SCRUM in Marketing Department" into "Scrum (software development)"? At the very least they should both be merged into something like "Scrum (development process)" (talk) 03:38, 4 June 2014 (UTC)
Support - Was just going to AfD the other one when I saw the merge proposal. If you feel like something from that completely unsourced yet text-heavy article can be salvaged to move over here (or, as above, an alternative combined name), more power to you :) --— Rhododendrites talk |  01:13, 5 June 2014 (UTC)

Product Owner representing stakeholders[edit]

On 18 May, user Mvaraujo edited the description of Product Owner to counter the assertion that "the Product Owner represents the stakeholders and is the voice of the customer" with "(note: this shall be incorrect as stakeholder is anyone with action in the project)", citing the Wikipedia entry for Stakeholder (corporate) to support this assertion.

In fact, that Wikipedia entry states that a stakeholder is any "person or organization that has a legitimate interest in a project", not action as they mentioned.

The prime source of reference for anything to do with Scrum should be the Scrum Guide, published by the founders of Scrum (Ken Schwaber and Jeff Sutherland). In this guide, the Product Owner is described thus (my emphasis):

"The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes:
  • Clearly expressing Product Backlog items;
  • Ordering the items in the Product Backlog to best achieve goals and missions;
  • Optimizing the value of the work the Development Team performs;
  • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
  • Ensuring the Development Team understands items in the Product Backlog to the level needed.
The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.
The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner.
For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner’s decisions are visible in the content and ordering of the Product Backlog. No one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn’t allowed to act on what anyone else says."

Under this definition, we can clearly see that the intention is that the Product Owner is meant to be the single point of contact between the development team and the rest of the organisation, and hence represent all stakeholders. Davidjcmorris  Talk  23:22, 17 May 2014 (UTC)