Overview of the different aspects of agile engineering practices (the modern practices for software development) and how they can be adopted in [agile] teams.
This document discusses engineering practices within Scrum and proposes updates to the Agile Manifesto. It begins by summarizing the four values of the original Agile Manifesto. It then argues the Agile Manifesto is outdated and proposes expanding on its values. The document outlines goals for improving the current state of Agile, including demanding technical excellence, promoting culture change, maximizing business value, and organizing knowledge. Finally, it lists six engineering practices within Scrum: requirements elaboration management, configuration management, integration, layered testing, agile architecture and design, and coding standards.
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.
Agile Testing - presentation for Agile User Groupsuwalki24.pl
The document discusses agile testing principles and processes. It compares agile testing to waterfall testing and outlines some key differences. It also addresses topics like continuous integration, test automation, managing test cases and issues, and transitioning from waterfall to agile. Pseudo-agile projects are described as those that claim to use agile but lack key elements like automation, continuous integration, or involvement of testers throughout the process.
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.
The document discusses unit testing and test-driven development (TDD). It introduces unit testing and TDD, explaining their benefits and how they can improve quality. It also provides an overview of JUnit for unit testing in Java and the red-green-blue process for TDD. The document concludes with a live demo of TDD and suggestions for implementing TDD and acceptance test-driven development.
The document outlines a test strategy for an agile software project. It discusses testing at each stage: release planning, sprints, a hardening sprint, and release. Key points include writing test cases during planning and sprints, different types of testing done during each phase including unit, integration, feature and system testing, retrospectives to improve, and using metrics like burn downs and defect tracking to enhance predictability. The overall strategy emphasizes testing early and often throughout development in short iterations.
This document discusses engineering practices within Scrum and proposes updates to the Agile Manifesto. It begins by summarizing the four values of the original Agile Manifesto. It then argues the Agile Manifesto is outdated and proposes expanding on its values. The document outlines goals for improving the current state of Agile, including demanding technical excellence, promoting culture change, maximizing business value, and organizing knowledge. Finally, it lists six engineering practices within Scrum: requirements elaboration management, configuration management, integration, layered testing, agile architecture and design, and coding standards.
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.
Agile Testing - presentation for Agile User Groupsuwalki24.pl
The document discusses agile testing principles and processes. It compares agile testing to waterfall testing and outlines some key differences. It also addresses topics like continuous integration, test automation, managing test cases and issues, and transitioning from waterfall to agile. Pseudo-agile projects are described as those that claim to use agile but lack key elements like automation, continuous integration, or involvement of testers throughout the process.
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.
The document discusses unit testing and test-driven development (TDD). It introduces unit testing and TDD, explaining their benefits and how they can improve quality. It also provides an overview of JUnit for unit testing in Java and the red-green-blue process for TDD. The document concludes with a live demo of TDD and suggestions for implementing TDD and acceptance test-driven development.
The document outlines a test strategy for an agile software project. It discusses testing at each stage: release planning, sprints, a hardening sprint, and release. Key points include writing test cases during planning and sprints, different types of testing done during each phase including unit, integration, feature and system testing, retrospectives to improve, and using metrics like burn downs and defect tracking to enhance predictability. The overall strategy emphasizes testing early and often throughout development in short iterations.
A software testing practice that follow the principle of agile software development is called Agile Testing.
Agile is an iterative development methodology where requirement evolve through collaboration between the customer and self-organizing teams and agile aligns development with customer need.
Website: https://www.1solutions.biz/
Agile testing principles and practices - Anil KaradeIndicThreads
Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum.
The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.
Agile Testing – embedding testing into agile software development lifecycle Kari Kakkonen
My presentation on Agile Testing, including a tuning concept and a case study of agile testing choices in a project, held 16 of June, 2014 at a customer internal seminar.
The document provides an overview of agile scrum testing methodology. It describes agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. It then outlines the key aspects of scrum testing including product backlogs, sprints, daily standup meetings, sprint planning and retrospectives. It also discusses the proposed scrum testing process of identifying test scenarios, writing test cases per sprint, delayed execution, and inclusion of defects in the product backlog.
This document summarizes a presentation about improving software development practices at a company. It discusses bringing in experts to teach test-driven development, refactoring, and applying agile principles like Scrum. Over several years, it shows how the company gradually adopted more practices like automated unit testing, design principles, embedded agile, and combining agile with Six Sigma. Coaching individual teams and a whole module helped advance skills and standards, but spreading the changes more widely remained a challenge.
Introducing QA Into an Agile EnvironmentJoseph Beale
This document discusses introducing quality assurance (QA) processes into an agile development environment. It describes some common challenges that can arise when development and testing are not well integrated, such as business stakeholders finding bugs late in the process. The author advocates for making QA practices and results visible and incorporating QA personnel into agile ceremonies like planning and demos. With collaboration, commitment to quality, and clear communication, the QA team was able to gain trust and find bugs earlier. Their approach evolved to take on more types of testing, and they worked with business to define different testing levels and work testing around releases.
This document presents an overview of agile testing. It discusses how agile testing differs from general testing by following the principles of agile software development and involving all team members, including testers. The document notes that specification by example is used to define desired and undesired behaviors to guide coding. Some benefits of agile testing are more testing time, continuous testing, face-to-face communication, self-organization, less manual testing, and competency development.
Testing and DevOps Culture: Lessons LearnedLB Denker
This document discusses the speaker's background and experiences with software engineering practices. It covers his education in computational mathematics and computer science, past roles at Universal Instruments developing machine software and at Google and Etsy implementing DevOps practices. Key topics covered include the benefits of continuous integration, deployment and delivery; the importance of testing including test-driven development; and embracing interdependence between developers and other IT roles. Best practices are noted to be situational and relationships must be respected.
Slides from a session presented by Fadi Stephan from Kaizenko at the 2019 Global Scrum Gathering in Austin, TX on 05/20/2019 DC. Also see the blog series on Agile Testing at https://www.kaizenko.com/agile-testing/
Abstract:
Many teams struggle with fitting in testing activities inside of a Sprint. They end up doing primarily development activities in a Sprint and push testing activities to run in dedicated testing Sprints following the coding Sprints or have a coding and testing Sprint running in parallel. However, in Scrum, the output of every Sprint is a potentially shippable product increment. This means the product increment should be well tested within the Sprint and ready to be delivered. Come to this presentation to learn how to tackle testing on an Agile team, what kind of tests to execute, what to automate and what not to automate, the different test responsibilities, and when to run which tests. Leave with a testing strategy that you can start applying the next day to gradually get a team to start testing from day 1 of the Sprint and deliver a true product increment at the end of each Sprint.
This document provides an overview of agile testing. It discusses what agile testing is, common agile testing strategies and stages, principles of agile testing, advantages such as reduced time and money and regular feedback, challenges like compressed testing cycles and minimal time for planning, and concludes that communication between teams is key to agile testing success. The agile testing life cycle involves four stages: iteration 0 for initial setup, construction iterations for ongoing testing, release for deployment, and production for maintenance. Principles include testing moving the project forward, testing as a continuous activity, everyone on the team participating in testing, and reducing feedback loops.
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
Agile Testing involves testing in the context of Agile development. It is done continuously and collaboratively by all members of the team throughout the development process, rather than just by QA/testers at the end. This helps ensure high quality, useful software is delivered iteratively.
Agile tour ncr test360_degree - agile testing on steroidsVipul Gupta
This document discusses challenges with product testing in agile environments and introduces an approach called "Agile Testing on Steroids" to address these challenges. It presents the philosophy behind Agile Testing on Steroids which is to take a pragmatic approach using integrated toolsets and practices to remove subjectivity from decision making. Key aspects include test automation, continuous integration, requirement and test case management, defect tracking, and metrics collection to enable fact-based prioritization, decisions and traceability between requirements, code, tests and defects. The benefits outlined are more streamlined, systematic and comprehensive testing that acts as an informal collaboration platform.
Shift left as first transformation step into Quality AssuranceZbyszek Mockun
Do you work in a company which has established effective testing process, which ensure high quality and support Agile methodologies? Can your testing process be used as a model for other companies? Fortunately, we were in that place a few years ago and had to ask ourselves a question about the next step. The answer was: Let’s be Quality Assurance Engineers rather than Testers. But what should we do? How can we do this transformation?
At the same time, I got feedback from my colleague – Head of Java practice: “Your testers found defects in areas / scenarios which weren’t included in development scope / my devs didn’t know that should cover those edge cases. What can we do with that?”
I had to agree with him. There is no sense to test scenarios which weren’t implemented. This was the starting point of our transformation. We decided to implement Shift left model as it looks like the most promising one. But when we implemented it not everything worked as smooth as we wished. New challenges appeared, but more in my presentation.
Comparative study on agile software development: Software development methodologies are constantly evolving due to changing technologies and new demands from users. Today’s dynamic business environment has given rise to emergent organizations that continuously adapt their structures, strategies, and policies to suit the new environment[12]. Such organizations need information systems that constantly evolve to meet their changing requirements. Though traditional software development methodologies, such as life cyclebased structured and object oriented approaches, continue to dominate the systems development few decades and much research has done in traditional methodologies, Agile software development brings its own set of novel challenges that must be addressed to satisfy the customer through early and continuous delivery of the valuable software. It’s a set of best practice that allows rapid delivery of high quality software to meet customer needs and also accommodate changes in the requirements.[13] Traditional, plan-driven software development methodologies lack the flexibility to dynamically adjust the development process. Agile development is the ability to develop software quickly keeping pace with the rapidly changing requirements. We speculate that from the need to satisfy the customer through early and continuous delivery of the valuable software, Agile software development is emerged. In this paper, we provide a brief comparison of agile development methodologies with traditional systems development methodologies, and discuss the challenges of adopting agile methodologies. A number of software development methods such as extreme programming (XP), feature-driven development, crystal clear method, scrum, dynamic systems development, and adaptive software development are also briefly discussed in this paper.
A guide for adopting Agile Testing. Gives the overall framework, principles and practices. Starts with Introduction to Agile Testing and then moves on to cover technical practices, HR and training needs which need focus during implementation of Agile Testing.
YouTube Link: https://youtu.be/UQWyG3xSr5k
** Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses **
This Edureka PPT on "What is Agile Testing" will help you get in-depth knowledge on Agile testing and why it is important to perform agile tests on your software in an iterative manner.
What is Agile Testing?
Principles of Agile Testing
Advantages
Agile Testing Methods
Life Cycle
Test Plan & Quadrants
Companies using Agile Testing
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Slide of the T.D.D. Coding Dojo (programming language neutral version)
T.D.D. Dojo Agenda (3 hours):
05' Welcome and Dojo rules.
15' T.D.D. in a very small nutshell (slides)
05' Q&A
20' TDD Sempai demo (I will show how to use TDD to solve a simple kata)
10' Choose the kata
25' Kata first round
05' break
25' Kata second round
05' break
25' Kata third round
05' break
30' Lesson learned: code sharing
Short presentation of unit test as a method to verify isolated units of code.
Unit test is a white box, code level testing method
Unit tests are written by coders for coders to test the code design (and the code functionality)
A software testing practice that follow the principle of agile software development is called Agile Testing.
Agile is an iterative development methodology where requirement evolve through collaboration between the customer and self-organizing teams and agile aligns development with customer need.
Website: https://www.1solutions.biz/
Agile testing principles and practices - Anil KaradeIndicThreads
Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum.
The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.
Agile Testing – embedding testing into agile software development lifecycle Kari Kakkonen
My presentation on Agile Testing, including a tuning concept and a case study of agile testing choices in a project, held 16 of June, 2014 at a customer internal seminar.
The document provides an overview of agile scrum testing methodology. It describes agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. It then outlines the key aspects of scrum testing including product backlogs, sprints, daily standup meetings, sprint planning and retrospectives. It also discusses the proposed scrum testing process of identifying test scenarios, writing test cases per sprint, delayed execution, and inclusion of defects in the product backlog.
This document summarizes a presentation about improving software development practices at a company. It discusses bringing in experts to teach test-driven development, refactoring, and applying agile principles like Scrum. Over several years, it shows how the company gradually adopted more practices like automated unit testing, design principles, embedded agile, and combining agile with Six Sigma. Coaching individual teams and a whole module helped advance skills and standards, but spreading the changes more widely remained a challenge.
Introducing QA Into an Agile EnvironmentJoseph Beale
This document discusses introducing quality assurance (QA) processes into an agile development environment. It describes some common challenges that can arise when development and testing are not well integrated, such as business stakeholders finding bugs late in the process. The author advocates for making QA practices and results visible and incorporating QA personnel into agile ceremonies like planning and demos. With collaboration, commitment to quality, and clear communication, the QA team was able to gain trust and find bugs earlier. Their approach evolved to take on more types of testing, and they worked with business to define different testing levels and work testing around releases.
This document presents an overview of agile testing. It discusses how agile testing differs from general testing by following the principles of agile software development and involving all team members, including testers. The document notes that specification by example is used to define desired and undesired behaviors to guide coding. Some benefits of agile testing are more testing time, continuous testing, face-to-face communication, self-organization, less manual testing, and competency development.
Testing and DevOps Culture: Lessons LearnedLB Denker
This document discusses the speaker's background and experiences with software engineering practices. It covers his education in computational mathematics and computer science, past roles at Universal Instruments developing machine software and at Google and Etsy implementing DevOps practices. Key topics covered include the benefits of continuous integration, deployment and delivery; the importance of testing including test-driven development; and embracing interdependence between developers and other IT roles. Best practices are noted to be situational and relationships must be respected.
Slides from a session presented by Fadi Stephan from Kaizenko at the 2019 Global Scrum Gathering in Austin, TX on 05/20/2019 DC. Also see the blog series on Agile Testing at https://www.kaizenko.com/agile-testing/
Abstract:
Many teams struggle with fitting in testing activities inside of a Sprint. They end up doing primarily development activities in a Sprint and push testing activities to run in dedicated testing Sprints following the coding Sprints or have a coding and testing Sprint running in parallel. However, in Scrum, the output of every Sprint is a potentially shippable product increment. This means the product increment should be well tested within the Sprint and ready to be delivered. Come to this presentation to learn how to tackle testing on an Agile team, what kind of tests to execute, what to automate and what not to automate, the different test responsibilities, and when to run which tests. Leave with a testing strategy that you can start applying the next day to gradually get a team to start testing from day 1 of the Sprint and deliver a true product increment at the end of each Sprint.
This document provides an overview of agile testing. It discusses what agile testing is, common agile testing strategies and stages, principles of agile testing, advantages such as reduced time and money and regular feedback, challenges like compressed testing cycles and minimal time for planning, and concludes that communication between teams is key to agile testing success. The agile testing life cycle involves four stages: iteration 0 for initial setup, construction iterations for ongoing testing, release for deployment, and production for maintenance. Principles include testing moving the project forward, testing as a continuous activity, everyone on the team participating in testing, and reducing feedback loops.
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
Agile Testing involves testing in the context of Agile development. It is done continuously and collaboratively by all members of the team throughout the development process, rather than just by QA/testers at the end. This helps ensure high quality, useful software is delivered iteratively.
Agile tour ncr test360_degree - agile testing on steroidsVipul Gupta
This document discusses challenges with product testing in agile environments and introduces an approach called "Agile Testing on Steroids" to address these challenges. It presents the philosophy behind Agile Testing on Steroids which is to take a pragmatic approach using integrated toolsets and practices to remove subjectivity from decision making. Key aspects include test automation, continuous integration, requirement and test case management, defect tracking, and metrics collection to enable fact-based prioritization, decisions and traceability between requirements, code, tests and defects. The benefits outlined are more streamlined, systematic and comprehensive testing that acts as an informal collaboration platform.
Shift left as first transformation step into Quality AssuranceZbyszek Mockun
Do you work in a company which has established effective testing process, which ensure high quality and support Agile methodologies? Can your testing process be used as a model for other companies? Fortunately, we were in that place a few years ago and had to ask ourselves a question about the next step. The answer was: Let’s be Quality Assurance Engineers rather than Testers. But what should we do? How can we do this transformation?
At the same time, I got feedback from my colleague – Head of Java practice: “Your testers found defects in areas / scenarios which weren’t included in development scope / my devs didn’t know that should cover those edge cases. What can we do with that?”
I had to agree with him. There is no sense to test scenarios which weren’t implemented. This was the starting point of our transformation. We decided to implement Shift left model as it looks like the most promising one. But when we implemented it not everything worked as smooth as we wished. New challenges appeared, but more in my presentation.
Comparative study on agile software development: Software development methodologies are constantly evolving due to changing technologies and new demands from users. Today’s dynamic business environment has given rise to emergent organizations that continuously adapt their structures, strategies, and policies to suit the new environment[12]. Such organizations need information systems that constantly evolve to meet their changing requirements. Though traditional software development methodologies, such as life cyclebased structured and object oriented approaches, continue to dominate the systems development few decades and much research has done in traditional methodologies, Agile software development brings its own set of novel challenges that must be addressed to satisfy the customer through early and continuous delivery of the valuable software. It’s a set of best practice that allows rapid delivery of high quality software to meet customer needs and also accommodate changes in the requirements.[13] Traditional, plan-driven software development methodologies lack the flexibility to dynamically adjust the development process. Agile development is the ability to develop software quickly keeping pace with the rapidly changing requirements. We speculate that from the need to satisfy the customer through early and continuous delivery of the valuable software, Agile software development is emerged. In this paper, we provide a brief comparison of agile development methodologies with traditional systems development methodologies, and discuss the challenges of adopting agile methodologies. A number of software development methods such as extreme programming (XP), feature-driven development, crystal clear method, scrum, dynamic systems development, and adaptive software development are also briefly discussed in this paper.
A guide for adopting Agile Testing. Gives the overall framework, principles and practices. Starts with Introduction to Agile Testing and then moves on to cover technical practices, HR and training needs which need focus during implementation of Agile Testing.
YouTube Link: https://youtu.be/UQWyG3xSr5k
** Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses **
This Edureka PPT on "What is Agile Testing" will help you get in-depth knowledge on Agile testing and why it is important to perform agile tests on your software in an iterative manner.
What is Agile Testing?
Principles of Agile Testing
Advantages
Agile Testing Methods
Life Cycle
Test Plan & Quadrants
Companies using Agile Testing
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Slide of the T.D.D. Coding Dojo (programming language neutral version)
T.D.D. Dojo Agenda (3 hours):
05' Welcome and Dojo rules.
15' T.D.D. in a very small nutshell (slides)
05' Q&A
20' TDD Sempai demo (I will show how to use TDD to solve a simple kata)
10' Choose the kata
25' Kata first round
05' break
25' Kata second round
05' break
25' Kata third round
05' break
30' Lesson learned: code sharing
Short presentation of unit test as a method to verify isolated units of code.
Unit test is a white box, code level testing method
Unit tests are written by coders for coders to test the code design (and the code functionality)
The document discusses software development life cycles (SDLC) and software testing. It describes several SDLC models - waterfall, spiral, V, and agile methodology. The waterfall model involves sequential phases from requirements to maintenance. Agile methodology values individuals, working software, customer collaboration, and responding to change. The document also outlines the roles, principles, and process flow of agile development including user stories, iterations, daily stand-ups, and continuous integration.
This document discusses the agile tools available in Visual Studio 2010. It provides an overview of Visual Studio 2010's capabilities for managing the entire software development lifecycle using agile methodologies like Scrum. Key features highlighted include improved support for agile processes like Scrum through templates and work item tracking, reporting and planning tools, and tight integration across the development lifecycle from requirements through deployment. The document argues that Visual Studio 2010's agile tools can help teams overcome complexity, improve quality, increase transparency, facilitate collaboration, and reduce risk through a lightweight and customizable approach.
This is take two of the presentation, some things added, some removed, but still the regurgitation is best..
The purpose is to raise your awareness of software architecture in light of modern day agile development. Disciplines to incorporate and reconsider
Presented at the BEACON 2017 conference at Hyderabad, India on December 1 - 3, 2017; this session revisits a presentation originally delivered in 2008 with updated tools reflecting a more up-to-date Agile engineering environment.
In October 2009, I presented a well-received session entitled An Agile Engineering Environment (in 59 Minutes or Less) at an Agile conference in Chengdu, China. From 2009 – 2015 the environment presented in that session remained fundamentally unchanged as our primary internal development environment. By 2015, however, we began seeing the emergence of new tools which build upon the basic premises of that environment, but enable an even more robust environment to be established even more quickly and independently than the 59-minute environment realized in the 2009 session.
In this session, we will briefly introduce the original configuration and see how modern tooling and techniques enable the improved environment to be established in a fraction of the time, enabling even greater agility in our engineering environment.
In October 2009, I presented a well-received session entitled An Agile Engineering Environment (in 59 Minutes or Less) at an Agile conference in Chengdu, China. From 2009 – 2015 the environment presented in that session remained fundamentally unchanged as our primary internal development environment. By 2015, however, we began seeing the emergence of new tools which build upon the basic premises of that environment, but enable an even more robust environment to be established even more quickly and independently than the 59-minute environment realized in the 2009 session.
In this session, we will briefly introduce the original configuration and see how modern tooling and techniques enable the improved environment to be established in a fraction of the time, enabling even greater agility in our engineering environment.
This document discusses test-driven development (TDD) and acceptance test-driven development (ATDD). It defines TDD as a process of first writing a test, then code to pass the test, and refactoring code while relying on tests. ATDD helps ensure correct external features by defining tests for customer requirements. The document outlines benefits like reduced bugs and increased confidence. It also discusses tools that support TDD/ATDD like unit testing frameworks, FitNesse for acceptance tests, continuous integration, and code coverage tools.
Critical Capabilities to Shifting Left the Right WaySmartBear
The concept of testing earlier in the SDLC isn't new, but the term "shift left" has reignited its importance. See how shifting left can help you, and how to do it right.
Lap around ALM with Visual Studio and TFS 2013Paul Hacker
This document discusses features and capabilities of Visual Studio 2013 and Team Foundation Server 2013 for application lifecycle management. It covers areas like agile management, developer tools, testing, feedback, DevOps, release management, and using TFS in the cloud. The presentation agenda includes overviews of TFS, agile portfolio management, code review requests, web-based testing tools, integrating System Center Operations Manager with TFS, release management automation, and capabilities when using Visual Studio Online such as automated builds and load testing.
Software Engineering- Crisis and Process ModelsNishu Rastogi
The document discusses various software engineering process models including the waterfall model, iterative waterfall model, prototyping model, evolutionary model, rapid application development model, and spiral model. It provides details on the key activities and stages in each model's software development life cycle. The document also compares the different models and discusses when each may be best applied based on factors like the problem's understandability, decomposability into modules, and tolerance for incremental delivery.
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.
This document discusses BSG's approach to agile software development. It covers their use of agile methodologies like Scrum, test-driven development, behavior-driven development, and pair programming. It also describes their testing strategy, which uses a hybrid of BDD and TDD with a domain specific language. Tests are written at multiple levels, from acceptance to unit, and are run locally and through continuous integration with Jenkins.
This document discusses agile engineering practices used to develop software iteratively. It recommends practices like test-driven development, continuous integration, refactoring, collective code ownership, and pair programming. It emphasizes automating tests, keeping designs and documentation simple, evolving designs over time based on needs, and inspecting and adapting practices based on measurements and retrospectives. The goal is to deliver working software frequently that satisfies customers' needs.
RTC & Work Item Customization OverviewBharat Malge
Rational Team Concert Introduction
- Rational Team Concert (RTC) is a Jazz-based product that allows teams to collaborate using integrated planning, work item management, source control, builds, dashboards and reports.
- It supports customization of processes and has Eclipse, Visual Studio and web-based interfaces.
- RTC addresses challenges of distributed teams through visibility into team members, artifacts, responsibilities and processes within a project.
Behavior Driven Development—A Guide to Agile Practices by Josh EastmanQA or the Highway
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
The document discusses various agile concepts including:
- Agile software development focuses on adaptability, incremental delivery, and customer satisfaction. Common techniques include extreme programming, refactoring, and test-first development.
- The Agile Manifesto values individuals, working software, customer collaboration, and responding to change over processes, documentation, contracts, and strict plans.
- Site reliability engineering uses software tools to automate infrastructure tasks like monitoring and deployment. Scrum organizes projects into sprints and roles like product owners and scrum masters. Kanban uses boards to visualize and optimize workflow. Lean aims to eliminate waste from processes through continuous improvement.
The document discusses modern architecture and its key principles. It covers programming paradigms like object-oriented programming and functional programming and how they relate to architecture. It also discusses SOLID design principles, components, attributes of modern architecture like loose coupling and high cohesion, and patterns like domain-driven design and event sourcing. Specific architectures like microservices are mentioned. Case studies are presented and questions are posed about architectural topics.
Similar to Presentation of agile engineering practices (20)
The mythical technical debt. (Brooke, please, forgive me)Roberto Bettazzoni
The Mythical Technical Debt
(Brooke, please, forgive me.)
<This talk is designed for a technical audience>
In software-intensive systems development, we often face trade-offs between speed and long-term maintainability. These trade-offs accumulate as technical debt, the hidden cost of short-term decisions that can impact future development.
Technical debt goes beyond the initial choices made when creating software. It encompasses design decisions, coding practices, or anything that might hinder future development efforts. By effectively identifying and managing this debt, we can build robust and scalable software systems.
In this talk, we'll explore different types of technical debt and their impact on projects. We'll delve into practical methods to identify, measure, and reduce it. Finally, we'll see how to turn technical debt into an advantage, using it as a springboard for innovation with real-world examples.
Giornat Mondiale della Retrospettiva 2020 - Riassunto Meetup RemotoRoberto Bettazzoni
Documento di riassunto generale dal meetup remoto per la Giornata mondiale della retrospettiva. Questo comprende la presentazione, i riassunti prodotti dai tavoli virtuali specializzati nella diverse fasi della retro, il risultato del feedback finale dei partecipanti, la lista dei riferimenti citati ed altri sull’argomento.
https://zoom.us/meeting/944245270
https://www.agile42.com/it/blog/2020/03/20/meetup-world-retrospective-day/
https://www.agile42.com/it/blog/2020/04/04/la-retrospettiva-sulla-retrospettiva/
Complexity indicators: estimation precision and test typesRoberto Bettazzoni
This presentation is part of "Continuous change" (the practice to continuosly change the way of working according to the continuous change of the products needs)
This presentation is focused on the description of 2 complexity indicators: the user stories estimation precision and the type of the test that the team can plan|realize
Some of the most advanced technical practices allow to get sustainable and effective benefits only if you use them properly. Unfortunately the inertia in adapting the way of working to the changing needs can thwart any technological advantage.
In this talk I discuss the reason why an appropriate change of the way of working is a non postponable need. I also present some methods and indicators to help you adapting your way of working to the product’s needs, your company's culture and the technical practices.
Test-driven development (TDD) is an agile practice that involves writing automated tests before writing code (test-first programming), then refactoring the code and designing incrementally. The TDD process involves adding a test, running tests to see failures, writing code to pass the test, and refactoring code. As an example, an employee wants to use an expenses program via a web interface to collect expenses from any device. The tasks would be to create a web server, HTML page, read HTTP parameters, test the legacy expenses program, refactor it to connect to the HTML commands, and build the web application.
Cynefin Lego Game
[sessione hands-on presentata insieme a Gaetano Mazzanti]
Il Cynefin Lego Game è stato creato dai coach di Agile 42 nel 2011, è stato presentato in diverse conferenze ed utilizzato in diversi roll-out, anche in Italia.
La versione 2.0 in italiano e' l'evoluzione della versione originale http://www.agile42.com/en/blog/2011/12/25/cynefin-lego-game/
Rispetto all'originale ha alcune parti diverse, soprattutto le attivita per i contesti complesso e caotico.
One hour presentation about pairing activities (programming and training).
Pair programming description about 10 min.
Game "pair story writing" about 25 min.
2006 Talk di sera ERLUG (Emilia Romagna Linux User Group)
Realizzati insieme ad Ilias Bartolini . 5a e ultima parte
Presentazione di XP vers. 2.0 come descritta dal secondo libro bianco [nota: all'epoca era stato appena pubblicato ... riferimenti non precisi :-) ]
2006 Talk di sera ERLUG (Emilai Romagna Linux User Group)
Realizzati insieme ad Ilias Bartolini . 4a parte
Rapporti tra le metodologie e pratiche Agile ed il movimento Open Source
2006 Talk di sera ERLUG (Emilia Romagna Linux User Group)
Realizzati insieme ad Ilias Bartolini . 3a parte
Presentazione della tecnica del code kata con esempio non riportato nella slide per problemi di copyright
Introduzione alle metodologie e pratiche Agili ... ma l'agile c'entra qualcos...Roberto Bettazzoni
2006
Prima serata di una serie di Talk serali all' ERLUG (Emilia Romagna Linux User Group) Presentazione delle Metodologie Agili (confronto con la situazione esistente)
Presentazione delle Pratiche Agili
Esempio d'applicazione di tecniche Agili
Agile e OSS distribuito
eXtreme Programming
Scrum is a simple framework for delivering working software in short iterations called sprints, usually lasting 30 days. It has three roles: Product Owner who prioritizes features in a backlog, Scrum Master who facilitates the process, and a self-organizing team. The team works in sprints using ceremonies of sprint planning, daily stand-ups, sprint review and retrospective to inspect and adapt their process. The goal is working software over documentation and responding to change over following a plan.
Sessione presentata all'Italian Agile Day 19 nov 2010
BDD Live Show
In questa sessione simuleremo una breve sessione di BDD su un problema “reale” (una semplice applicazione da riga di comando). Durante la presentazione useremo un mix di tecnologie (tra le quali Ruby e Python), ma la sessione sarà comprensibile anche a chi non conosce questi linguaggi.
Intervento al linux day 2013
I tools di programmazione per le device mobili sono quasi all'altezza di quelli per Linux; è giunta quindi l'ora di cimentarsi nella scrittura di script e programmi per telefoni: è facile, divertente ed i risultati sono interessanti.
In venti minuti vi mostrerò come si può scrivere un semplice programma per un telefono o tablet Android utilizzando Python e tools open source
The document discusses lean tools like value stream mapping and Kanban. It provides examples of using value stream mapping to visualize and analyze the flow of work in a software development process and identify areas for improvement like reducing wait times. Kanban is introduced as a tool that uses visual cues and limits on work-in-progress to control flow and facilitate continuous improvement through collaborative experiments. Examples are given of using a Kanban board to visualize different scenarios and how work would flow through the process.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Presentation of agile engineering practices
1. Presentation of
Agile Engineering Practices
Overview of the different aspects of agile engineering practices (AEP)
and how they can be adopted in agile teams
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
2. About us
Niels Verdonk Roberto Bettazzoni
eXtreme programming Trainers
niels.verdonk@agile42.nl
linkedin.com/in/nverdo
@nverdo
Agile Coaches
roberto.bettazzoni@agile42.it
linkedin.com/in/robertobettazzoni
@bettazzoni
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
3. Presentation of Agile Engineering Practices
• Introduction
• Presentation of the level of knowledge
• Presentation of Agile Engineering Practices
• Presentation on our way to approach these practices
• Explanation of two different activities happened in Siemens
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
4. A.E.P. entry level
Personal point of view:
• your production code is tested (in some ways)
• you can test your code (in some way)
• you can access and understand all the part of the project of your competence
• you can repeat the building of any version of your project
• you can do and undo any modification to the code of your competence
Project point of view:
• The product is tested (in some way)
• The production code is tested (in some ways)
• The contents of any releases is known
• Any releases can be re-build
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
5. eXtreme Programming practices
Sit Together
Whole Team
Informative Workspace
Energized Work
Weekly Cycle
Quarterly Cycle
Slack
User Stories
Pair Programming
Refactoring
Ten Minute Build
Continuous Integration
T.D.D. (was Test first)
Incremental Design
font: Extreme Programming Explained: Embrace Change 2nd Ed. (2004)
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
6. eXtreme Programming practices
Sit Together
Whole Team
Informative Workspace
Energized Work
Weekly Cycle
Quarterly Cycle
Slack
User Stories
Pair Programming
Refactoring
Ten Minute Build
Continuous Integration
T.D.D. (was Test first)
Incremental Design
AEP
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
7. A.E.P. expert level
Personal point of view
•You produce code that is working as expected, easily readable and properly tested.
•You know your project[s]. You can modify any part that concern your skills and you can overview the
entire project to a new member
•You have a basic understanding of the Software Build, Unit Test and Continuous Integration tools and you
can explain it to a new team member using shared lectures or pair programming
Project point of view
•There are Acceptance Tests created for any new US completed
•The successful build implies the successful run of all the tests of the project (Unit, Functional, Acceptance)
•The build are completely automated. The tests that can be automated are completely automated. Both
are under Continuous Integration.
•Collective code ownership: no procedure or access restrict or limits changes to the code, so every coder
could understand and change any part of the project. In this way no person or group of people could
become a bottleneck.
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
8. AEP an overview
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
9. Agile42 way to facilitate application of AEP
• presentations
• trainings
class training
dojo
workshop
• mentoring
• coaching
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
10. Some training examples
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
11. Hot topic on “Pair Training”
1hour, 10-20 participants - presentation - 4C schema
Agenda
• Guess 3 pair training or coaching characteristics. (C1: connection activity)
• Pair Training and Coaching (C2: concept)
• Pair Programming references (C2: concept)
• Pair Story Writing (C3: Concrete practice. Activity)
• Share your opinion (C4: Conclusion)
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License
12. Unit test Awareness Dojo in C#
3 hours 6-12 participants
Agenda
• Unit Test in a very small nutshell
• The Dojo rules
• Unit Tests demo
• 1st round on Kata (25 min.)
• 2nd round on Kata (25 min.)
• Code sharing
• Retrospective
agile42 | We advise, train and coach companies building software | www.agile42.com | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License