Gain insight into how Scrum helps organizations build valuable high-quality products predictably with manageable risk.
Please view "Implied Benefits of Scrum" on YouTube for a detailed presentation of these charts: https://youtu.be/f5NmysVDlwc
The video represents part 1 of a series entitled “The Value of Scrum”.
You can view the full playlist here: https://www.youtube.com/playlist?list=PL1nsXfZDpx3Su-7fk4Yfq7rorJpDSr-b0
3. Employees
Morale
Employee retention
Team ownership reduces
risk of individual ability
Commitment
Customer
Keep customers and
attract new business
Deliver features on time
Response to new or
changing requirements
Deliver what the customer
expects
Business
Fewer bugs increase
efficiency and improve
profit margin
Accurate Schedule
Predictions
Reduce the risk of failure
Minimize development
unused features
Quality
Predictability
Manageable
Risk
Value
6. • Significant improvements in Quality, Communication, product fitness and work-life balance
• The scrum master and development teams were successfully implementing the rules of scrum
• The product owners struggled to communicate vision, goals and priority to the teams
Findings
• Use of NPS by individual teams to compare progress to previous sprints and the average scores from all
teams
• Use NPS to examine larger trends within the company
• Use scores in individual categories to identify focus areas
• In this case, Product owner training and support was provided in order to address improve the indicated
issues
• Pinpoint areas that good scrum teams are doing as retrospective focus areas
Response
7. System test
defect count
The total number of
defects found
during system test
Provides an
indicator of code
quality delivered to
system test
Deferred defect
count
Number of known
defects designated
to fix in a future
release
Provides an
indicator of the
level of quality
experienced by the
customer
Daily Open
defect count
The number of
open defects on any
given day of the
release
Provides a curve
used to compare
progress between
releases
8. There was a correlation between high scores on the scrum survey and
Improvements in defect metrics, specifically in the following areas:
Delivering working
software at the end of each
sprint
Working within strict time
boxes
Management best practice
of Setting high level quality
goals for teams
Scrum had a net positive impact on all three categories:
Number of defects found
during system test
Total number of defects
deferred
Peak daily open defects
per cycle
9. Only three of the teams had NPS data
before and after scrum was implemented
Of those teams, all saw an improvement
NPS (+8, +14, +16)
Indicates increased customer satisfaction when using
Scrum
These charts were generated in support of my Youtube video entitled “Implied Benefits of Scrum”, which you can view at the link provided below:
https://youtu.be/f5NmysVDlwc
This video represents the first in a series that can be viewed on my Youtube channel entitled “Enduring Agile”:
Implied Benefits of Scrum: https://www.youtube.com/watch?v=f5Nmy
Scrum Case Studies: https://www.youtube.com/watch?v=tMBvg
Impacts of Multitasking in Scrum: https://www.youtube.com/watch?v=OPMIa
Relative Estimation in Scrum – The Value of Scrum Part 3b: https://youtu.be/Bkg7akbVap0
Agile Games in Scrum - https://youtu.be/aygjaWl3bnc
Regards,
James Walmsley
www.linkedin.com/in/jameswalmsleycsm
In their book published in 2012 entitled Software in 30 Days, Ken Schwaber and Jeff Sutherland recognized the ever-increasing need of organizations “to be able to create value by building, customizing and using software”.
For the customer, higher quality products improve overall satisfaction.
From the Business perspective, fewer bugs increase efficiency and improve profit margin.
And from the employee’s perspective, improved quality improves morale and job satisfaction.
The answer comes in two forms: Organic feedback and Metrics
- Organizations often depend on feedback from team members to understand if Scrum is working
- If a plan for measuring its effectiveness isn’t in place from the start, it is difficult to make a comparison between the state of the organization before Scrum was implemented as compared to the state resulting from the new approach.
Adobe published a case study in 2011 entitled “Measuring The Impact Of Scrum on Product Development at Adobe Systems”.
The paper identifies three measurement areas recommended for use in measuring Scrum’s impact:
Subjective Ratings, which were collected from Scrum Practitioners using a survey
Defect Data, representing software bug data collected from multiple defect tracking systems
Net Promotor Score, which is a point value provided indicating level of satisfaction
The subjective ratings resulting from the survey provided a few key findings which Adobe responded to with specific actions.
The next indicator providing an understanding of the impact of scrum is defect data.
The analysis of defect metrics resulted in two main findings