Timeboxed releases - Peter Antman
•Download as ODP, PDF•
0 likes•323 views
The document discusses principles for agile software development and releasing software in a continuous manner. It outlines five steps to achieve this: 1) Learn how to plan in small iterations, 2) Organize delivery to keep focus and avoid issues, 3) Automate everything for traceability, 4) Test everything continuously, and 5) Always integrate code to ensure releases are always releasable. The goal is to release software early and often through a process of timeboxed iterations, continuous integration, and automated testing.
Report
Share
Report
Share
![[email_address]](https://image.slidesharecdn.com/1-timeboxedreleases-peterantman-100110092329-phpapp02/85/Timeboxed-releases-Peter-Antman-1-320.jpg)
Recommended
WordPress Upgrades: Read, Set, Go!
Check out Dustin Meza's, Director of Customer Experience Operations at WP Engine, presentation from Word Camp Boston. Enjoy!
4Developers 2015: Twoja własna profesjonalna kontrolka WPF - tak jak robią to...
Marcin Kawalerowicz, Marcin Słowik
Language: English
Używałeś już kiedyś kontrolek takich producentów jak Telerik, Infragistics czy DevExpress? Pewnie tak. Zastanawiałeś się jak opracowują oni produkty tego typu? Zapewne nie za bardzo. My zadaliśmy sobie trud, żeby przejrzeć jak tworzone są profesjonalne kontrolki WPF. Podczas sesji pokarzemy Ci jak stworzyć wysokiej klasy kontrolkę. Zajmiemy się templatem w XAMLu oraz oprogramujemy całość w C#. Gotową kontrolkę będziesz mógł użyć w wielu swoich projektach.
Continuous delivery
This document discusses continuous delivery and provides steps to achieve it. Continuous delivery aims to provide fast, high quality feedback at multiple levels through the development process. It recommends having automated source control, builds, testing, deployment, monitoring and self-healing systems. The key steps are to have automated builds that pass all tests with each change, to measure and improve code quality, to implement automated validation of both code and features through tests, and to deploy and monitor applications automatically to catch any issues. Containers can help developers deploy applications for testing more easily. The overall goal is to establish a pipeline that allows for frequent, low-risk deployments.
Putting the pro in programmer
This document provides tips for improving development processes and becoming a pro programmer. It recommends using version control like Git and hosting code online or yourself. It also suggests using Vagrant to create consistent development environments across platforms. Other tips include using bug trackers integrated with version control, enforcing adding ticket IDs to commits, writing tests for bug fixes, setting up continuous integration with Jenkins, and monitoring systems for alerts. The overall message is that these practices can help programmers write better code and work more efficiently.
Denver Salesforce DUG DF 2018 roundup
The document summarizes a Denver Salesforce DUG meeting agenda and Dreamforce session roundups from various members.
The agenda includes group updates, Dreamforce session highlights from members, and a group goals brainstorming session. Under group updates, new community and leadership details are provided.
Key Dreamforce session takeaways are summarized for topics like the IdeaExchange platform changes, Visual Studio Code tips, Salesforce DX, Lightning components testing, Apex testing best practices, and new Apex features. The document aims to share top sessions and insights from the Dreamforce conference.
Continuous integration introduction
This document discusses continuous integration (CI), including key concepts like integrating code changes frequently through automation to detect errors early. CI aims to make the development and testing environments similar to production. The document outlines the developer, QA, and team aspects of CI and provides examples of basic CI workflows and tools like Jenkins, Travis-CI, and GitLab-CI. An effective CI follows the "five-minute rule" where a build is triggered after a code change and validation is completed within five minutes with failure notifications. CI helps enable continuous delivery pipelines by frequently testing integrated changes.
Continuous Quality with Postman
This document summarizes a presentation on continuous quality testing with Postman. The presentation introduced continuous quality as a systematic approach to finding and fixing defects during development. It covered recommended testing practices like running tests locally and automating tests. The presentation demonstrated how to extend Postman with libraries, use monitors for regression testing, and automate testing in CI/CD pipelines with Newman. Additional resources on testing with Postman were provided.
CI with TFS
Continuous integration (CI) with TFS involves integrating code changes frequently through automated builds and tests upon each commit to the single source repository. This allows for rapid feedback on the code quality and catches issues early. The automated builds should be fast and make their output and results easily visible. To start, create a nightly automated build, add test cases, speed it up, and trigger builds on commit.
Recommended
WordPress Upgrades: Read, Set, Go!
Check out Dustin Meza's, Director of Customer Experience Operations at WP Engine, presentation from Word Camp Boston. Enjoy!
4Developers 2015: Twoja własna profesjonalna kontrolka WPF - tak jak robią to...
Marcin Kawalerowicz, Marcin Słowik
Language: English
Używałeś już kiedyś kontrolek takich producentów jak Telerik, Infragistics czy DevExpress? Pewnie tak. Zastanawiałeś się jak opracowują oni produkty tego typu? Zapewne nie za bardzo. My zadaliśmy sobie trud, żeby przejrzeć jak tworzone są profesjonalne kontrolki WPF. Podczas sesji pokarzemy Ci jak stworzyć wysokiej klasy kontrolkę. Zajmiemy się templatem w XAMLu oraz oprogramujemy całość w C#. Gotową kontrolkę będziesz mógł użyć w wielu swoich projektach.
Continuous delivery
This document discusses continuous delivery and provides steps to achieve it. Continuous delivery aims to provide fast, high quality feedback at multiple levels through the development process. It recommends having automated source control, builds, testing, deployment, monitoring and self-healing systems. The key steps are to have automated builds that pass all tests with each change, to measure and improve code quality, to implement automated validation of both code and features through tests, and to deploy and monitor applications automatically to catch any issues. Containers can help developers deploy applications for testing more easily. The overall goal is to establish a pipeline that allows for frequent, low-risk deployments.
Putting the pro in programmer
This document provides tips for improving development processes and becoming a pro programmer. It recommends using version control like Git and hosting code online or yourself. It also suggests using Vagrant to create consistent development environments across platforms. Other tips include using bug trackers integrated with version control, enforcing adding ticket IDs to commits, writing tests for bug fixes, setting up continuous integration with Jenkins, and monitoring systems for alerts. The overall message is that these practices can help programmers write better code and work more efficiently.
Denver Salesforce DUG DF 2018 roundup
The document summarizes a Denver Salesforce DUG meeting agenda and Dreamforce session roundups from various members.
The agenda includes group updates, Dreamforce session highlights from members, and a group goals brainstorming session. Under group updates, new community and leadership details are provided.
Key Dreamforce session takeaways are summarized for topics like the IdeaExchange platform changes, Visual Studio Code tips, Salesforce DX, Lightning components testing, Apex testing best practices, and new Apex features. The document aims to share top sessions and insights from the Dreamforce conference.
Continuous integration introduction
This document discusses continuous integration (CI), including key concepts like integrating code changes frequently through automation to detect errors early. CI aims to make the development and testing environments similar to production. The document outlines the developer, QA, and team aspects of CI and provides examples of basic CI workflows and tools like Jenkins, Travis-CI, and GitLab-CI. An effective CI follows the "five-minute rule" where a build is triggered after a code change and validation is completed within five minutes with failure notifications. CI helps enable continuous delivery pipelines by frequently testing integrated changes.
Continuous Quality with Postman
This document summarizes a presentation on continuous quality testing with Postman. The presentation introduced continuous quality as a systematic approach to finding and fixing defects during development. It covered recommended testing practices like running tests locally and automating tests. The presentation demonstrated how to extend Postman with libraries, use monitors for regression testing, and automate testing in CI/CD pipelines with Newman. Additional resources on testing with Postman were provided.
CI with TFS
Continuous integration (CI) with TFS involves integrating code changes frequently through automated builds and tests upon each commit to the single source repository. This allows for rapid feedback on the code quality and catches issues early. The automated builds should be fast and make their output and results easily visible. To start, create a nightly automated build, add test cases, speed it up, and trigger builds on commit.
Extreme Programming - to the next-level
This document discusses taking extreme programming principles to the next level by turning traditional practices "up to 11". It explores several ideas for achieving faster feedback including mob programming, continuous deployment, hypothesis-driven user stories, shared product ownership, monitoring-driven development, and continuous learning. The author asks the reader to consider which ideas may work to implement in their organization this month.
Introduction to Automated Testing
Learn about the benefits of writing unit tests. You will spend less time fixing bugs and you will get a better design for your software. Some of the questions answered are:
Why should I, as a developer, write tests?
How can I improve the software design by writing tests?
How can I save time, by spending time writing tests?
When should I write unit tests and when should I write system tests?
Fast end-to-end-tests
This document summarizes Lars Thorup's presentation on fast end-to-end tests. It discusses the drawbacks of traditional end-to-end tests like being slow, imprecise, complicated and fragile. Unit tests are faster but rely on mocked dependencies. The presentation demonstrates a way to automatically generate mocks to test applications from end-to-end very quickly while avoiding the downsides of mocks. The demo shows a Node.js app with front-end and back-end tested at almost 100 end-to-end tests per second.
Episode 5 - Writing unit tests in Salesforce
The document provides an agenda for a session on writing unit tests in Apex. It discusses why unit tests are important in Apex, how to structure test classes, best practices for testing, and resources for learning more about Apex testing. The session demonstrates executing unit tests and techniques like accessing private members, running tests within limits, and creating test data. Attendees are encouraged to ask questions during the last 15 minutes.
Automated Performance Testing
If you are like most test driven developers, you write automated tests for your software to get fast feedback about potential problems. Most of the tests you write will verify the functional behaviour of the software: When we call this function or press this button, the expected result is that value or that message.
But what about the non-functional behaviour, such as performance: When we perform this query the expected speed of getting results should be no more than that many milliseconds. It is important to be able to write automated performance tests as well, because they can give us early feedback about potential performance problems. But expected performance is not as clear-cut as expected results. Expected results are either correct or wrong. Expected performance is more like a threshold: If the performance is worse than this, we want the test to fail.
TFS Build - Continuous Integration
Continuous integration with TFS allows teams to integrate code changes frequently through an automated build and testing process. It involves setting up a single source code repository in TFS and automating the build to verify code and unit tests upon each commit, helping to build software faster. The process starts by creating an automated nightly build and adding test cases, then configuring the system to trigger a build with each check-in. Additional steps include implementing code analysis, metrics collection, and alerts to notify teams of issues or deployments.
Developer day - AWS: Fast Environments = Fast Deployments
The document discusses how AWS enables fast and flexible deployments through automation. It outlines problems with manual and unique server deployments like breakages and lack of change management. The solution presented is to automate the entire process through continuous integration and deployment tools like Jenkins, GitHub, Grunt, and AWS CloudFormation. This treats servers as identical and deployable resources, ensures all code is tested and production-ready, and allows for boring but successful automated deployments on demand.
Continuous Delivery - In 10 Minutes
Continuous delivery involves three phases: (1) continuous integration to integrate code changes, (2) continuous elevation to deliver complete software packages through an automated approval workflow, and (3) elevated CI where multiple teams participate in continuous integration and elevation. The goal is to streamline the process from code check-in to delivery to customers.
DevQAOps - Surviving in a DevOps World
Talk given by Winston Laoh at the QA/LA meetup hosted at Q Los Angeles. The goal of the presentation was to inform and persuade test related engineers on how to integrate into DevOps organizations.
Baptism By Fire - Why production issues make you a better developer
This document discusses lessons learned from production issues at a mobile analytics company. It summarizes three main production incidents:
1) An incident where slow queues and missing monitoring on message brokers caused service degradation. They learned to monitor all internal queues and implement sliding buffers.
2) Traffic doubling unexpectedly exposed issues with shutting down servers and manual input analysis. They created tools for automatic scaling and input handling.
3) A minor code change caused major breaks due to insufficient knowledge of their Python web handler and scaling limitations. They learned to thoroughly understand their systems and investigate issues more deeply.
The overall lessons are to stay calm during incidents, try quick fixes, escalate issues to the team, and ensure proper monitoring,
Unit 1 final activity
This document provides instructions for a final activity for a history unit on nationalism, industrialization, and imperialism. Students must choose one of the three topics they have already written a paragraph on, have classmates proofread it, and write a final draft in MS Word. They then need to create an account and upload their paragraph to Turnitin.com. A test on unit 1 will be administered on August 28, so students should review the study guide to prepare.
Adrian marinica continuous integration in the visual studio world
This document discusses continuous integration practices in the Visual Studio world. It defines continuous integration as integrating work frequently, usually daily, with automated testing to quickly detect errors. Successful continuous integration requires maintaining a single source repository, automating builds and testing, committing to the mainline daily, and automating deployment. Examples are given of companies that continuously integrate and deploy many times a day. Challenges include the effort required to set up systems to enable continuous integration and ensure sufficient test coverage. Release management with Visual Studio and Team Foundation Server is discussed as a way to facilitate deploying to multiple environments.
SaaS Project Management
This document proposes a team-based project management system for continuously developed SaaS products. It acknowledges limitations in assuming interchangeable team members, constant velocity, definite projects or known requirements. The proposed system includes releases, iterations, calendars, team members, teams, work items and a work viewer to provide visibility into priorities and schedules across specialized teams and evolving work.
Load-testing 101 for Startups with Artillery.io
An overview of what you need to know about load-testing as a pre-launch startup. Slides for my "Load-testing For Startups" workshop
Going serverless at Comic Relief
This document summarizes Comic Relief's transition to a serverless architecture for its donations platform. Some key points:
- Comic Relief raises over £1 billion for charity campaigns and is moving its technical landscape to be fully serverless.
- Benefits of going serverless include increased speed of iteration, needing fewer engineers, and no costs when not in use.
- The donations platform donation.comicrelief.com was rebuilt on a serverless architecture using services like AWS Lambda and API Gateway.
- Testing and deployment were changed to focus on feature pipelines to prototype and production pipelines to deploy continuously with testing.
- Observability, alerting, scalability, redundancy and resiliency were all built
Agile Engineering Sparker GLASScon 2015
This document provides information about an expert in Agile software development practices named Stephen Ritchie. It summarizes his experience, certifications, and areas of focus including Agile coaching. The document recommends practices for implementing Agile such as version control, continuous integration, automated testing, and deployment automation. It lists tools that can be used for each practice and recommends an order for implementation. The document also discusses benefits of practices like reduced defect rates and faster deployments.
Jenkins Test Automation with codeBeamer ALM
Testing is a vital part of software development, since it is about finding the software bugs. You can choose from automated and manual testing. Automated testing is good for large projects with many systems users, while manual testing is good for smaller projects or for companies with insufficient budget.
You can also run Continuous testing. The purpose of Continuous testing and continuous integration is to enable continuous delivery, the end goal of which is to accelerate the delivery of high quality software.
Automation is essential for Continuous Testing but Automated Testing is not the same as Continuous Testing.
Try Jenkins Test Automation with codeBeamer ALM. Jenkins is an open source continuous integration tool written in Java. Jenkins provides continuous integration services for software development.
How to Upgrade to the Newest Shiniest Django Version
This document summarizes Susan's presentation on upgrading Django projects. The presentation covered:
- Why upgrades are important for getting new features, fixes and security updates.
- The steps involved in upgrading include running tests, fixing broken tests one by one, checking that fewer tests fail with each new version, verifying the UI still works, and editing deployment files.
- Challenges include dependencies breaking, release notes documenting changes that require code updates, and the repetitive nature of fixing tests across multiple versions.
- The key takeaways are to upgrade one version at a time, run and fix tests with each version, read release notes, break tasks into small steps, and use checklists to track progress
Episode 18 - Asynchronous Apex
This document discusses asynchronous Apex in Salesforce, including future methods and queueable Apex. It provides an overview of asynchronous Apex, why it is used, different asynchronous Apex approaches, and compares future methods and queueable Apex. The agenda includes explaining asynchronous Apex, reasons for using it like avoiding governor limits and allowing callouts from triggers, asynchronous governor limits, future methods, queueable Apex, and a demo.
Put "fast" back in "fast feedback"
One of the cornerstones in Agile development is fast feedback. For engineering, "fast" means "instantly" or "in 5 minutes", not "tomorrow" or "this week". Your engineering practices should ensure that you can answer yes to most of the following questions:
- Do we get all test results in less than 5 minutes after a commit?
- Is our code coverage more than 75% for both front-end and back-end?
- Can we start exploratory testing in less than 15 minutes after a commit?
- Do all our tests pass more than 90% of our commits?
This talk will give you practical advice on how to get to "yes, we get fast feedback".
DevOps: Automate all the things
A whistlestop tour of how we use DevOps at the University of Warwick to continuously deliver software
Ssw forte-agile-seminar
This document provides an overview and summary of Steve Forte's half-day Agile seminar presented by SSW. The seminar covers topics including an introduction to Agile and Scrum, Agile estimation, Agile and offshore teams, and Agile tools. Attendees can ask questions throughout the interactive seminar.
More Related Content
What's hot
Extreme Programming - to the next-level
This document discusses taking extreme programming principles to the next level by turning traditional practices "up to 11". It explores several ideas for achieving faster feedback including mob programming, continuous deployment, hypothesis-driven user stories, shared product ownership, monitoring-driven development, and continuous learning. The author asks the reader to consider which ideas may work to implement in their organization this month.
Introduction to Automated Testing
Learn about the benefits of writing unit tests. You will spend less time fixing bugs and you will get a better design for your software. Some of the questions answered are:
Why should I, as a developer, write tests?
How can I improve the software design by writing tests?
How can I save time, by spending time writing tests?
When should I write unit tests and when should I write system tests?
Fast end-to-end-tests
This document summarizes Lars Thorup's presentation on fast end-to-end tests. It discusses the drawbacks of traditional end-to-end tests like being slow, imprecise, complicated and fragile. Unit tests are faster but rely on mocked dependencies. The presentation demonstrates a way to automatically generate mocks to test applications from end-to-end very quickly while avoiding the downsides of mocks. The demo shows a Node.js app with front-end and back-end tested at almost 100 end-to-end tests per second.
Episode 5 - Writing unit tests in Salesforce
The document provides an agenda for a session on writing unit tests in Apex. It discusses why unit tests are important in Apex, how to structure test classes, best practices for testing, and resources for learning more about Apex testing. The session demonstrates executing unit tests and techniques like accessing private members, running tests within limits, and creating test data. Attendees are encouraged to ask questions during the last 15 minutes.
Automated Performance Testing
If you are like most test driven developers, you write automated tests for your software to get fast feedback about potential problems. Most of the tests you write will verify the functional behaviour of the software: When we call this function or press this button, the expected result is that value or that message.
But what about the non-functional behaviour, such as performance: When we perform this query the expected speed of getting results should be no more than that many milliseconds. It is important to be able to write automated performance tests as well, because they can give us early feedback about potential performance problems. But expected performance is not as clear-cut as expected results. Expected results are either correct or wrong. Expected performance is more like a threshold: If the performance is worse than this, we want the test to fail.
TFS Build - Continuous Integration
Continuous integration with TFS allows teams to integrate code changes frequently through an automated build and testing process. It involves setting up a single source code repository in TFS and automating the build to verify code and unit tests upon each commit, helping to build software faster. The process starts by creating an automated nightly build and adding test cases, then configuring the system to trigger a build with each check-in. Additional steps include implementing code analysis, metrics collection, and alerts to notify teams of issues or deployments.
Developer day - AWS: Fast Environments = Fast Deployments
The document discusses how AWS enables fast and flexible deployments through automation. It outlines problems with manual and unique server deployments like breakages and lack of change management. The solution presented is to automate the entire process through continuous integration and deployment tools like Jenkins, GitHub, Grunt, and AWS CloudFormation. This treats servers as identical and deployable resources, ensures all code is tested and production-ready, and allows for boring but successful automated deployments on demand.
Continuous Delivery - In 10 Minutes
Continuous delivery involves three phases: (1) continuous integration to integrate code changes, (2) continuous elevation to deliver complete software packages through an automated approval workflow, and (3) elevated CI where multiple teams participate in continuous integration and elevation. The goal is to streamline the process from code check-in to delivery to customers.
DevQAOps - Surviving in a DevOps World
Talk given by Winston Laoh at the QA/LA meetup hosted at Q Los Angeles. The goal of the presentation was to inform and persuade test related engineers on how to integrate into DevOps organizations.
Baptism By Fire - Why production issues make you a better developer
This document discusses lessons learned from production issues at a mobile analytics company. It summarizes three main production incidents:
1) An incident where slow queues and missing monitoring on message brokers caused service degradation. They learned to monitor all internal queues and implement sliding buffers.
2) Traffic doubling unexpectedly exposed issues with shutting down servers and manual input analysis. They created tools for automatic scaling and input handling.
3) A minor code change caused major breaks due to insufficient knowledge of their Python web handler and scaling limitations. They learned to thoroughly understand their systems and investigate issues more deeply.
The overall lessons are to stay calm during incidents, try quick fixes, escalate issues to the team, and ensure proper monitoring,
Unit 1 final activity
This document provides instructions for a final activity for a history unit on nationalism, industrialization, and imperialism. Students must choose one of the three topics they have already written a paragraph on, have classmates proofread it, and write a final draft in MS Word. They then need to create an account and upload their paragraph to Turnitin.com. A test on unit 1 will be administered on August 28, so students should review the study guide to prepare.
Adrian marinica continuous integration in the visual studio world
This document discusses continuous integration practices in the Visual Studio world. It defines continuous integration as integrating work frequently, usually daily, with automated testing to quickly detect errors. Successful continuous integration requires maintaining a single source repository, automating builds and testing, committing to the mainline daily, and automating deployment. Examples are given of companies that continuously integrate and deploy many times a day. Challenges include the effort required to set up systems to enable continuous integration and ensure sufficient test coverage. Release management with Visual Studio and Team Foundation Server is discussed as a way to facilitate deploying to multiple environments.
SaaS Project Management
This document proposes a team-based project management system for continuously developed SaaS products. It acknowledges limitations in assuming interchangeable team members, constant velocity, definite projects or known requirements. The proposed system includes releases, iterations, calendars, team members, teams, work items and a work viewer to provide visibility into priorities and schedules across specialized teams and evolving work.
Load-testing 101 for Startups with Artillery.io
An overview of what you need to know about load-testing as a pre-launch startup. Slides for my "Load-testing For Startups" workshop
Going serverless at Comic Relief
This document summarizes Comic Relief's transition to a serverless architecture for its donations platform. Some key points:
- Comic Relief raises over £1 billion for charity campaigns and is moving its technical landscape to be fully serverless.
- Benefits of going serverless include increased speed of iteration, needing fewer engineers, and no costs when not in use.
- The donations platform donation.comicrelief.com was rebuilt on a serverless architecture using services like AWS Lambda and API Gateway.
- Testing and deployment were changed to focus on feature pipelines to prototype and production pipelines to deploy continuously with testing.
- Observability, alerting, scalability, redundancy and resiliency were all built
Agile Engineering Sparker GLASScon 2015
This document provides information about an expert in Agile software development practices named Stephen Ritchie. It summarizes his experience, certifications, and areas of focus including Agile coaching. The document recommends practices for implementing Agile such as version control, continuous integration, automated testing, and deployment automation. It lists tools that can be used for each practice and recommends an order for implementation. The document also discusses benefits of practices like reduced defect rates and faster deployments.
Jenkins Test Automation with codeBeamer ALM
Testing is a vital part of software development, since it is about finding the software bugs. You can choose from automated and manual testing. Automated testing is good for large projects with many systems users, while manual testing is good for smaller projects or for companies with insufficient budget.
You can also run Continuous testing. The purpose of Continuous testing and continuous integration is to enable continuous delivery, the end goal of which is to accelerate the delivery of high quality software.
Automation is essential for Continuous Testing but Automated Testing is not the same as Continuous Testing.
Try Jenkins Test Automation with codeBeamer ALM. Jenkins is an open source continuous integration tool written in Java. Jenkins provides continuous integration services for software development.
How to Upgrade to the Newest Shiniest Django Version
This document summarizes Susan's presentation on upgrading Django projects. The presentation covered:
- Why upgrades are important for getting new features, fixes and security updates.
- The steps involved in upgrading include running tests, fixing broken tests one by one, checking that fewer tests fail with each new version, verifying the UI still works, and editing deployment files.
- Challenges include dependencies breaking, release notes documenting changes that require code updates, and the repetitive nature of fixing tests across multiple versions.
- The key takeaways are to upgrade one version at a time, run and fix tests with each version, read release notes, break tasks into small steps, and use checklists to track progress
Episode 18 - Asynchronous Apex
This document discusses asynchronous Apex in Salesforce, including future methods and queueable Apex. It provides an overview of asynchronous Apex, why it is used, different asynchronous Apex approaches, and compares future methods and queueable Apex. The agenda includes explaining asynchronous Apex, reasons for using it like avoiding governor limits and allowing callouts from triggers, asynchronous governor limits, future methods, queueable Apex, and a demo.
Put "fast" back in "fast feedback"
One of the cornerstones in Agile development is fast feedback. For engineering, "fast" means "instantly" or "in 5 minutes", not "tomorrow" or "this week". Your engineering practices should ensure that you can answer yes to most of the following questions:
- Do we get all test results in less than 5 minutes after a commit?
- Is our code coverage more than 75% for both front-end and back-end?
- Can we start exploratory testing in less than 15 minutes after a commit?
- Do all our tests pass more than 90% of our commits?
This talk will give you practical advice on how to get to "yes, we get fast feedback".
What's hot (20)
Developer day - AWS: Fast Environments = Fast Deployments
Developer day - AWS: Fast Environments = Fast Deployments
Baptism By Fire - Why production issues make you a better developer
Baptism By Fire - Why production issues make you a better developer
Adrian marinica continuous integration in the visual studio world
Adrian marinica continuous integration in the visual studio world
How to Upgrade to the Newest Shiniest Django Version
How to Upgrade to the Newest Shiniest Django Version
Similar to Timeboxed releases - Peter Antman
DevOps: Automate all the things
A whistlestop tour of how we use DevOps at the University of Warwick to continuously deliver software
Ssw forte-agile-seminar
This document provides an overview and summary of Steve Forte's half-day Agile seminar presented by SSW. The seminar covers topics including an introduction to Agile and Scrum, Agile estimation, Agile and offshore teams, and Agile tools. Attendees can ask questions throughout the interactive seminar.
Redistributable Intro To Scrum
Scrum is an agile framework for managing product development that focuses on iterative delivery of working software in short cycles called sprints. It involves self-organizing cross-functional teams, prioritized backlogs to track requirements, and daily stand-up meetings. The goal is to rapidly and repeatedly deliver the highest business value in the shortest time through a flexible, holistic and collaborative approach.
Introduction into Scrum
A Reusable Scrum Presentation. Introduce Scrum to your team, ScrumMaster and Product Owner. Created by mountaingoatsoftware.com
Continuous Delivery - the missing parts - Paul Stack
This document discusses continuous delivery and the missing parts of implementing it fully. It begins by defining continuous delivery as building, testing, and releasing software faster and more frequently. It outlines eight principles and four practices of continuous delivery. However, it notes that while developers may implement continuous delivery, the operations side is often missing parts like configuration management, immutable infrastructure, logging, metrics, monitoring, orchestration, and disaster recovery. A maturity model for continuous delivery is presented, and benefits like agility, faster recovery, more experimentation, and better products for customers are discussed.
Agile scrum induction
The document provides an overview of Agile and Scrum methodologies. It describes key concepts like the Agile manifesto, Scrum roles, ceremonies like daily stand-ups and retrospectives, and practices like user stories, estimation, and burn-down charts. The objective is to familiarize people with the basic principles and processes in Agile and Scrum development.
DevOps - Boldly Go for Distro
This is a 90 min talk with some exercises and discussion that I gave at the DHS Agile Expo. It places DevOps as a series of feedback loops and emphasizes agile engineering practices being at the core.
Waterfallacies V1 1
This presentation shows the development of methods that have made agile possible and discusses religious positions of CMMI-ers and Agilists
Intro To Scrum
I got a copy of this from the internet, and it was not written by me. yet I found this PPT quite helpful for you to understand the Scrum, so just enjoy it.
Just In Time Scalability Agile Methods To Support Massive Growth Presentation
Eric Reis and Chris Hondl's MySQL conference presentation on Just In Time Scalability. http://startuplessonslearned.blogspot.com/2008/09/just-in-time-scalability.html
Just In Time Scalability Agile Methods To Support Massive Growth Presentation
The document discusses techniques for scaling web applications to support massive growth using agile methods. It describes IMVU's architecture transformation from a small site built on open source tools to a large scaled architecture. Key techniques discussed include continuous integration and deployment, incremental changes, monitoring metrics, caching, sharding databases, and evolving data designs without downtime.
DX@Scale: Optimizing Salesforce Development and Deployment for large scale pr...
DX@Scale: Optimizing Salesforce Development and Deployment for large scale pr...Paris Salesforce Developer Group
In this talk, Azlam Abdulsalam and Ramzi Akremi will share their experiences in an ongoing Salesforce program how they build deploy and maintain 20+ unlocked packages through a highly optimised pipeline.An Introduction to Scrum
Scrum is an agile framework for managing product development that focuses on iterative delivery of working software. It involves short development cycles called sprints that typically last 2-4 weeks. Teams are self-organizing and work is planned and tracked using artifacts like a product backlog, sprint backlog, and daily stand-up meetings. The goal is to frequently deliver working, tested software to gain early customer feedback and continuously adapt to changing requirements.
How to organize qa process in agile speed
This document discusses organizing QA processes within an Agile Scrum team. It describes the project structure, team structure, and work processes of a distributed Scrum team supporting newspaper sites. Key QA activities in Scrum include negotiating quality, clarifying stories/tasks, ensuring acceptance tests verify quality, and providing estimates. Some challenges faced include frequent releases, lack of demos with business, communication issues, insufficient task descriptions, and not tracking QA work in sprints. Suggested solutions involve improving processes around releases, demos, communication, knowledge sharing, task descriptions, adding QA estimates to sprints, and breaking large tasks into smaller ones.
Agile_SDLC_Node.js@Paypal_ppt
This document discusses Agile practices, software development lifecycles (SDLC), and the use of Node.js at PayPal. It outlines typical Agile processes like sprint planning, backlog grooming, pair programming, mob programming, and retrospectives. It also describes PayPal's SDLC pipeline and use of Git flow for source control. Finally, it summarizes how PayPal adopted Node.js in 2012 and has since open sourced frameworks like Kraken.js and tools like Nemo.js while growing a large community of Node.js developers.
Agile Software Development with Scrum
This document summarizes an introduction to agile project management using Scrum. It defines Scrum and its key roles, processes, and artifacts. The document discusses the Scrum process including sprint planning meetings, daily stand-ups, and sprint reviews. It also covers Scrum artifacts like the product and sprint backlogs and burn down charts. The document aims to provide an overview of Scrum for those who write code or follow a software development process.
FOEN9001CognitoPoster
Philip Sewell worked as a middleware software developer at Cognito Ltd. His roles included bug fixing, implementing new features, and responding to emergencies. He developed a new Rabbit Retry Service to improve Cognito's message delivery system. The new service prevents failed messages from blocking the processing of other messages and allows modifying messages before retrying them. Cognito uses an agile development process with two-week sprints, daily stand-ups, end of sprint demos, and retrospectives.
IIBA and Solvera May Event - Testing w Agile slides
The document discusses agile principles and practices for software development and solution delivery. It outlines how scrum can be applied to both areas, including establishing story-level and unit tests, iterative development through sprints, and acceptance of features by business stakeholders. For solution delivery using packaged software, additional challenges are test automation and defining the product manager role given pre-existing packages.
Testaus 2014 -seminaari: Arto Kiiskinen, Mirasys Oy. Case Mirasys: Toiminnoil...
This document discusses testing challenges for a software company that develops a video management system product with frequent changes to requirements, priorities, and hardware platforms. The key challenges include long-term planning difficulties due to constantly changing priorities, limited testing resources compared to the size of the product and number of developers, and setup time for complex integration tests. It provides recommendations for achieving high team effectiveness through minimizing interruptions, focusing testing on individual stories, and establishing trust in story-level testing to reduce risks for major releases.
Scrum and Agile SDLC 101
The document provides an overview of Agile software development using Scrum. It describes Scrum as an Agile framework that focuses on delivering business value through short iterative development cycles called sprints. Key aspects of Scrum include self-organizing cross-functional teams, prioritized product backlogs maintained by a Product Owner, and regular sprint planning, daily standup, review and retrospective meetings facilitated by a Scrum Master.
Similar to Timeboxed releases - Peter Antman (20)
Continuous Delivery - the missing parts - Paul Stack
Continuous Delivery - the missing parts - Paul Stack
Just In Time Scalability Agile Methods To Support Massive Growth Presentation
Just In Time Scalability Agile Methods To Support Massive Growth Presentation
Just In Time Scalability Agile Methods To Support Massive Growth Presentation
Just In Time Scalability Agile Methods To Support Massive Growth Presentation
DX@Scale: Optimizing Salesforce Development and Deployment for large scale pr...
DX@Scale: Optimizing Salesforce Development and Deployment for large scale pr...
IIBA and Solvera May Event - Testing w Agile slides
IIBA and Solvera May Event - Testing w Agile slides
Testaus 2014 -seminaari: Arto Kiiskinen, Mirasys Oy. Case Mirasys: Toiminnoil...
Testaus 2014 -seminaari: Arto Kiiskinen, Mirasys Oy. Case Mirasys: Toiminnoil...
More from manssandstrom
Tillståndslös programmering devlin 2011
Presentation jag höll på DevLin 2011 om hur det är att gå över från att utveckla objekt- (klass)orienterat till att utveckla i funktionella språk exemplifierat med erlang.
Agile och Kanban på driftavdelningen - Tomas Bjorkholm
The document discusses using Kanban principles for operations teams. It describes some key characteristics of Kanban including limiting work in progress, visualizing workflow, and focusing on continuously improving lead time. Various examples of Kanban boards are provided, including ones tailored for non-cross functional teams and for breaking work into smaller stories less than one week. The Kanban process involves daily stand-ups, sprint planning and retrospectives to continuously improve.
More from manssandstrom (20)
Agile och Kanban på driftavdelningen - Tomas Bjorkholm
Agile och Kanban på driftavdelningen - Tomas Bjorkholm
Skala scrum med visuell planering från lean - Daniel Berg
Skala scrum med visuell planering från lean - Daniel Berg
Klyftan mellan nyutveckling och förvaltning - Petter Wigle
Klyftan mellan nyutveckling och förvaltning - Petter Wigle
Användaren smidig lättrorlig och vig? - Mattias Persson
Användaren smidig lättrorlig och vig? - Mattias Persson
Spelregler för självorganiserande team - Tomas Lundborg
Spelregler för självorganiserande team - Tomas Lundborg
Scrum och städning, fika eller städa det är frågan - Josefina Trende
Scrum och städning, fika eller städa det är frågan - Josefina Trende
Enkelhet som medel möjlighet som mål - Niklas Lindstrom
Enkelhet som medel möjlighet som mål - Niklas Lindstrom
10 Sätt att arbeta med åtagande - Marcus Widerberg
10 Sätt att arbeta med åtagande - Marcus Widerberg
Parprogrammering bra i alla lägen? - Niklas Lindholm
Parprogrammering bra i alla lägen? - Niklas Lindholm
Recently uploaded
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...
This LF Energy webinar took place June 20, 2024. It featured:
-Alex Thornton, LF Energy
-Hallie Cramer, Google
-Daniel Roesler, UtilityAPI
-Henry Richardson, WattTime
In response to the urgency and scale required to effectively address climate change, open source solutions offer significant potential for driving innovation and progress. Currently, there is a growing demand for standardization and interoperability in energy data and modeling. Open source standards and specifications within the energy sector can also alleviate challenges associated with data fragmentation, transparency, and accessibility. At the same time, it is crucial to consider privacy and security concerns throughout the development of open source platforms.
This webinar will delve into the motivations behind establishing LF Energy’s Carbon Data Specification Consortium. It will provide an overview of the draft specifications and the ongoing progress made by the respective working groups.
Three primary specifications will be discussed:
-Discovery and client registration, emphasizing transparent processes and secure and private access
-Customer data, centering around customer tariffs, bills, energy usage, and full consumption disclosure
-Power systems data, focusing on grid data, inclusive of transmission and distribution networks, generation, intergrid power flows, and market settlement data
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
"Scaling RAG Applications to serve millions of users", Kevin Goedecke
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
A Deep Dive into ScyllaDB's Architecture
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
Astute Business Solutions | Oracle Cloud Partner |
Your goto partner for Oracle Cloud, PeopleSoft, E-Business Suite, and Ellucian Banner. We are a firm specialized in managed services and consulting.
GNSS spoofing via SDR (Criptored Talks 2024)
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Demystifying Knowledge Management through Storytelling
The Department of Veteran Affairs (VA) invited Taylor Paschal, Knowledge & Information Management Consultant at Enterprise Knowledge, to speak at a Knowledge Management Lunch and Learn hosted on June 12, 2024. All Office of Administration staff were invited to attend and received professional development credit for participating in the voluntary event.
The objectives of the Lunch and Learn presentation were to:
- Review what KM ‘is’ and ‘isn’t’
- Understand the value of KM and the benefits of engaging
- Define and reflect on your “what’s in it for me?”
- Share actionable ways you can participate in Knowledge - - Capture & Transfer
Essentials of Automations: Exploring Attributes & Automation Parameters
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
High performance Serverless Java on AWS- GoTo Amsterdam 2024
Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Tomaz Bratanic
Graph ML and GenAI Expert - Neo4j
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Recently uploaded (20)
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
"Scaling RAG Applications to serve millions of users", Kevin Goedecke
"Scaling RAG Applications to serve millions of users", Kevin Goedecke
Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Demystifying Knowledge Management through Storytelling
Demystifying Knowledge Management through Storytelling
Essentials of Automations: Exploring Attributes & Automation Parameters
Essentials of Automations: Exploring Attributes & Automation Parameters
High performance Serverless Java on AWS- GoTo Amsterdam 2024
High performance Serverless Java on AWS- GoTo Amsterdam 2024
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Timeboxed releases - Peter Antman
- 2. Polopoly – Enterprise Web CMS
- 4. Time Boxed Releases 2 weeks A quarter DP1 Major DP5 DP4 DP3 Minor DP2 A month
- 8. Burn Down Release Plan
- 12. Follow the Trace
- 14. Stop the Line When Test Fails
- 19. END