...

• Brian Lance blance@uci.edu, DUE Data & Development
• Mel Layos mlayos@uci.edu, UC Recruit Application Support
• Erik Kelly erkelly@uci.edu, Academic Web Technologies
• Victor Pham phamvd@uci.edu, Chancellor & Provost IT

Benefits of Scrum

With each project stakeholder seeing a different aspect of scrum, there's usually a variety of reasons for using Scrum. The following are benefits OIT Scrum teams have observed from using Scrum:

• Customers:
  • Transparency & trust: regularly see evidence of project progress at demos, standups, etc...
  • Effectiveness: team focuses on delivering the highest value functionality first
• Team:
  • Empowerment: teams decide how to deliver potentially shippable increments, increasing ownership
  • Efficiency: teams organize and manage their own work, leading to improvements in efficiency and effectiveness
• Operations:
  • Collaboration: developers and operations partner to improve reliability, security, and ...
  • Speed: Releasing every two weeks (or more frequently) encourages automation, version control, and configuration management
• Leadership:
  • Customer-centric: teams collaborate with customers and routinely ask for their feedback, leading to improved results
  • Innovative: self-organization promotes a more innovative and creative environment
  • Staff engagement: team buy-in and shared ownership are essential to employee satisfaction and engagement
  • Cross-training: peer reviews, collaborative planning, pairing, etc... spreads knowledge throughout the team, reducing the bus factor

What is Scrum?

Scrum is an agile way to manage a project. Instead of planning everything up front, Scrum teams plan and deliver a product iteratively. Scrum iterations are called "sprints" and typically last 2 weeks (some teams standardize on 3 or 4 weeks).

...

• Product Backlog: prioritized list of everything that might be needed in the product
• Sprint Backlog: the set of the Product Backlog items selected for a Sprint. Teams use index cards, Trello, or other tools to track progress
• Burn-downs, burn-ups, or cumulative flows: used by some teams to track progress towards the goal

Why Scrum?

...

Benefits of Scrum

Each stakeholder often sees a different reason to use Scrum. The following are benefits OIT Scrum teams have observed from using Scrum:

• Customers:
  • Transparency & trust: regularly see evidence of project progress at demos, standups, etc...
  • Effectiveness: team focuses on delivering the highest value functionality first
• Team:
  • Empowerment: teams decide how to deliver potentially shippable increments, increasing ownership
  • Efficiency: teams organize and manage their own work, leading to improvements in efficiency and effectiveness
• Operations:
  • Collaboration: developers and operations partner to improve reliability, security, and speed
  • Speed: Releasing every two weeks (or more frequently) encourages automation, version control, and configuration management
• Leadership:
  • Customer-centric: teams collaborate with customers and routinely ask for their feedback, leading to improved results
  • Innovative: self-organization can promote a more innovative and creative environment
  • Staff engagement: team buy-in and shared ownership are essential to employee satisfaction and engagement
  • Cross-training: peer reviews, collaborative planning, pairing, etc... spreads knowledge throughout the team, reducing the bus factor

Scrum Resources

Please consider adding resources that have been useful to you in adopting Scrum.

...