Back to Forum

Scrum Theory

Last post 07:01 am September 28, 2015 by Gregor Lorenz
1 reply
Arvind H V
02:57 am September 24, 2015

Hi All,

Can anyone help me in understanding the below points with an example or an scenario.

What do you mean by -

1. Scrum makes clear the relative efficacy of your product management and development practices so that you can improve.

2. Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is been seen.

3. Inspections are most beneficial when diligently performed by skilled inspectors at the point of work.

4. If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted.

Gregor Lorenz
07:01 am September 28, 2015

(1) is about the effectiveness of scrum and the constant validation of success (e.g. value delivered). Detecting flaws is essentially the same as identifying needs for improvement wrt. product management and/or development practices.

Examples:
- PO verifying the increments,
- the feedback gathered during sprint reviews
- the feedback of the users/market (frequent release)
- burn-up charts that measure the increase of delivered value, ...

(2) is basically saying that all participants must share the same standards (quality and procedureal mindset) in order to ensure that all provided information is transparent at all times, everybody agrees to the way it is measured and presented and knows how to interpret it. Transparency is worth nothing if some want to see other information or don't know how to make sense of the provided information.

Example:
- Product Backlog and prioritization is transparent at all times
- definition of "done"
- showing prgoress as burn-down and/or burn-up charts

(3) Inspect as you go - at the place of work and done by skilled people. Skill is a necessitiy. The best skills are usually found at the place of work. What this sentence is trying to say is: "Build quality right from the start at the place of work, rather than employing inspectors that check final deliveries.": Detecting flaws early at the place of work is also more economic than detecitng (and fixing) them late.

Example:
- Pair programming.where two developers are constantly providing peer reviews

(4) Scrum has zero tolerance for ignoring bad quality in processes and or the product. When detected, this needs to be fixed.

Examples:
- add defects to product backlog. Better fix them immediately if it fits in the sprint.
- discuss procedural problems in Sprint Retrospective - then solve them.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.