UNITED WAY STL ACADEMY
  • Courses
  • Log In
  • Join Free
  • Home
  • Courses
  • Scrum Essentials

Scrum for Business Agility

Curriculum

  • 5 Sections
  • 29 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • IT Management and Operations
    8
    • 1.1
      Big Data and Large-Scale Migration
      10 mins
    • 1.2
      Commercial-Off-the-Shelf (COTS) Implementations
      10 mins
    • 1.3
      Oracle Primavera Unifier
      10 mins
    • 1.4
      ServiceNow
      10 mins
    • 1.5
      Broadcom’s Clarity
      10 mins
    • 1.6
      DevOps and Beyond
      10 mins
    • 1.7
      Profit-and-Loss Potential
      10 mins
    • 1.8
      Innovation versus Stability
      10 mins
  • Portfolio Management
    8
    • 2.1
      Portfolio Management Challenges
      10 mins
    • 2.2
      De-scaling Scrum for Large Portfolios
      10 mins
    • 2.3
      A Vertical Slicing Overview
      10 mins
    • 2.4
      Scrum of Scrums
      10 mins
    • 2.5
      Large-Scale Scrum (LeSS)
      10 mins
    • 2.6
      Scrum@Scale
      10 mins
    • 2.7
      Nexus
      10 mins
    • 2.8
      Scaled Agile Framework (SAFe)
      10 mins
  • Human Resources and Finance
    3
    • 3.1
      Human Resources and Scrum
      10 mins
    • 3.2
      Creating the Right Culture
      10 mins
    • 3.3
      Finance
      10 mins
  • Business Development
    7
    • 4.1
      Marketing Evolution
      10 mins
    • 4.2
      Scrum for Marketing
      10 mins
    • 4.3
      Marketing Tools
      10 mins
    • 4.4
      Scrum in Action (Marketing)
      10 mins
    • 4.5
      The Gap Between Marketing and Sales
      10 mins
    • 4.6
      Scrum for Sales
      10 mins
    • 4.7
      Determining Roadmap to Value (Sales)
      10 mins
  • Customer Service
    3
    • 5.1
      Customers: The Most Crucial Stakeholders
      10 mins
    • 5.2
      Scrum and Customer Service
      10 mins
    • 5.3
      Scrum in Action in Customer Service
      10 mins

Innovation versus Stability

Scrum for Business Agility

Innovation versus Stability

🕐 12 min read
The Big Question

How can organizations successfully balance the need for innovation with the demand for stability in IT operations?

IT operations are the backbone of organizational stability, ensuring performance and uptime. Yet, the drive for innovation demands rapid and frequent change. This creates a fundamental tension: how do teams pursue creative solutions without compromising operational reliability?

💡 Did You Know?

DevOps originated as a movement to bridge the gap between software development and IT operations, aiming to improve collaboration and accelerate delivery cycles while maintaining stability.

Organizations rely on IT operations for stability, performance, and uptime, yet IT must always be innovating, which implies the need to change quickly and often. Stability and change conflict. This conflict is solved by tightening collaboration between operations and developers. Rather than developing new technology and throwing it over the fence for operations to support and vice versa, the operations side of the business builds sandboxes, or sets of standards within which developers can build.

Major tech companies like Netflix and Amazon use operational “sandboxes” to empower their development teams to innovate quickly, while still adhering to reliability standards that keep their services running smoothly for millions of users.

Every time developers make code changes in the innovation process, they can breathe easy, knowing those code changes are made within the set of standards agreed on between operations and development. Changes in database structures or designs within operational standards avert the risks inherent in the same changes made in development silos with little or no collaboration with operations.

Sandbox

A controlled environment or set of standards where developers can experiment and innovate without risking operational stability.

Practitioners often use a “definition of done” that incorporates operational standards, ensuring that every change aligns with reliability expectations.

These standards are incorporated into a team’s definition of done. IT can rest assured that within each sprint, the teams are staying in the sandbox for each requirement. When changes in the sandbox need to be made, development and operations consult and establish the new boundaries.

Definition of Done

A shared agreement among teams about the criteria that must be met before a user story or task is considered complete, including operational standards.

How might defining clear operational standards improve the trust between development and operations teams?

The need for improved coordination is key, especially in software development, which is where DevOps comes in.

Want to go deeper? The science behind balancing innovation and stability

Studies in organizational psychology show that teams perform best when boundaries are clear but flexible. By establishing sandboxes, teams set safe limits for experimentation—allowing innovation while reducing risk. This approach is central to modern DevOps practices, which emphasize iterative improvement and shared responsibility.

What challenges might teams face when negotiating “sandbox” boundaries, and how can they resolve disagreements?

⏱ 5 minutes
Activity: Sandbox Boundary Mapping

Work with your team to identify and map out the current standards that define your “sandbox.”

  1. List all operational standards your development team must adhere to (e.g., security, uptime, data integrity).
  2. Discuss which standards could be updated for greater flexibility without sacrificing reliability.

How could sandboxes accelerate innovation while minimizing risk in your organization?

Reflect on a time when rapid innovation conflicted with operational stability in your work or studies. What steps could have improved the balance?

0 words Take your time — depth matters more than length
❌ Common Misconception

IT operations and software development are separate functions that must operate independently to avoid interference.

✅ The Reality

Close collaboration between IT operations and development is essential for balancing innovation and stability, preventing risky changes and ensuring reliable performance.

  • IT operations provide essential stability, but innovation requires frequent change.
  • Sandboxes and shared standards help teams innovate safely.
+50 XP

What is the primary purpose of “sandboxes” in IT operations?

Review the “Sandbox” and collaboration section above to find the answer.
Flashcard

What is a “sandbox” in the context of IT operations?

Tap to reveal
Answer

A set of standards or a controlled environment where developers can innovate safely, without risking operational stability.

Flashcard

What does “definition of done” mean in Scrum and IT operations?

Tap to reveal
Answer

A shared agreement on criteria that must be met for a task to be considered complete, including operational standards.

Flashcard

What conflict exists between innovation and stability in IT?

Tap to reveal
Answer

Rapid change required for innovation can threaten the stability, performance, and uptime that IT operations provide.

Key Takeaway

Collaboration and shared standards between IT operations and developers enable innovation without sacrificing stability.

Key Takeaway

Sandboxes provide the safe boundaries teams need to experiment and innovate, ensuring every change supports operational reliability.

Stability and change conflict. This conflict is solved by tightening collaboration between operations and developers.

SHIFT

The Shift

  • Innovation and stability aren’t mutually exclusive: sandboxes and standards bridge the gap.
  • Collaboration is key—teams must work together to define and adjust operational boundaries.
  • DevOps practices help organizations maintain reliability while accelerating innovation.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

Profit-and-Loss Potential
Prev
Portfolio Management Challenges
Next

© 2026 United Way STL Academy | Powered by Sejal Learning Systems.

Modal title

Main Content