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).
 

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)" 130.195.253.6 (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)

Scrum Master Role[edit]

I would like to suggest some modifications to the Scrum Master role...some of the statements that are currently included in this definition represent an opinion that is not necessarily true in all circumstances. Here are my suggested changes:

The statement "In fact, there is no role of project manager in Scrum at all, because none is needed." is not necessarily true in all situations and represents someone's opinion. This statement is NORMALLY true at the team level in Scrum but Scrum is intended to be used as a general framework in many different situations and there are certainly some situations where there might be a need for a project manager. For example, there are many situations where Scrum might be used in large, complex enterprise-level projects that might require some level of project management. I have personally used Scrum as a framework for a government contracting project consisting of three Scrum teams and there certainly was a need for a project manager in that situation. I suggest deleting this statement.

I suggest deleting the last sentence in this section "Practicing Scrum with the addition of a project manager indicates a fundamental misunderstanding of Scrum, and typically results in conflicting responsibilities, unclear authority, and sub-optimal results" for the same reason.

Scrum is intended to be a general framework and the spirit behind it is to take an adaptive approach to adapt the process to each particular process as necessary. I think these two statements that imply that it is NEVER appropriate to use a project manager in a Scrum project are overly prescriptive and not consistent with that spirit. — Preceding unsigned comment added by Chuckcobb3 (talkcontribs) 14:28, 4 October 2014 (UTC)

I deleted many of these sentences because they violated copyright. This deletion also had the side effect of toning down the emphasis that the above commenter was worried about. --Officiallyover (talk) 01:59, 28 October 2014 (UTC)
I also found the diff. I or others very much ought to check other contributions around that time for direct quotes that aren't identified as such. --Officiallyover (talk) 02:15, 28 October 2014 (UTC)