DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Scrum Myth: You Can Only Release the Product at the End of the Sprint

Scrum Myth: You Can Only Release the Product at the End of the Sprint

Sure, you can have multiple releases in a Sprint — you just need to think about how Scrum enables you to achieve delivery instead of what a process stops you from doing.

Alasdair Macleod user avatar by
Alasdair Macleod
·
Feb. 04, 17 · Opinion
Like (2)
Save
Tweet
Share
4.16K Views

Join the DZone community and get the full member experience.

Join For Free

One of the recurring Scrum Myth discussions I have with colleagues, teams new to Scrum and those attending training when comparing Scrum and DevOps relates to a misinterpretation of the following paragraph from the Scrum Guide.

At the end of a Sprint, the new Increment must be “Done,” which means it must be in useable condition and meet the Scrum Team’s definition of “Done.” It must be in useable condition regardless of whether the Product Owner decides to actually release it. —  Scrum Guide

The discussions tend to start from the basis that Scrum prevents a Scrum Team from releasing more regularly than at the end of the Sprint and is slower than DevOps at getting releases into the market and users hands for feedback.

I generally suggest that they re-read the statement and look to see if they can find any part or sentence in it that explicitly says that a Scrum Team may only release at the end of the Sprint. I see this as being the minimum state in the "what" that the Scrum Framework describes the Increment must be in at the end of the Sprint. Like any other minimum, if you can get to that point earlier, then you should if possible take advantage of the early delivery.

When people come either to community discussions or training on more advanced uses of Scrum, they realize that the same techniques of Continuous Integration, Continuous Delivery, and Continuous Deployment are all recommended complementary practices in Scrum implementations in order to be successful. A follow-up question relates to where the increment should be deployed to by the end of the Sprint. This can be defined in a Scrum Team's Definition of Done taking account of at what point on the particular platform are all tests run that mean the increment is in a potentially usable and releasable state.

I personally work with many teams that deploy fully tested and integrated code to live multiple times within a day using Scrum to deliver robust, scalable Enterprise Applications with millions of users per month.

So, using Scrum, can you have multiple releases in a Sprint? Sure, you can — you just need to think about how Scrum enables you to achieve delivery instead of what a process stops you from doing.

scrum Sprint (software development) Release (agency)

Published at DZone with permission of Alasdair Macleod, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • The Role of Data Governance in Data Strategy: Part II
  • How to Develop a Portrait Retouching Function
  • Public Cloud-to-Cloud Repatriation Trend
  • 2023 Software Testing Trends: A Look Ahead at the Industry's Future

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: