STRIVING FOR CONTINUOUS INTEGRATION AND DEPLOYMENT

Oct 10, 2017Download as pptx, pdf

1 like248 views

STRIVING FOR CONTINUOUS INTEGRATION AND DEPLOYMENT Continuous integration and deployment (CI/CD) empowers organizations to bring their solution in production fast and frequent. This interactive session will share the benefits of this concept and introduce eight conditions that need to be met in order to make CI/CD a success. After this brief introduction, we will make small groups and explore these conditions, exchange experiences and you will get an understanding what needs to be improved in your organization. Talk to your peers and learn where they stand. Of course each of the groups will share their learnings, so we all go home with an understanding of how you can benefit from CI/CD and what needs to be done to make it work.

STRIVING FOR CONTINUOUS
INTEGRATION AND DEPLOYMENT
1
Derk-Jan de Grood
[SC]2 – 4 October 2017

2
STRIVING FOR CONTINUOUS INTEGRATION AND
DEPLOYMENT
Continuous integration and deployment (CI/CD)
empowers organizations to bring their solution in
production fast and frequent. This interactive session
will share the benefits of this concept and introduce
eight conditions that need to be met in order to make
CI/CD a success. After this brief introduction, we will
make small groups and explore these conditions,
exchange experiences and you will get an
understanding what needs to be improved in your
organization. Talk to your peers and learn where they
stand. Of course each of the groups will share their
learnings, so we all go home with an understanding of
how you can benefit from CI/CD and what needs to be
done to make it work.

Continues Integration & Deployment
A brief introduction
4

Levels
5
Code &
commit
Integrate
& build
Test Deliver

Definitions
Continuous integration (CI) is the practice of merging all
developer working copies to a shared mainline several
times a day.
With continuous delivery (CD) teams produce software in
short cycles, ensuring that the software can be reliably
released at any time. It aims at building, testing, and
releasing software faster and more frequently.
Continuous deployment (CD) is the next step of
continuous delivery: Every change that passes the
automated tests is deployed to production automatically.
[Sources: Wikipedia and puppet.com]
6

Continuous Delivery Example
7
Local
• Code
• Unit Test
• Commit
Development
• Save Repo
• Get config
• Deploy
• Test
Test
• Save Repo
• Get config
• Deploy
• Test
Acceptance
• Save Repe
• Get config
• Deploy
• Test
1
Daily
• Nightly regression
test
• Monitoring
Daily
• Nightly
performance test
• Monitoring
Daily
• E2E test
• Monitoring

Advantages
• Efficiency
• Reduces amount of rework
• Predictability
• Reduced time to market
• Fast feedback
• Reducing risk
• Better quality solutions
8

CI/CD requires that (in random order)
1
Teams collaborate
with each other
Integration is
continuous
Deployment is a
hands-off process
Feedback loop to
improve quality
Features are
launched frequently
Acceptance criteria
are clear
Teams have all
required skills and
knowledge
Tests are
automated
Valori-version1.2-2017

CI/CD requires that (in random order)
1
Teams collaborate
with each other
Deployment is a
hands-off process
Feedback loop to
improve quality
Features are
launched frequently
Acceptance criteria
are clear
Teams have all
required skills and
knowledge
Tests are
automated
Valori-version1.2-2017
Architecture supports
partial development
and release

The process of building and deploying software can be tedious, difficult, and problem-prone. Even more challenging is building a continuous integration and delivery platform that can be flexible and adaptive to your agile software teams. Take a sneak peek into how Dude Solutions revamped and replaced their entire continuous integration and delivery process with a brand new environment and toolset in just under 3 months! We will share our experiences: the good, the bad, and the ugly.

Difference between traditional and agile software developmentDeepaThirumurugan

Introduction to Agile Software Development ProcessSoftware Park Thailand

The document provides an introduction to agile software development processes. It discusses the waterfall model and iterative and incremental model. It then defines agile as a collection of iterative development methodologies that are lightweight and value individuals, interactions, working software, and responding to change. The document outlines agile principles and practices like user stories, story points, test-driven development, pair programming, daily stand-up meetings, story boards, burn down charts, continuous integration, and retrospectives. It concludes with feedback from an agile team noting benefits like earlier defect detection but also challenges in applying new techniques and lack of product management involvement.

03 fse agiledevelopmentMohesh Chandran

This document discusses various agile software development approaches. It begins by outlining the objectives of discussing agile development and explaining the Extreme Programming approach. It then summarizes the Manifesto for Agile Software Development. The rest of the document describes key concepts of agile development such as agility, principles of agility, and human factors important for agile teams. It also provides details on other agile processes including Adaptive Software Development, Dynamic Systems Development Method, Scrum, Crystal, Feature Driven Development, and Agile Modeling.

Agile software developmentRajesh Piryani

The document provides an outline and introduction for a term paper on Agile Software Development. It discusses key aspects of Agile development including the Agile Manifesto, values and principles, methodologies like Extreme Programming (XP) and Scrum, and how Agile development compares to the Waterfall model. The outline covers topics such as the Agile Manifesto, Agile vs Waterfall, methodologies, a case study, performance evaluation, and conclusion.

ISTQB agile tester exam - Conclusions about CertificationMichał Dudziak

This document discusses the ISTQB Agile Tester certification. It provides an overview of agile software development practices like Scrum, Kanban, and user stories. It discusses the tester's role in agile projects, including automating tests, collaborating with developers, and responding quickly to changes. It recommends preparing for the certification by reading materials from ISTQB and other sources, and gaining experience with agile testing practices on the job. Earning the ISTQB Agile Tester certification validates knowledge of agile principles and how to effectively test in agile environments.

Developing Quality Products Quickly through a Culture of CI/CDPaul Hepworth

Extreme programming - a quick and agile overview !Vinit Kumar Singh

Software development life cycleRomano Machoka

The software development life cycle (SDLC) is a process for developing software that aims to produce high quality software at the lowest cost in the shortest time possible. It includes planning, designing, building, testing, deploying, and maintaining a software system. The SDLC involves 7 stages: identifying requirements, planning, designing, building, testing, deploying, and maintaining the software. Each stage contributes to developing software that meets user needs.

Agile TestingNaresh Jain

This document introduces concepts of agile testing and compares it to traditional testing practices. It discusses the fundamental shift in thought process required for agile testing and provides some pointers on tools and techniques used. The traditional software development process involves separate sequential phases of analyze, design, code, and test/bug fix, while agile embraces uncertainty and a more iterative approach.

Our Journey Down the Yellow Brick Road (Agile Adoption @ Directi)Directi Group

Continuous delivery slideshare upload 101914Vijay Reddy

The document outlines a continuous delivery process that includes continuous integration, automated testing, deployment and acceptance testing. Changes are version controlled and built, then all unit, integration and acceptance tests are run along with regression tests. If tests pass, deployments are automated to staging and production environments. User acceptance testing is also conducted before prioritizing releases. The goal is to enable faster delivery, feedback and learning through continuous processes.

CI-CD and DevOps with RubyPierluigi Riti

DevOps is a set of practices aimed at reducing the time between committing code changes and deploying to production while ensuring high quality. It involves treating operations teams as first-class citizens in requirements, making developers responsible for incidents, enforcing consistent deployment processes, using continuous delivery and infrastructure as code. The DevOps lifecycle integrates requirements, development, build, testing, deployment and execution with tools for continuous integration, delivery and monitoring. Adopting CI/CD and DevOps can accelerate time to market, build the right products through frequent releases, improve productivity, deliver reliable releases, improve quality and increase customer satisfaction. A roadmap for DevOps includes improving transparency, implementing CI/CD practices, improving communication between teams, and changing

Agile software developmentskobu

This document summarizes several key aspects of agile software development. It defines agile as an iterative approach performed collaboratively to produce high-quality software that meets changing stakeholder needs. Myths about agile, such as no documentation or planning, are dispelled. Popular agile methods like extreme programming, agile unified process, and scrum are introduced along with their characteristics and processes. The document synthesizes existing literature on agile methods to enable comparison and selection.

Xp exterme-programming-modelAli MasudianPour

Extreme Programming (XP) is a software development methodology intended to improve quality and responsiveness to changing requirements. It involves 5 activities - planning, managing, designing, coding, and testing. Planning includes writing user stories, release planning, and frequent small releases. Managing involves dedicated workspace, stand-up meetings, and measuring velocity. Design focuses on simplicity, metaphors, CRC cards, and refactoring. Coding uses pair programming, tests first, and integration testing. All code must have unit tests that pass before release.

Introduction To Extreme ProgrammingJoe Drumgoole

XPMikalai Alimenkou

XP is an agile software development methodology that was created between 1996-1999. It focuses heavily on quality through practices like pair programming, code review, test-driven development at all levels including acceptance tests written by customers, and continuous integration. XP works best for strong, cohesive teams and requires adopting all of its practices as a unified approach rather than individually.

Myths of Product DevelopmentShoaib Shaukat

This document discusses common misconceptions in product development and proposes lean thinking alternatives. It addresses six prevailing practices: 1) high resource utilization improves performance, 2) large batches improve economics, 3) sticking to plans is best, 4) starting sooner finishes sooner, 5) more features increase customer liking, and 6) getting it right the first time is most successful. For each, it advocates limiting work in progress, incorporating customer feedback early and often through minimal viable products and experimentation, and accepting that plans will change and failure is part of the learning process. The key takeaway is to make information visible, quantify delays, introduce slack, focus on response over efficiency, use small batches with fast feedback, and treat plans and features

Agile Technical LeadershipAlexandru Bolboaca

Test Driven Development presentation delhi meetupNaveen Kumar Singh

Automated agile testing using CucumberNaveen Kumar Singh

The document discusses automated agile testing and test-driven development approaches like behavior driven development (BDD) and acceptance test driven development (ATDD). It describes the BDD process, using the Given-When-Then format for writing acceptance criteria and test cases. Example tools for ATDD, BDD, and test-driven development are provided. Best practices mentioned include using BDD for collaboration, acceptance tests, and test-driven development for coding.

Agile Engineering PracticesVernon Stinebaker

Behavior driven development - Deliver Value by CollaborationNaveen Kumar Singh

A collaborative approach to the quality in the agile enterprise by Jaco ViljoenIndigoCube

The document discusses challenges with quality and collaboration in different software development systems like waterfall, water-scrum-fall, and continuous delivery. It proposes shifting user acceptance testing left to the development phase and implementing acceptance test driven development with the whole team. The solution is to prevent defects through early testing, collaborate around quality, automate acceptance and regression testing, and build a continuous delivery pipeline to enable frequent releases. The implementation involved shifting processes from "water-scrum-fall" to "continuous delivery" with a phased approach to minimize impact.

SDLC SmashupLester Martin

ISTQB Agile ExtensionDavis Thomas

This document provides an overview of agile software testing principles and processes. It begins with discussing the fundamentals of agile development, including the agile manifesto, principles, and common agile approaches like Scrum and Kanban. It then covers key differences between testing in traditional vs agile projects, such as integrated development and testing activities, reduced documentation, and different test levels. The document also discusses important agile testing practices like collaborative user story creation, retrospectives, continuous integration, and the involvement of testers in planning.

XP (IT Brunch)Mikalai Alimenkou

Agile engineering practices – a short overviewSerhiy Yevtushenko

This document provides a short overview of agile engineering practices, including Scrum, XP, Kanban, FDD, and DSDM. It summarizes key practices such as pair programming, test-driven development, behavior driven development, acceptance testing, exploratory testing, polyglot programming, domain specific languages, continuous integration, continuous testing, static code checking, agile databases, lightweight domain modeling, and continuous delivery. Each practice is briefly described in one slide with information on feedback time, styles, and challenges.

Tester’s considerations when moving towards successful CI/CDDerk-Jan de Grood

These are the slides of the tutorial I gave at QA&Testing in Bilbao on 17 October 2018 Continuous integration and deployment (CI/CD) empowers organizations to bring their solution in production fast and frequent. This interactive session will share the benefits of this concept and introduce eight conditions that need to be met in order to make CI/CD a success. After this brief introduction, we will make small groups and explore these conditions, exchange experiences and you will get an understanding what needs to be improved in your organization. Talk to your peers and learn where they stand. Of course each of the groups will share their learnings, so we all go home with an understanding of how you can benefit from CI/CD and what needs to be done to make it work. Finally we will see what test strategy we would advise if our company would decide to move towards CI/CD and this cover we consider much more than just automate our tests…

Continues delivery - IntroductionErez Attar

More Related Content

What's hot (20)

Software development life cycleRomano Machoka

Agile TestingNaresh Jain

Our Journey Down the Yellow Brick Road (Agile Adoption @ Directi)Directi Group

Continuous delivery slideshare upload 101914Vijay Reddy

CI-CD and DevOps with RubyPierluigi Riti

Agile software developmentskobu

Xp exterme-programming-modelAli MasudianPour

Introduction To Extreme ProgrammingJoe Drumgoole

XPMikalai Alimenkou

Myths of Product DevelopmentShoaib Shaukat

Agile Technical LeadershipAlexandru Bolboaca

Test Driven Development presentation delhi meetupNaveen Kumar Singh

Automated agile testing using CucumberNaveen Kumar Singh

Agile Engineering PracticesVernon Stinebaker

Behavior driven development - Deliver Value by CollaborationNaveen Kumar Singh

A collaborative approach to the quality in the agile enterprise by Jaco ViljoenIndigoCube

SDLC SmashupLester Martin

ISTQB Agile ExtensionDavis Thomas

XP (IT Brunch)Mikalai Alimenkou

Agile engineering practices – a short overviewSerhiy Yevtushenko

Software development life cycleRomano Machoka

Agile TestingNaresh Jain

Our Journey Down the Yellow Brick Road (Agile Adoption @ Directi)Directi Group

Continuous delivery slideshare upload 101914Vijay Reddy

CI-CD and DevOps with RubyPierluigi Riti

Agile software developmentskobu

Xp exterme-programming-modelAli MasudianPour

Introduction To Extreme ProgrammingJoe Drumgoole

XPMikalai Alimenkou

Myths of Product DevelopmentShoaib Shaukat

Agile Technical LeadershipAlexandru Bolboaca

Test Driven Development presentation delhi meetupNaveen Kumar Singh

Automated agile testing using CucumberNaveen Kumar Singh

Agile Engineering PracticesVernon Stinebaker

Behavior driven development - Deliver Value by CollaborationNaveen Kumar Singh

A collaborative approach to the quality in the agile enterprise by Jaco ViljoenIndigoCube

SDLC SmashupLester Martin

ISTQB Agile ExtensionDavis Thomas

XP (IT Brunch)Mikalai Alimenkou

Agile engineering practices – a short overviewSerhiy Yevtushenko

Similar to STRIVING FOR CONTINUOUS INTEGRATION AND DEPLOYMENT (20)

Tester’s considerations when moving towards successful CI/CDDerk-Jan de Grood

Continues delivery - IntroductionErez Attar

Continuous everythingTEST Huddle

DevOps - Understanding Core Concepts (Old)Nitin Bhide

Flusso Continuous Integration & Continuous DeliveryJoost van der Griendt

This document discusses continuous integration (CI) and continuous delivery (CD). It defines CI as frequently integrating work and verifying it through automated builds and tests. It defines CD as ensuring every change can be released and any version can be deployed with the push of a button. The document outlines why organizations adopt CI/CD, advanced concepts like infrastructure as code, and provides recommendations for implementing CI/CD such as starting small, automating tasks, and forming cross-functional teams.

Drupal Continuous Integration and devops - Beyond JenkinsPromet Source

Continuous Delivery: why ? where to start ? how to scale ?Jean-Philippe Briend

This document provides an overview of continuous delivery and how to get started with it. It defines key terms like continuous integration, continuous delivery, and continuous deployment. It discusses the benefits of continuous delivery like delivering value faster and with higher quality. It then presents several maturity models for assessing an organization's continuous delivery capabilities. It provides recommendations for where to start the continuous delivery journey, such as focusing on automating deployments and environments first. Finally, it discusses challenges of scaling continuous delivery across large organizations.

Introducing Continuous Integration Using VstsMohamed Samy

Agile with process 3 best for all types ofAssadLeo1

DevOps for absolute beginners (2022 edition)Ahmed Misbah

Are you planning to pursue a career in DevOps? Already working with DevOps but want to know what’s new in 2022? This session is for you! Join us in the 2022 edition of “DevOps for absolute beginners” session, where you will learn all about DevOps from the perspective of People, Process, and Technology. We will be talking about topics like Automation, Continous Integration, Continous Delivery, Infrastructure as Code, etc. We will also be talking about the latest trends in DevOps, including Chaos Engineering, MLOps, and eBPF. The session will conclude with great bonus material for software professional enthusiastic about DevOps, one of them being a carefully crafted learning path for DevOps from years of experience in the industry. Don’t miss out on the rest of the material.

Agile software developmentpradeeppatelpmp

This document provides an overview of agile software development and project progress monitoring. It defines agile as an iterative development approach based on self-organizing teams. Key aspects of agile include adaptive planning, evolutionary development, time-boxed iterations, and responding rapidly to changes. Status is displayed prominently and daily stand-up meetings occur. Common agile methods discussed are Scrum, Extreme Programming, and Kanban. Tools to support agile include Jira, VersionOne, and continuous integration tools.

Continuous EverythingAndrea Tino

The document discusses methodologies for implementing DevOps in an organization, focusing on Continuous Integration (CI), Continuous Delivery (CD), and Continuous Deployment (CDP). It defines each practice and describes the typical architecture and workflows. CI automates building and testing code changes. CD further automates deploying to pre-production environments. CDP fully automates deploying to production. The document warns that CDP is risky and an organization must be prepared with capabilities like fast deployment rollbacks and monitoring before implementing it.

Chapter 2Sergio Andrés Rodríguez Galeano

Agile Software Development MethodologiesPradeep Patel, PMP®

Continuous integration for se group meetingSergii Shmarkatiuk

Continuous integration (CI) is a software engineering practice where developers frequently integrate their work, leading to multiple integrations per day. This approach reduces integration problems and allows teams to develop cohesive software more rapidly. The presentation discusses what CI is, why teams need it, prerequisites like version control and automated testing, typical workflows, tools, and benefits like reduced risks and improved code quality. It also examines problems teams face in implementing CI effectively and potential areas of future research like making CI tools more adaptive and addressing scalability issues.

What is Continuous Integration_ - A Comprehensive Guide.pdfkalichargn70th171

Dev ops != Dev+OpsShalu Ahuja

CI / CD pipeline presentation of SE.pptxmazanali7145

Boast the Potential of DevOps with CI CDZoe Gilbert

How Dealogic Scaled Agile &; Delivers EffectivelyIrfan Ikram

Presented by Irfan Ikram This is a walk through of how Dealogic has adopted agile processes and more importantly scaled them as it has grown as a business. Topics covered include: - DevOps Culture (You Build it, You Run it ) - Rapid Delivery - Minimizing Collaboration - Empowering Teams - Scaling Agile across Teams - Breaking down the monolith product - Managing Continuous Improvement - Effective MVP - Showing Value Delivered

Tester’s considerations when moving towards successful CI/CDDerk-Jan de Grood

Continues delivery - IntroductionErez Attar

Continuous everythingTEST Huddle

DevOps - Understanding Core Concepts (Old)Nitin Bhide

Flusso Continuous Integration & Continuous DeliveryJoost van der Griendt

Drupal Continuous Integration and devops - Beyond JenkinsPromet Source

Continuous Delivery: why ? where to start ? how to scale ?Jean-Philippe Briend

Introducing Continuous Integration Using VstsMohamed Samy

Agile with process 3 best for all types ofAssadLeo1

DevOps for absolute beginners (2022 edition)Ahmed Misbah

Agile software developmentpradeeppatelpmp

Continuous EverythingAndrea Tino

Chapter 2Sergio Andrés Rodríguez Galeano

Agile Software Development MethodologiesPradeep Patel, PMP®

Continuous integration for se group meetingSergii Shmarkatiuk

What is Continuous Integration_ - A Comprehensive Guide.pdfkalichargn70th171

Dev ops != Dev+OpsShalu Ahuja

CI / CD pipeline presentation of SE.pptxmazanali7145

Boast the Potential of DevOps with CI CDZoe Gilbert

How Dealogic Scaled Agile &; Delivers EffectivelyIrfan Ikram

More from Derk-Jan de Grood (20)

Skilling up your dev team - 8 things to consider when skilling-up your dev teamDerk-Jan de Grood

Slides of my DevOps Pro Europe 2025 presentation Vilnius: Most IT organizations face challenges of being underskilled or understaffed, making it difficult to find skilled developers and manage workload efficiently. This leads to risks, dependencies, and delays, particularly when critical tasks depend on a few key developers. Investing in employee development is crucial for improving performance and attracting talent, but it requires strategic planning and collaboration. Companies are aware of this, so why do they keep failing? Successful upskilling involves team autonomy, leadership buy-in, and dedicated focus. This presentation outlines eight key considerations for effective upskilling: defining clear roles, identifying needed skills, conducting gap analyses, planning for future needs, exploring diverse training methods, securing leadership support, actively monitoring progress, and embedding upskilling into HR processes. By addressing these aspects, organizations can foster technical excellence and continuous improvement.

Value Determination with the value framework v04.pptxDerk-Jan de Grood

Slides of my DevOps Pro Europe 2025 presentation Vilnius: Organizations seeking to enhance value delivery benefit from better planning and prioritization. The value framework offers a simple way to rate backlog items based on their value, aligning them with organizational goals and making priority decisions more transparent, also to the stakeholders. In my talk, I'll explain how to use and adapt the framework. In my organization, introducing the Value Framework with five independent rating factors made value determination more objective and efficient. This streamlined backlog prioritization and improved meeting engagement. The framework provides guidelines for implementation, fostering awareness and alignment among product owners, and enabling faster, more objective value determination.

IAD2024 Easy Value Determination with the Value FrameworkDerk-Jan de Grood

rganizations seeking to enhance value delivery benefit from better planning and prioritization. The value framework offers a simple way to rate backlog items based on their value, aligning them with organizational goals and making priority decisions more transparent, also to the stakeholders. In my talk, I'll explain how to use and adapt the framework. In my organization, introducing the Value Framework with five independent rating factors made value determination more objective and efficient. This streamlined backlog prioritization and improved meeting engagement. The framework provides guidelines for implementation, fostering awareness and alignment among product owners, and enabling faster, more objective value determination.

2022 IPMA Vakdag- Back to Basic v02 - compressed for handout.pptxDerk-Jan de Grood

The document discusses different phases or "waves" of an Agile transformation within an organization. It describes three waves: 1) teams mastering Agile basics, 2) focusing on cross-team alignment and technical releases, and 3) focusing on business value and performance. Each wave is characterized by typical challenges regarding organizational structure, roles, workflow, collaboration, dependencies and metrics. The model provides insights for organizations on where they are in their Agile journey and what steps they can take to continue progressing.

Keeping the customer satisfied as an agile coachDerk-Jan de Grood

These are the slides of the presentation I gave at the agile testing days 2021. In this presentation I will explain how as agile coaches can keep our stakeholders satisfied In my latest book I describe the things that customers want. In order to deliver solutions that create happy customers they should have insight in wat they purchase, they want to have control and be able to adapt their product or subscription, it should be safe and reliable, delivered fast and cheap. While writing the book it occurred to me that agile coaches have customers also. In this presentation I will explain how these items apply to agile coaching as well and how as agile coaches can keep our stakeholders satisfied. We’ll discuss coaching agreements, transformational roadmaps as means to provide insight. How we can allow adaptivity in our coaching, What Agile coaches can do provide safety and how e.g., self service can be applied to reduce costs and speed up delivery. How does this apply in distributed teams and what self-service coaching can we define? But, most of all I will share practices and explain how they can be used to make an impact, deliver value and keep our customer satisfied. Attend this talk when you want to learn some effective practices and gain understanding how they relate to each other. When you want work on the satisfaction of your internal customers.

Aginext 2021: Built-in Quality - How agile coaches can contributeDerk-Jan de Grood

Built-in Quality is key when you want to achieve Business Agility. Yesterday I spoke at the AgiNext Conference in London. In my presentation I explained the importance of Built-in Quality, what is actually is and introduced an approach to implement it. The presentation explains how we can take a validated learning approach to eliminate waste and learn how to improve our development life cycle. I share the suggestions that SAFe makes and give a prioritised overview of quality measures. Throughout the presentation I share my thought on how Agile Coaches can contribute to built quality in.

Agile Business Day 2020 - Refinement- Unlock the full potential of your refi...Derk-Jan de Grood

Good refinement makes development more predictable, leads to better solutions and enables the Product Owner to set the right priorities. Still many teams fail to unlock the full potential of refinement. Join this session to get practical tips to get more out of your refinement sessions.I have guided many teams during their transition toward Agile. Initially most attention went to the ceremonies and understanding the agile values. Experience taught me that when the team gets up to speed refinement becomes a bottleneck. Crucial because good refinement makes development more predictable, leads to better solutions and enables the Product Owner to set the right priorities.Unfortunately, I see many teams that do not unlock the full potential of refinement. Not only is the time spent on refinement often limited, many of the refinement meetings I join are inefficient. I meet teams that spent half the meeting watching the Product Owner entering the new backlog items in the workflow system. Although they poker the user stories afterwards, little time is left to discussions the best solution and risks that need to be avoided.In this talk I will focus on the following topics• Advantages of good refinement and what I see in daily practise• How we can boost the potential of Refinement by organising it as a process rather than a meeting• Introduction of challenging questions that can be used to prepare your refinement• And last but not least, how you can involve the off-site team members of distributed teamsJoin this session if you are an Agile Coach of SM and want to help your team(s) to get more out of refinement. If you are a PO and feel a need to boost quality and predictability, or if you are a member of a distributed team and want to involve your fellow team members making better solutions.

Agile Testing Days -the Challenges AheadDerk-Jan de Grood

The document discusses challenges that will influence the way testing work is done in the future. It highlights trends like test automation, continuous integration and deployment, changing technical and business knowledge needs, and working in multi-disciplinary teams. The keynote speakers will discuss these challenges and provide guidance on how testers can prepare for them. They will also recommend sessions in the ATD2019 conference program that can help attendees prepare for these challenges and trends.

Test Management in Agile - Agile testing Days 2018Derk-Jan de Grood

Yesterday Jan Jaap Cannegieter and I gave an amazing tutorial at the Agile testing days. In our full day tutorial we discussed the role of the test manager and how to add value in an agile environment. We discovered that a test manager is operation at two interfaces. One is being that of a quality ambassador that shows the business and stakeholders how testing is done and how its progressing . On the other interface the test manager is enabling the team(s) to build quality into their deliverables. During this full day tutorial we deep dived on both aspects. We discussed the agile test strategy and investigated what activities we test managers undertake, what activities we find important and what is valued most by our stakeholder. You wouldn’t be surprised if we told you that there is a gap between both. Next we practiced with defining agile test plans at MVP and sprint level. And assessed other roles that test managers can adopt. We closed the full circle by concluding that extra activities might be added to our initial brainstorm results. The topic is truly alive. Not only did we have a full rum (we had an all-time conference record with the amount of attendees), during the day we had a lot of lively discussions and answered a lot of questions from the participants. We loved the participation of all in the room and believe we all had a good day.

Keynote: Testing and Quality in the Scaled Agile Framework for Lean Enterpris...Derk-Jan de Grood

This document summarizes a keynote presentation on testing and quality in the Scaled Agile Framework (SAFe) given by Mette Bruhn-Pedersen and Derk-Jan de Grood. It discusses how SAFe addresses testing and quality, but that more guidance could be provided, especially around roles. It also provides suggestions for defining a quality strategy and embedding quality practices at each level of the framework, from the team to portfolio levels. The presentation emphasizes building quality in from the start and establishing a chief quality officer role.

I am a agile tester, because...(Agile testing put to practice)Derk-Jan de Grood

On 12 September Andreas Prins and I gave two presentation on the TestNet session night. The theme of the event was: Transforming testing to fit modern development. Andreas identified various rhythms (or wavelengths) in the SDLC and explained the automation that can be done in order to have short lead times and frequent feedback on code quality and delivered value. My presentation was called “I am an agile tester, because…”. During my talk I discussed what it takes to be an agile tester and I introduced 12 statements that can be used as manifesto for the agile tester. During the presentation 40+ participants filled in the survey and we got a nice impression of how agile our testing is. You can find the results below, and in the slide deck. Using a recent project I was involved in I put these statements to the test. I explain the test strategy I applied and shared my successes and failures. One of the participants tweeted about the presentation: “A nice war story. The 12 statements trigger me to think about my own role and the role of testing within my project and organization”. I think I succeeded my mission.

I am a agile tester, because...(masterclass at the Barcelona Test Academy)Derk-Jan de Grood

These are the slides of the masterclass I gave 24-1-2018 at the Barcelona Test Academy. Using a assessment we started a discussion about what it takes to be an agile tester. Description: Testing has transformed into Agile Testing. Testing has become a responsibilty of the whole development team. Many testers wonder what their role is now that everyone is testing. Some people say that Testing is WHAT we do and Agile is HOW we do it. In order to contribute effectively to quality solutions, agile testers need to combine the WHAT and HOW in their daily approach. Time for a deep-dive. What defines the agile tester and how do we add value. In this workshop participant will fill ins an self-assessment based on the 12 characteristics of the agile tester. We’ll share the group results and create a snapshot of where we stand. Next, we will discuss each of the characteristics mean to us, how do they make agile testing work, help to boost the agility of the test process and how we can embed quality in the agile development process. In groups we will share examples from the trenches to go along with each of characteristics. What do we do to make it work, and what challenges do we encounter? Participants will help each other and be able to benchmark their own ideas. This session aligns with the needs that I recognize with many colleagues. They are good testers, work successfully in an agile environment, but want to get better in explaining why they are a good tester. How does their attitude and approach contribute to valuable software solutions? Join this session if you want to improve yourself and want to get practical tips from the real world; If you want to learn what makes your testing agile and how is your agile mindset translated into a valuable testing approach. Participants can use the self-assessment to identify blind spots in their skills. Each of the participants will leave the room with a good understanding of where he/she stands: “I am an agile tester because…”

Agile Testing Days -Trends and future in testing 2017Derk-Jan de Grood

Today I gave a presentation at the Agile Testing Days. The room was packed and we talked about the way the testing profession in evolving. 5 years ago the Dutch Test Association published a book that described the changes in the testing profession. I was one of the 7 authors and we organized a few workshops on the theme. Last may we hosted a retrospective workshop during which the participants evaluated the 2012 predictions. Key question during this workshop was: What is the status of the profession and what skills and role should a tester take in order to add value and a job. In my 2017 ATD presentation I shared the results that of this workshop. I shared the highlights of the book, told what predictions were correct and which were incorrect. But most of all I will shared the opinion of or fellow testers: What do roles do they have now, and what roles do they expect to have in 5 years from now. Join this session if you are sometimes worried about the sustainability of your role, if you want to specialize yourself but wonder what specialisms are a safe bet, if you want to stay ahead of the game and be prepared for the future.

Getting a grip on your test maturity using the ambition chartDerk-Jan de Grood

Agile test teams access their effectiveness every sprint. The power of retrospectives is that they, when done well, focus on improving in small achievable steps. This ensures that progress is being made and is more than just a far away dream. Despite the above, I experienced that in and around teams the proposed improvements are measured and valued against the maturity of the agile adoption. I noticed that in several situations people were judging the performance of the team and the proposed improvements against an implicit blueprint; small improvements were fine “for just now” and regarded as a “good first step”. The implication of the above struck me! We all had our own plan and expectations, but these were implicit and not transparent. In reaction I developed the ambition chart. It is a graphical one-pager that gives insight in the current state, the collective ambition and describes the next step to be taken. The ambition chart can be used to: Discus and align expectations and ambition that individual team members have and create a team goal. To break big goals into smaller steps To prioritize improvement suggestions made in the retrospective To manage dependencies between different area’s of improvement To focus on the next step that needs to be taken, without being distracted by the end goal Manage expectations that management and stakeholders have, e.g. by clarifying that the team does a lot of things very well, but address that it has identified some improvements that are not yet on the agenda. To visualize progress and tell success stories to the rest of the organization In this presentation I will explain how to make and use an ambition chart. I will explain situations in which it can be beneficial and share some examples of focus areas.

Practitest webinar - When a test manager makes a differenceDerk-Jan de Grood

Due to the adoption of Agile, the role of test manager seems redundant. Teams and individual professionals are self-managing and coordinating their own work. Nevertheless, in some organizations and projects, there is a need for a quality ambassador that understand the agile quality strategy and can help, monitor and ensure that working solutions are delivered. In this webinar we will explore situations in which you as a test manager can make a difference. For example: How do we e.g. deal with compliance, integration and final acceptance in a contractor’s context? How does a test manager coordinate the work over teams and ensures the quality of the testing itself? Thanks Joel Montvelisky, PractiTest Chief Solution Architect, for hosting my webinar.

EuroSTAR webinar: creating Agile Test Strategies for larger EnterprisesDerk-Jan de Grood

Many organisations are reducing their test managers and Test Competence Centres. Quality is embedded in development. Testing is responsibility of the team. Still testing is on the rebound. In bigger projects and in enterprises an effective test strategy is vital to ensure that the team does the right testing, we focus on integration and we have insight in inter- team dependencies. In this webinar, Derk-Jan will share his experiences as an overall test manager in various projects and define some key ingredients of an Agile Test Strategy.

Agile in de Echte Wereld- Starten met ScrumDerk-Jan de Grood

Op 15 december 2016 presenteerden we het nieuwe boek: Agile in de Echte Wereld- Starten met Scrum op het kantoor van Valori. Uitnodigingstekst: "Agile in de Echte Wereld, Starten met Scrum", het nieuwe boek van Derk-Jan de Grood is uit! Dit heugelijke feit vieren we op donderdag 15 december a.s. graag met een select gezelfschap. We zouden het erg leuk vinden als jij bij de boekpresentatie aanwezig wilt zijn en nodigen je hierbij dan ook van harte uit. Derk-Jan heeft zijn agile kennis en ervaring en die van zijn Valori collega’s verwerkt tot een praktische gids waarin de invoering van Scrum centraal staat. Met als resultaat een gemakkelijk lezend boek dat geworteld is in de echte wereld. Het gaat niet over cutting-edge innovatie voor de enkeling, maar over de zaken die iedereen dagelijks tegenkomt als je aan de slag gaat met Scrum. Het boek staat vol met herkenbare dilemma's en toegankelijke tips. Het is daarmee een praktisch leidraad voor iedereen die start met Scrum, of die zijn agile ontwikkelproces wil verbeteren. Tijdens de boekpresentatie op 15 december zal, naast een introductie van de auteur zelf, ook Bernadet Miceli haar ervaringen delen over de Scrum transitie bij Greenchoice. Na afloop ontvang je het boek gratis* mee naar huis en zal Derk-Jan, indien gewenst, het boek signeren. Programma 16:30 Ontvangst 17:00 Introductie van het boek door Derk-Jan de Grood - Auteur, Thoughtleader Testen en Agile-tranisitiecoach bij Valori 17:30 Scrum transitie bij Greenchoice door Bernadet Miceli – Manager IT bij Greenchoice 18:00 Borrel, signeren en netwerken 19:00 Einde

Getting a grip on your agile maturity using the ambition chartDerk-Jan de Grood

This document discusses using an Ambition Chart to measure and improve agile maturity over time. The Ambition Chart identifies key maturity areas and allows teams to assess their current status, set incremental goals, and track progress. Examples are provided of Ambition Charts used for testing maturity and Scrum implementation. Guidance is given on identifying areas, dreaming of an ideal future state, defining small steps, using descriptive statements, and focusing on continuous improvement rather than end goals.

Testing fundamentals in a changing world (annotated slides)Derk-Jan de Grood

Slides of my September SIGIST Keynote. Description: With the fast adoption of agile the definition of testing and our test approach changes. When deploying daily, there is no room for manual testing and a test report. It’s time to get back to our fundamentals. Why do we work the way we do, and what needs do organisations have? In this Keynote, Derk-Jan de Grood will explore the fundamental assets of the test profession, so we can reshape or test approach and make it work in an Agile context. Although the daily focus shifts from working in silo’s to collaboration, from execution to coaching, from preparing to doing, the test fundamentals remain in place. In our search we will distinguish unchanged artefacts that we’ll create for a different reason and goals that remain unchanged but will only be achieved if we take a different route. But bear in mind, not every project is done by using agile methods. Therefore we’ll also explore what concepts of agile testing can we use to improve our traditional projects. By understanding what is changed and what not we can adopt our approach, guide our stakeholders and colleagues in order to align testing with the company goals. Three key points:  Both agile and traditional projects are changing – testing needs to align  We still need some of the same test fundamentals – but perhaps for a different reason  We still have some of the same test goals – but we’ need to achieve them in different ways.

Survival techniques for Testers-BEYOND THE T-SHAPED TESTER Derk-Jan de Grood

he T-shaped tester (Rob Lambert, Lisa Crispin and Janet Gregory) combines need for general knowledge with advanced test skills to be successful. But testing is a versatile profession and demands are growing. Time to go beyond the T-shape and introduce the π-shaped tester. Extend your global knowledge (development, project management, agile etc) and test skills with yet another specialism to stay in demand, e.g. security, test automation, requirements. In this webinar, Derk-Jan and Jan Jaap report the results of their search for future needs. They explain how we can survive as a tester and what skills and knowledge we need to develop. In their story they include the responses they got from the 100 participants that joined the workshops they gave on this topic. Key Takeaways: Become aware of the need to continuously develop yourself What specialism’s should I adapt to become a better tester Insights in how to brand your knowledge and let the world know about your specialism Derk Jan de Grood WebinarDerk-Jan de Grood works for Valori as senior test manager and Agile Transition Coach. His drive is to improve the visibility of testing in both agile and traditional organizations, by sharing his knowledge and experience by means of training, presentations, workshops and publications. He is a regular speaker at conferences like EuroSTAR, wrote several successful books on software testing and publishes articles for the major testing magazines. In 2014 he won the EuroSTAR Testing Excellence Award. Jan Jaap Cannegieter webinarJan Jaap Cannegieter is a well-known consultant, author, (keynote) speaker and requirements and test specialist form the Netherlands. He has 20 years of experience in ICT and did assignment s in testing, quality assurance, TMMi, CMMI, SPI, Agile and requirements. In testing he was a tester, test manager, test consultant and workshop leader. At this moment Jan Jaap is test/QA-manager and delivery manager at DinamiQs and vice president of SYSQA B.V., a company of 180 employees specialized in requirements, software testing, quality assurance and IT-governance. Within SYSQA Jan Jaap coaches other testers and test managers, is the thought leader and responsible for product development. He is the driving force behind Situational Testing and he wrote several articles and books in the Netherlands.