SlideShare a Scribd company logo
Rapid agile release flow
   and the agile testing

          Shirly Ronen-Harel
                      Aug 2010
http://il.linkedin.com/pub/shirly-ronen-harel/0/653/249
                    shirly@agilesparks.com
• The following presentation will describe a
  short flow of daily uploads to production
  environment while the sum of those daily
  uploads results with a business and customer
  release, While The testing in this case is
  manual regression tests, no automation tests
  exists yet.
• This is an agile team solution for dealing
  with on going releases to production of
  PSP’s while at the same time not released to
  an end customer.
• This may fit companies working with internet
  products which PSP’s must be released on
  a short period of time basis and autometion
  regression tests having a low coverage of
  product functionality.
• Some of the rapid release flow may fit to
  an internal customer tools development or
  any product development.
• We are distinguishing between a daily upload
  of PSP (potentially shippable product) and
  a final release to customer use.
Production change request




     Business release




 Station- Customer release
The company holds three types of release :
1.   CR :Production change request of user stories group: Release from development to production
     environment:
•    This is a process that is managed on a day to day basis where potentially shippable products (PSP’s)
     are integrated into the code main trunk and uploaded into the production environment
•    It does not mean that they are released or open to users use yet
•    These small releases allow continues functional integration into the production environment without
     overload users or internal customers with new frequent changes.
•    Each production upload is managed as a production change request as a part of the change
     management process in the organization

1.   A business Release
•    Milestone (sometime periodical sets of milestones) where the product organization decides to issue a
     business release containing the PSP’s (potentially shippable product) that were uploaded to
     production so far.
•    From this point on , no new features will enter into the customer release..
•    Internal customer acceptance tests can begin .

1.     Station - Customer release
•      a frequent small release to customer , that has a name and a number , , which was developed for
     few iterations(1-3) and has a millstone and ETA for release to customer/users use.
•      It is usually part of a bigger version release.
•      This release is prepared for some time , including relevant marketing materials and training for users
     .
R – business release takes the entire CR’s so far uploaded to production and
 close them to a release not yet release to customer. Development and
 upload of CR continues but will be integrated to the next R.
 Customer related tests /pilot may begin at this stage.




CR – (user stories group) Agile development                S - Customer release:
team uploads PSP’s to production , sometimes               The product is release to customer including
on a daily basis. This process is managed as               documentations and all preparations the business
change request process of production change                needed to do in order to be able to prepare customer
control.                                                   for a quality release.


        Uploads of PSP to production demands the architecture ability to
        split between production and customer releases.
Release/CR/Stations




No customer releases (s) is allowed between stations (s).
There can be many CR’s released during the iteration (with a quality
definition of done)
Sometimes there are delays in delivery of business features to the R
milestone.
Once an agile team miss those R milestones ,with features to be
released , those features will be moved to the next R station.
User stories (US) Freeze



US freeze           US freeze          US freeze




                                                                Business release        Customer
                                                                                         release




No new user stories can enter (unless major exception is required) a Sprint/Iteration
after the planning session is set and team commits to sprint goals and
artifacts.
Code Freeze



   US freeze   US freeze                  US freeze




                   Code freeze is set
                   before any CR or PSP
Backlog user stories Freeze and code Freeze




          Top 3 (n) user stories freeze


According to team WIP Team should work on top n` user stories only.
                      ,
Other user stories , that are in the backlog ,are not yet coded . They
are Only elaborated and acceptance criteria are defined.
1   Working on top
        user stories

        Once a user story is
        developed (and done) , the
        team is allowed to pick up
        the next user story and code
2       it (obviously- including
        testing).
        The next in line user story ,
        ready with acceptance
        criteria is entering the list
        of top n worked user stories.
User Story Code Freeze
 Just before a user story is done, team freeze code , and
 regression tests starts(Manual tests).
User Stories Quality Tests


                             Each user story is
                             tested for its tasks,
                             its functionality and
                             with other user
                             stories for a group
                             regression tests, As
                             part of a mini
                             hardening tests
                             phase.
Release End Game Tests

US freeze          US freeze




                                             Business release   Business release




                               Freeze




Before business release (R) the team will perform the end game tests ,
packaging and final quality verifications.
R&R
      •Product manger is Responsible
      for the product plan.
      •PO : Product owner preparing
      release and sprint backlog.
      •Scrum team : ‘Development and
      testing’ is responsible for quality.
      •Code freeze is a mutual decision
      between Po and scrum team.
      •Upload to Staging environment is
      a mutual decision between PO,
      Release manager and scrum team.
      •Upload to production environment
      is a mutual decision between PO,
      product manager and Release
      manger .
      •Business release is a decision for
      product release to make.
The company mature agile operation performs this
flow in a days<->weeks time farms. and it works!

More Related Content

PDF
Shirly Ronen - User story testing activities
PDF
Shirly Ronen - Documenting an agile defect
PDF
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex Environments
PDF
Automate your way to agility
PDF
Agile Software Development in Practice - A Developer Perspective
PDF
Building Mobile (app) Masterpiece with Distributed Agile
PDF
Agile Software Development Process Practice in Thai Culture
PDF
Agile Testing Introduction
Shirly Ronen - User story testing activities
Shirly Ronen - Documenting an agile defect
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex Environments
Automate your way to agility
Agile Software Development in Practice - A Developer Perspective
Building Mobile (app) Masterpiece with Distributed Agile
Agile Software Development Process Practice in Thai Culture
Agile Testing Introduction

What's hot (17)

PDF
Continuous delivery @åf consult
PDF
How to organize qa process in agile speed
PDF
Why Test Driven Development?
PPTX
Agile testing for agile sparks kanban clients
PDF
Vaidyanathan Ramalingam Agile Testing Conference Speech
PDF
Vaidyanathan Ramalingam Trade Off Economics In Testing Conference Speech
PDF
PDF
Vaidyanathan Ramalingam Waterfall Vs Agile Testing Conference Speech
PDF
Vaidyanathan Ramalingam Testing Checklist Conference Speech
PDF
Vaidyanathan Ramalingam Software Testing Eco System Conference Speech
PDF
Vaidyanathan Ramalingam Silicon India Testing Conference 2 July2011 Speech
PDF
Vaidyanathan Ramalingam Agile Testing Leadership Lessons Softec 2 July2011
PDF
Vaidyanathan Ramalingam Rca In Agile Conference Speech
PDF
Vaidyanathan Ramalingam Rca In Testing Conference Speech
PDF
RFT - Ashish Mathur
PDF
Karate API Testing-Complete Guidance by Testrig
PDF
Test driven development
Continuous delivery @åf consult
How to organize qa process in agile speed
Why Test Driven Development?
Agile testing for agile sparks kanban clients
Vaidyanathan Ramalingam Agile Testing Conference Speech
Vaidyanathan Ramalingam Trade Off Economics In Testing Conference Speech
Vaidyanathan Ramalingam Waterfall Vs Agile Testing Conference Speech
Vaidyanathan Ramalingam Testing Checklist Conference Speech
Vaidyanathan Ramalingam Software Testing Eco System Conference Speech
Vaidyanathan Ramalingam Silicon India Testing Conference 2 July2011 Speech
Vaidyanathan Ramalingam Agile Testing Leadership Lessons Softec 2 July2011
Vaidyanathan Ramalingam Rca In Agile Conference Speech
Vaidyanathan Ramalingam Rca In Testing Conference Speech
RFT - Ashish Mathur
Karate API Testing-Complete Guidance by Testrig
Test driven development
Ad

Similar to Shirly Ronen - rapid release flow and agile testing-as (20)

PPT
Understand release engineering
PPTX
Automation Testing Project and Framework Details
PPTX
Scrum Process Overview
PPT
QA Challenges in an Agile World
PDF
Agile lifecycle handbook by bhawani nandan prasad
PPTX
Info dev flexibility in agile
PPTX
Continuous Build To Continuous Release - Experience
PPT
What Is Agile Scrum
PDF
Testing in an Open Source Middleware Platform Space The WSO2 Way.
PDF
Agile_basics
PDF
Software Process @ Fountain Park Ltd
PPTX
agiletesting-220223101844.pptx
PDF
Ralph Jocham, effective agile - Scaled Scrum at Swiss Postal Services | Agile...
PPTX
PPT
Adaptive Development Methodology
PPT
Agile scrum induction
PPS
Software Development Life Cycle Testingtypes
PPTX
Scrum implementation
PPTX
Agile process with a fixed cost
PPTX
MyPresentation2
Understand release engineering
Automation Testing Project and Framework Details
Scrum Process Overview
QA Challenges in an Agile World
Agile lifecycle handbook by bhawani nandan prasad
Info dev flexibility in agile
Continuous Build To Continuous Release - Experience
What Is Agile Scrum
Testing in an Open Source Middleware Platform Space The WSO2 Way.
Agile_basics
Software Process @ Fountain Park Ltd
agiletesting-220223101844.pptx
Ralph Jocham, effective agile - Scaled Scrum at Swiss Postal Services | Agile...
Adaptive Development Methodology
Agile scrum induction
Software Development Life Cycle Testingtypes
Scrum implementation
Agile process with a fixed cost
MyPresentation2
Ad

More from AgileSparks (20)

PPTX
What Do Agile Leaders Do by Kurt Bittner
PDF
Distributed Teams by Kevin Goldsmith
PPTX
A Back-End Approach to Customer Driven by Adi Gostynski
PPTX
Jira Portfolio by Elad Ben-Noam
PDF
Agile Hiring at Scale by Yon Bergman
PPTX
Are We Really Using Our Resources in The Most Effective Way? by Perry Yaqubo...
PPTX
Honest Experimentation by Jonathan Bertfield
PPTX
Pango Journey to an Agile Cloud by Yaniv Kalo
PPTX
ClickSoftware Agile Tranistion by Meny Duek
PPTX
Augury's Journey Towards CD by Assaf Mizrachi
PPTX
Kubernetes is Hard! Lessons Learned Taking Our Apps to Kubernetes by Eldad Assis
PPTX
Creating a Culture of Ownership and Trust with Visibility and Transparency by...
PPTX
Real Innovation is with Real Customers by Baat Enosh
PPTX
True Continuous Improvement with Toyota Kata by Jesper Boeg
PDF
Homo-Adaptus Agile Worker by Lior Frenkel
PPTX
Intel CHD Case Study by Ronen Ezra
PPTX
Leading Innovation by Jonathan Bertfield
PDF
Organization architecture autonomy and accountability
PDF
Tribal Unity, Agile Israel 2017
PDF
The mindful manager, Agile Israel 2017
What Do Agile Leaders Do by Kurt Bittner
Distributed Teams by Kevin Goldsmith
A Back-End Approach to Customer Driven by Adi Gostynski
Jira Portfolio by Elad Ben-Noam
Agile Hiring at Scale by Yon Bergman
Are We Really Using Our Resources in The Most Effective Way? by Perry Yaqubo...
Honest Experimentation by Jonathan Bertfield
Pango Journey to an Agile Cloud by Yaniv Kalo
ClickSoftware Agile Tranistion by Meny Duek
Augury's Journey Towards CD by Assaf Mizrachi
Kubernetes is Hard! Lessons Learned Taking Our Apps to Kubernetes by Eldad Assis
Creating a Culture of Ownership and Trust with Visibility and Transparency by...
Real Innovation is with Real Customers by Baat Enosh
True Continuous Improvement with Toyota Kata by Jesper Boeg
Homo-Adaptus Agile Worker by Lior Frenkel
Intel CHD Case Study by Ronen Ezra
Leading Innovation by Jonathan Bertfield
Organization architecture autonomy and accountability
Tribal Unity, Agile Israel 2017
The mindful manager, Agile Israel 2017

Recently uploaded (20)

PDF
solutions_manual_-_materials___processing_in_manufacturing__demargo_.pdf
PDF
Review of recent advances in non-invasive hemoglobin estimation
PDF
NewMind AI Weekly Chronicles - August'25 Week I
PDF
Unlocking AI with Model Context Protocol (MCP)
PDF
Advanced Soft Computing BINUS July 2025.pdf
PDF
Approach and Philosophy of On baking technology
PDF
Modernizing your data center with Dell and AMD
PDF
Chapter 3 Spatial Domain Image Processing.pdf
PPT
“AI and Expert System Decision Support & Business Intelligence Systems”
DOCX
The AUB Centre for AI in Media Proposal.docx
PDF
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
PDF
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
PDF
NewMind AI Monthly Chronicles - July 2025
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
PDF
Network Security Unit 5.pdf for BCA BBA.
PDF
GamePlan Trading System Review: Professional Trader's Honest Take
PDF
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
PPTX
breach-and-attack-simulation-cybersecurity-india-chennai-defenderrabbit-2025....
PDF
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
solutions_manual_-_materials___processing_in_manufacturing__demargo_.pdf
Review of recent advances in non-invasive hemoglobin estimation
NewMind AI Weekly Chronicles - August'25 Week I
Unlocking AI with Model Context Protocol (MCP)
Advanced Soft Computing BINUS July 2025.pdf
Approach and Philosophy of On baking technology
Modernizing your data center with Dell and AMD
Chapter 3 Spatial Domain Image Processing.pdf
“AI and Expert System Decision Support & Business Intelligence Systems”
The AUB Centre for AI in Media Proposal.docx
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
NewMind AI Monthly Chronicles - July 2025
The Rise and Fall of 3GPP – Time for a Sabbatical?
Network Security Unit 5.pdf for BCA BBA.
GamePlan Trading System Review: Professional Trader's Honest Take
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
breach-and-attack-simulation-cybersecurity-india-chennai-defenderrabbit-2025....
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
Reach Out and Touch Someone: Haptics and Empathic Computing

Shirly Ronen - rapid release flow and agile testing-as

  • 1. Rapid agile release flow and the agile testing Shirly Ronen-Harel Aug 2010 http://il.linkedin.com/pub/shirly-ronen-harel/0/653/249 shirly@agilesparks.com
  • 2. • The following presentation will describe a short flow of daily uploads to production environment while the sum of those daily uploads results with a business and customer release, While The testing in this case is manual regression tests, no automation tests exists yet. • This is an agile team solution for dealing with on going releases to production of PSP’s while at the same time not released to an end customer.
  • 3. • This may fit companies working with internet products which PSP’s must be released on a short period of time basis and autometion regression tests having a low coverage of product functionality. • Some of the rapid release flow may fit to an internal customer tools development or any product development. • We are distinguishing between a daily upload of PSP (potentially shippable product) and a final release to customer use.
  • 4. Production change request Business release Station- Customer release
  • 5. The company holds three types of release : 1. CR :Production change request of user stories group: Release from development to production environment: • This is a process that is managed on a day to day basis where potentially shippable products (PSP’s) are integrated into the code main trunk and uploaded into the production environment • It does not mean that they are released or open to users use yet • These small releases allow continues functional integration into the production environment without overload users or internal customers with new frequent changes. • Each production upload is managed as a production change request as a part of the change management process in the organization 1. A business Release • Milestone (sometime periodical sets of milestones) where the product organization decides to issue a business release containing the PSP’s (potentially shippable product) that were uploaded to production so far. • From this point on , no new features will enter into the customer release.. • Internal customer acceptance tests can begin . 1. Station - Customer release • a frequent small release to customer , that has a name and a number , , which was developed for few iterations(1-3) and has a millstone and ETA for release to customer/users use. • It is usually part of a bigger version release. • This release is prepared for some time , including relevant marketing materials and training for users .
  • 6. R – business release takes the entire CR’s so far uploaded to production and close them to a release not yet release to customer. Development and upload of CR continues but will be integrated to the next R. Customer related tests /pilot may begin at this stage. CR – (user stories group) Agile development S - Customer release: team uploads PSP’s to production , sometimes The product is release to customer including on a daily basis. This process is managed as documentations and all preparations the business change request process of production change needed to do in order to be able to prepare customer control. for a quality release. Uploads of PSP to production demands the architecture ability to split between production and customer releases.
  • 7. Release/CR/Stations No customer releases (s) is allowed between stations (s). There can be many CR’s released during the iteration (with a quality definition of done) Sometimes there are delays in delivery of business features to the R milestone. Once an agile team miss those R milestones ,with features to be released , those features will be moved to the next R station.
  • 8. User stories (US) Freeze US freeze US freeze US freeze Business release Customer release No new user stories can enter (unless major exception is required) a Sprint/Iteration after the planning session is set and team commits to sprint goals and artifacts.
  • 9. Code Freeze US freeze US freeze US freeze Code freeze is set before any CR or PSP
  • 10. Backlog user stories Freeze and code Freeze Top 3 (n) user stories freeze According to team WIP Team should work on top n` user stories only. , Other user stories , that are in the backlog ,are not yet coded . They are Only elaborated and acceptance criteria are defined.
  • 11. 1 Working on top user stories Once a user story is developed (and done) , the team is allowed to pick up the next user story and code 2 it (obviously- including testing). The next in line user story , ready with acceptance criteria is entering the list of top n worked user stories.
  • 12. User Story Code Freeze Just before a user story is done, team freeze code , and regression tests starts(Manual tests).
  • 13. User Stories Quality Tests Each user story is tested for its tasks, its functionality and with other user stories for a group regression tests, As part of a mini hardening tests phase.
  • 14. Release End Game Tests US freeze US freeze Business release Business release Freeze Before business release (R) the team will perform the end game tests , packaging and final quality verifications.
  • 15. R&R •Product manger is Responsible for the product plan. •PO : Product owner preparing release and sprint backlog. •Scrum team : ‘Development and testing’ is responsible for quality. •Code freeze is a mutual decision between Po and scrum team. •Upload to Staging environment is a mutual decision between PO, Release manager and scrum team. •Upload to production environment is a mutual decision between PO, product manager and Release manger . •Business release is a decision for product release to make.
  • 16. The company mature agile operation performs this flow in a days<->weeks time farms. and it works!