Less is more the 7 wastes of lean software development
2 likes246 views
The document discusses the concept of lean software development and identifies seven types of waste that can occur: partially done work, extra features, extra processing, task switching, waiting/delays, handoffs, and defects. It provides examples of how adopting lean principles can help software teams reduce waste and increase speed, reduce costs, and lower risks by focusing only on delivering business value through frequent small releases. Specific techniques mentioned include minimizing code, prioritizing the minimum viable product, keeping things simple, avoiding premature optimization, and reducing meetings and handoffs between teams.
1 of 52
Download to read offline
Ad
Recommended
The Evolution of Agile: Dealing with the Growing Pains
The Evolution of Agile: Dealing with the Growing PainsTechWell Agile development has evolved into a lifecycle that not only affects the IT department but the overall business as well. Forward-thinking enterprises recognize this and benefit from the software efficiency that agile development delivers. Through real-world examples, Jonathan Thorpe explains how enterprises can improve their agile success. Discover how successful global enterprises are applying the principles of agile development beyond just software development to a level where it affects entire business groups. Jonathan describes the evolution of agile and discusses why organizations are feeling growing pains as the methodology grows from the IT department to the business level. Learn how agile methodologies can be applied to business analysis, release management, and other IT processes to ensure applications are being delivered to customers on time and on budget. Are you ready to ensure your entire organization is truly agile?
Serena Software: Introducing Orchestrated ALM
Serena Software: Introducing Orchestrated ALMadamfrankl This document introduces Serena Software's Orchestrated ALM solutions for application delivery. It discusses the challenges of today's application delivery landscape, including manual processes that create errors, poor collaboration across teams, and a lack of end-to-end traceability. Serena's Orchestrated ALM solutions address these challenges by providing integrated tools for demand management, development management, release management, and process intelligence to improve delivery performance, lower costs, and drive accountability. The solutions include components for request management, portfolio analysis, requirements management, change management, release control, and more.
State of mobile Continuous Delivery at Spotify
State of mobile Continuous Delivery at SpotifyMobile Delivery Days Presenters: Kristian Lindwall - Tribe lead, Spotify
Presented on Mar 22 at 12:30pm
Over the last 2 years, Spotify has put a serious effort into raising the bar on mobile continuous delivery. This talk will be about that journey. What major obstacles have we overcome, where are we and what are the current biggest challenges?
Continuous delivery using jenkins
Continuous delivery using jenkinsLeena N This document discusses the importance of continuous delivery using Jenkins. It introduces continuous integration and continuous delivery, explaining that continuous integration provides fast feedback on code changes while continuous delivery provides feedback on production readiness. It outlines how to set up a build pipeline in Jenkins to guarantee production readiness and make releases risk-free and automated. The document emphasizes that continuous delivery satisfies customers through early and frequent delivery of software and encourages teams to take responsibility for releases through continuous improvement.
Testing in a continuous delivery environment
Testing in a continuous delivery environmentStefan Verhoeff Talk at Iqnite conference for software quality and testing about how we have do continuous delivery at here.com
Together with Siddharth Somasundaram
http://www.iqnite-conferences.com/suisse/programme/programme.aspx
The evolution of agile development process
The evolution of agile development processDavid Tzemach The Evolution of Agile Development Process
The main sections of this presentation
1. Overview
2. The Waterfall Model as a baseline
3. Waterfall Model – Phases of the process
4. The problem in traditional models
5. Agile Software Development as the Alternative
6. The Agile Manifesto – The Beginning
7. The Manifesto for Agile Software Development
8. The benefits of the agile methodology
Continuous Delivery Overview
Continuous Delivery OverviewLuca Minudel Continuous Delivery (CD) is often thought to be within the purview of tech practitioners – developers, testers, operations, delivery managers, etc. However, the industry is fast realizing that CD is actually more of a business decision. CD can be the game changer to help the organization stay a step ahead by delivering value to the customer reliably and frequently. CD isn’t a geeky fad, but a huge business enabler vouched for by Facebook, LinkedIn, Flickr and the like. In this session I’ll Introduce the principles, the practices, the tools, and the business value proposition of continuous delivery both from a business point of view and from a technical point of view.
Continuous Integration, Delivery and Deployment
Continuous Integration, Delivery and DeploymentEero Laukkanen The document discusses the history and evolution of continuous integration, delivery, and deployment practices in software development. It describes how the practices have developed from big bang integration, where changes were merged infrequently after long development periods, to modern approaches where integration and testing occur frequently or continuously. This allows issues to be detected and addressed earlier, reducing risks and improving productivity and code quality. Continuous delivery further aims to ensure code is always releasable, while continuous deployment automates actual releases. Surveys find these practices are becoming more common but also face challenges in adoption related to code quality, testing, organizational culture and resources.
CI/CD for mobile at HERE
CI/CD for mobile at HEREStefan Verhoeff This talk describes how we use a scaled approach for CI/CD. The system is set up for iOS and Android Apps but many of the concepts presented are applicable for any type of application. We will cover the different pipeline stages a change goes through, how we automate many levels of testing, treat our CI infrastructure as code, which key metrics we use and we track them on dashboards. All this demonstrates how we can get close to Continuous Delivery for platforms still ruled by App stores.
Automation on the go ict
Automation on the go ictIndium Software The document discusses Indium Software's approach to automation testing called In Cycle Testing (ICT). ICT involves automating test cases as soon as they are identified and written during development sprints, rather than waiting until after development is complete. This allows test automation to grow in parallel with development and ensures adequate test coverage of new features. The document outlines the phases of ICT including planning, functional verification, automation script development, integration and execution. It provides metrics showing how ICT can decrease testing timelines, retesting effort and backlogs while increasing defect detection rates.
DOES15 - Vineet Banga and Jacob Johnson - Learnings from a DevOps Organizatio...
DOES15 - Vineet Banga and Jacob Johnson - Learnings from a DevOps Organizatio...Gene Kim Vineet Banga, Senior Software Manager, GE Digital
Jacob Johnson, Director of Cloud Services & Operations, GE Digital
GE Software is building a platform for Industrial Internet. Over the last few months we have transformed our services into a cloud only offering. To achieve these results we have had to ramp our devops practices at an unprecedented rate, and we continue to do that as we move forward. Since we are building a platform to build application which monitor industrial assets such as: Wind Turbines, Jet Engines etc, security and compliance are extremely critical. While, these requirements require us to have clear delineation between operations and development, we continue to push the boundaries and blur the lines between dev and ops. This talk cover the organization model, development and operations practices that we have adopted:
Top Challenges & insights:
-Access control to production instances & policies on how to manage them
-How to prevent developer’s throwing code over the wall?
-How to take realtime feedback from deployed services to improve the development practices?
Learnings:
-True collaboration is driven by having a critical mass across the teams, who share some core beliefs.
-Talk of pager duty is generally not a motivator for developers, sometimes it can turn them off from thinking about operations
-Giving developers more control in the outcome of the service they have built is a much better way driving true collaboration
What is Continuous Integration and Continuous Delivery 
What is Continuous Integration and Continuous Delivery Sarah Elson Continuous integration and Continuous Delivery are the processes, where your development team involves frequent code changes that are pushed in the main branch while ensuring that it does not impact any changes made by developers working parallelly. The aim of it is to reduce the chance of defects and conflicts during the integration of the complete project. Let’s take a deep dive and learn more about the fundamentals of Continuous Integration and Continuous Delivery.
DevOps & BPM: Continuous Integration Power Tools
DevOps & BPM: Continuous Integration Power ToolsBonitasoft Continuous Integration is one of the DevOps power tools applicable to process-based application development. Bonitasoft COO Charles Souillard explains why there's no need to "re-invent the wheel."
Software development in Formula One: challenges, complexity and struggle for ...
Software development in Formula One: challenges, complexity and struggle for ...Luca Minudel This is an experience report based on more than 3 years (2006-2009) of software development in F1 with Scrum, Lean and XP, developing evolving and maintaining software to support the F1 racing team from the vehicle conception and throughout every test and race.
In these 3 years I promoted and supported the advancement of the existing Agile practices in my team and then for all the software development teams of the F1 racing team.
How was this experience? It was dense and intense. What made it valuable? It was:
- the unique context characterized by very high levels of competition, speed and unpredictable rapid changes.
- the challenge of doing computer programming in an F1 team: the team and I had to learn and invent how to work with a code-base that is very large and long lived, a product that is uncommonly complex, in an organization that has high levels of interdependency and with technologies and competitors that are fast moving targets. We found ourselves far behind the boundaries where centralized top-down approaches could possibly work and where a book, a school degree or an expert could possibly reveal the right answer.
We had to do software development in extreme conditions and push ourselves to the limit as F1 drivers that really push and find the limits with the aim of outperforming competitors.
Have we survived this chaos? How did we survive? Which team and coding practices emerged? This experience report will look at the answers to all those questions and will try to answer questions from participants.
Managing Continuous Delivery of Mobile Apps - for the Enterprise
Managing Continuous Delivery of Mobile Apps - for the EnterpriseSauce Labs Enabling CI / CD in your mobile development process means understanding the different solutions, overcoming unique challenges and ensuring the right ownership of the processes. In this webinar, you will learn the steps required to enable Continuous Delivery of Mobile Application Platforms.
Test coverage in a jiffy v0 9
Test coverage in a jiffy v0 9Indium Software This document summarizes guidelines for software testing presented by Indium Software. It discusses focusing testing on areas developed quickly, the GUI, and complex code. It provides best practices like managing time, being involved in all stages of development, using diagrams to understand complex logic, and working with developers. A case study shows how test cases were prioritized for a project based on safety, financial impact, important features, and end-to-end scenarios. The benefits of this approach include improved quality and minimizing defects.
Coding Safe Modern C++ With AUTOSAR Guidelines
Coding Safe Modern C++ With AUTOSAR GuidelinesPerforce That's why static code analysis experts from Perforce (formerly PRQA) were invited to join the working group for AUTOSAR’s “Guidelines for the use of the C++14 language in critical and safety-related systems”.
AUTOSAR guidelines are a smart choice for C++ developers. And it’s now easier to use them to achieve functional safety compliance, particularly with ISO 26262.
You’ll learn:
-Why AUTOSAR guidelines were developed — and the philosophy behind them.
-How the rules changed in the latest version — including mapping to ISO 26262.
-What’s next for AUTOSAR guidelines — hint: being merged into MISRA C++.
-Plus what’s next for AUTOSAR guidelines.
Project Management App v2.1
Project Management App v2.1CloudFronts Technologies LLP. Join us for the winter release (v2.1) of our PM App for the Dynamics 365 v9 release! During our session we will review key features, bug fixes and pricing updates.
Webinar "Load Testing e Performance Monitoring con NeoLoad e NeoSense"
Webinar "Load Testing e Performance Monitoring con NeoLoad e NeoSense"Emerasoft, solutions to collaborate Neotys è azienda leader nell'ambito del software testing.
In questo webinar verranno mostrate le funzionalità dei due tool di Neotys: NeoLoad e NeoSense.
NeoLoad è l’innovativa soluzione per il test di carico e di performance su applicazioni web e mobile, facile da usare e con intuitive dashboard comparative.
NeoSense è la soluzione dinamica che permette di monitorare le performance di tutte le applicazioni web e mobile.
Creando utenti virtuali in produzione, monitora le prestazioni di transazioni complesse eseguendo scenari registrati di attività degli utenti.
Scopri le funzionalità dei due tool e di come possono essere combinati con successo: NeoSense, sfruttando le eccellenti capacità di NeoLoad nel realizzare gli scenari dei test, è in grado di creare profili di monitoraggio realistici in modo veloce, anche nel caso di business app complesse o di utilizzo delle ultime tecnologie web e mobile.
Agile vs. waterfall - The fundamentals differences
Agile vs. waterfall - The fundamentals differencesDavid Tzemach In this presentation I will review the main differences between waterfall and agile methodology, this presentation is a great place to start if you want to know why more and more companies are using agile as the preferred development methodology.
Felix Müller: Live Coding: Zeebe - Camunda Days Oslo, CPH, Amsterdam
Felix Müller: Live Coding: Zeebe - Camunda Days Oslo, CPH, Amsterdamcamunda services GmbH Zeebe is the next generation workflow engine developed by Camunda. It takes workflow automation to an entirely new level, with massive throughput and infinite horizontal scalibility. In this session, Zeebe core developer Thorben Lindhauer will demonstrate how to get started with Zeebe.
How to Do Code Reviews at Massive Scale For DevOps
How to Do Code Reviews at Massive Scale For DevOpsPerforce Code review is a critical part of your build process. And when you do code review right, you can streamline your build process and achieve DevOps.
Most code review tools work great when you have a team of 10 developers. But what happens when you need to scale code review to 1,000s of developers? Many will struggle. But you don’t need to.
Join our experts Johan Karlsson and Robert Cowham for a 30-minute webinar. You’ll learn:
-The problems with scaling code review from 10s to 100s to 1,000s of developers along with other dimensions of scale (files, reviews, size).
-The solutions for dealing with all dimensions of scale.
-How to utilize Helix Swarm at massive scale.
Ready to scale code review and streamline your build process? Get started with Helix Swarm, a code review tool for Helix Core.
How to maintain a perfect product architecture in a non-stop start-up
How to maintain a perfect product architecture in a non-stop start-upAdam Kariv Lessons from the trenches - my 2¢ on software architecture.
As a the Mobile Architect in EverythingMe, I know it's hard to maintain the software architecture of our product. It's never as good looking as we want it to be, and it's a constant battle just to keep it barely acceptable... This is how we do it.
SBM Orchestrations - Beginners Guide (FUG Presentation)
SBM Orchestrations - Beginners Guide (FUG Presentation)Serena Software 1. The document discusses orchestrations in Serena Business Manager, including alternatives like web service notifications, connectors to Dimension CM and RM, and PVCS version control.
2. It provides an overview of using orchestrations for process enforcement, automation, and integration across the SDLC from development to operations.
3. The document outlines how to build orchestrations using concepts like processes, loops, variables, and calls to web services, and recommends best practices like creating orchestrations from transitions.
Continuous Integration
Continuous IntegrationVijaya K Continuous integration (CI) helps mitigate risks in software development like bugs, lack of team cohesion, and poor code quality. CI involves daily developer integrations verified by automated builds. It helps build software better, faster, and cheaper by identifying defects earlier through testing early and often. The 7 step CI process includes committing code frequently, never committing broken code, fixing build failures immediately, and building in every target environment. With CI, issues can be found and fixed faster through regular commits, automated testing, and better project visibility. A simple CI pipeline includes building, testing, releasing candidates, and deploying to environments like test and production. A CI starter kit includes an automated build process, test suite, source control, and build
Continuous delivery mobile application development
Continuous delivery mobile application developmentThoughtworks This document discusses continuous delivery for mobile application development. It describes how a team previously spent 9 months developing a mobile app before releasing it live, with another 2 months spent fixing bugs. The document then outlines a continuous delivery process involving continuous integration, implementing a full production pipeline with testing at each stage, configuration management, and enabling push button releases. This approach aims to minimize lead time from idea to live release by keeping software always production ready and releasing tied to business needs rather than IT constraints.
Agile_in_TomTom
Agile_in_TomTomJason Lo This document discusses TomTom's adoption of Agile practices for their navigation software development. It outlines why they moved to Agile from waterfall due to long lifecycles and inability to respond quickly to changing requirements. Key aspects covered include using SAFe for their framework, releasing every 2 months, continuous integration and delivery, and emphasizing team autonomy and self-motivation. Roles like Scrum Master, Product Owner, and DevOps are discussed as important for enabling their Agile processes.
Business Process Management - What is it, and why all the buzz?
Business Process Management - What is it, and why all the buzz?Bonitasoft Learn about:
- The definition of BPM and the history behind its emergence
- Applying BPM method and technology to best advantage
- Using BPM modeling notation to facilitate collaboration between business and IT
- Practical, real world examples of "BPM applied"
What scrum masters and product owners should know about software quality and ...
What scrum masters and product owners should know about software quality and ...STX Next The document discusses technical debt in software projects. It defines technical debt as compromises in quality or maintainability that accumulate when developers take shortcuts or make quick fixes rather than implementing clean code. Technical debt comes from decisions to cut corners, such as not refactoring code or thoroughly testing features. Over time, technical debt can lead to slower development, more bugs, and heavier testing needs.
The document recommends calculating technical debt through software metrics like code complexity, duplication, and test coverage. It also suggests effective ways to manage technical debt in agile projects, such as creating a technical debt backlog, educating stakeholders, automating tests, and conducting retrospectives to improve practices and prevent accumulating further debt. Regularly paying down
Lect2 conventional software management
Lect2 conventional software managementmeena466141 The document discusses issues with the conventional "waterfall" model of software development and proposes improvements. It analyzes that the waterfall model is risky and invites failure due to late testing exposing design flaws. It then provides 5 necessary improvements: 1) adding a design phase before analysis, 2) increased documentation, 3) developing the software in two iterations, 4) improved testing planning and 5) increased customer involvement. It also discusses common issues seen in practice with the waterfall model like protracted integration, late risk resolution, and adversarial stakeholder relationships due to a focus on documents over working software.
Ad
More Related Content
What's hot (20)
CI/CD for mobile at HERE
CI/CD for mobile at HEREStefan Verhoeff This talk describes how we use a scaled approach for CI/CD. The system is set up for iOS and Android Apps but many of the concepts presented are applicable for any type of application. We will cover the different pipeline stages a change goes through, how we automate many levels of testing, treat our CI infrastructure as code, which key metrics we use and we track them on dashboards. All this demonstrates how we can get close to Continuous Delivery for platforms still ruled by App stores.
Automation on the go ict
Automation on the go ictIndium Software The document discusses Indium Software's approach to automation testing called In Cycle Testing (ICT). ICT involves automating test cases as soon as they are identified and written during development sprints, rather than waiting until after development is complete. This allows test automation to grow in parallel with development and ensures adequate test coverage of new features. The document outlines the phases of ICT including planning, functional verification, automation script development, integration and execution. It provides metrics showing how ICT can decrease testing timelines, retesting effort and backlogs while increasing defect detection rates.
DOES15 - Vineet Banga and Jacob Johnson - Learnings from a DevOps Organizatio...
DOES15 - Vineet Banga and Jacob Johnson - Learnings from a DevOps Organizatio...Gene Kim Vineet Banga, Senior Software Manager, GE Digital
Jacob Johnson, Director of Cloud Services & Operations, GE Digital
GE Software is building a platform for Industrial Internet. Over the last few months we have transformed our services into a cloud only offering. To achieve these results we have had to ramp our devops practices at an unprecedented rate, and we continue to do that as we move forward. Since we are building a platform to build application which monitor industrial assets such as: Wind Turbines, Jet Engines etc, security and compliance are extremely critical. While, these requirements require us to have clear delineation between operations and development, we continue to push the boundaries and blur the lines between dev and ops. This talk cover the organization model, development and operations practices that we have adopted:
Top Challenges & insights:
-Access control to production instances & policies on how to manage them
-How to prevent developer’s throwing code over the wall?
-How to take realtime feedback from deployed services to improve the development practices?
Learnings:
-True collaboration is driven by having a critical mass across the teams, who share some core beliefs.
-Talk of pager duty is generally not a motivator for developers, sometimes it can turn them off from thinking about operations
-Giving developers more control in the outcome of the service they have built is a much better way driving true collaboration
What is Continuous Integration and Continuous Delivery
What is Continuous Integration and Continuous Delivery Sarah Elson Continuous integration and Continuous Delivery are the processes, where your development team involves frequent code changes that are pushed in the main branch while ensuring that it does not impact any changes made by developers working parallelly. The aim of it is to reduce the chance of defects and conflicts during the integration of the complete project. Let’s take a deep dive and learn more about the fundamentals of Continuous Integration and Continuous Delivery.
DevOps & BPM: Continuous Integration Power Tools
DevOps & BPM: Continuous Integration Power ToolsBonitasoft Continuous Integration is one of the DevOps power tools applicable to process-based application development. Bonitasoft COO Charles Souillard explains why there's no need to "re-invent the wheel."
Software development in Formula One: challenges, complexity and struggle for ...
Software development in Formula One: challenges, complexity and struggle for ...Luca Minudel This is an experience report based on more than 3 years (2006-2009) of software development in F1 with Scrum, Lean and XP, developing evolving and maintaining software to support the F1 racing team from the vehicle conception and throughout every test and race.
In these 3 years I promoted and supported the advancement of the existing Agile practices in my team and then for all the software development teams of the F1 racing team.
How was this experience? It was dense and intense. What made it valuable? It was:
- the unique context characterized by very high levels of competition, speed and unpredictable rapid changes.
- the challenge of doing computer programming in an F1 team: the team and I had to learn and invent how to work with a code-base that is very large and long lived, a product that is uncommonly complex, in an organization that has high levels of interdependency and with technologies and competitors that are fast moving targets. We found ourselves far behind the boundaries where centralized top-down approaches could possibly work and where a book, a school degree or an expert could possibly reveal the right answer.
We had to do software development in extreme conditions and push ourselves to the limit as F1 drivers that really push and find the limits with the aim of outperforming competitors.
Have we survived this chaos? How did we survive? Which team and coding practices emerged? This experience report will look at the answers to all those questions and will try to answer questions from participants.
Managing Continuous Delivery of Mobile Apps - for the Enterprise
Managing Continuous Delivery of Mobile Apps - for the EnterpriseSauce Labs Enabling CI / CD in your mobile development process means understanding the different solutions, overcoming unique challenges and ensuring the right ownership of the processes. In this webinar, you will learn the steps required to enable Continuous Delivery of Mobile Application Platforms.
Test coverage in a jiffy v0 9
Test coverage in a jiffy v0 9Indium Software This document summarizes guidelines for software testing presented by Indium Software. It discusses focusing testing on areas developed quickly, the GUI, and complex code. It provides best practices like managing time, being involved in all stages of development, using diagrams to understand complex logic, and working with developers. A case study shows how test cases were prioritized for a project based on safety, financial impact, important features, and end-to-end scenarios. The benefits of this approach include improved quality and minimizing defects.
Coding Safe Modern C++ With AUTOSAR Guidelines
Coding Safe Modern C++ With AUTOSAR GuidelinesPerforce That's why static code analysis experts from Perforce (formerly PRQA) were invited to join the working group for AUTOSAR’s “Guidelines for the use of the C++14 language in critical and safety-related systems”.
AUTOSAR guidelines are a smart choice for C++ developers. And it’s now easier to use them to achieve functional safety compliance, particularly with ISO 26262.
You’ll learn:
-Why AUTOSAR guidelines were developed — and the philosophy behind them.
-How the rules changed in the latest version — including mapping to ISO 26262.
-What’s next for AUTOSAR guidelines — hint: being merged into MISRA C++.
-Plus what’s next for AUTOSAR guidelines.
Project Management App v2.1
Project Management App v2.1CloudFronts Technologies LLP. Join us for the winter release (v2.1) of our PM App for the Dynamics 365 v9 release! During our session we will review key features, bug fixes and pricing updates.
Webinar "Load Testing e Performance Monitoring con NeoLoad e NeoSense"
Webinar "Load Testing e Performance Monitoring con NeoLoad e NeoSense"Emerasoft, solutions to collaborate Neotys è azienda leader nell'ambito del software testing.
In questo webinar verranno mostrate le funzionalità dei due tool di Neotys: NeoLoad e NeoSense.
NeoLoad è l’innovativa soluzione per il test di carico e di performance su applicazioni web e mobile, facile da usare e con intuitive dashboard comparative.
NeoSense è la soluzione dinamica che permette di monitorare le performance di tutte le applicazioni web e mobile.
Creando utenti virtuali in produzione, monitora le prestazioni di transazioni complesse eseguendo scenari registrati di attività degli utenti.
Scopri le funzionalità dei due tool e di come possono essere combinati con successo: NeoSense, sfruttando le eccellenti capacità di NeoLoad nel realizzare gli scenari dei test, è in grado di creare profili di monitoraggio realistici in modo veloce, anche nel caso di business app complesse o di utilizzo delle ultime tecnologie web e mobile.
Agile vs. waterfall - The fundamentals differences
Agile vs. waterfall - The fundamentals differencesDavid Tzemach In this presentation I will review the main differences between waterfall and agile methodology, this presentation is a great place to start if you want to know why more and more companies are using agile as the preferred development methodology.
Felix Müller: Live Coding: Zeebe - Camunda Days Oslo, CPH, Amsterdam
Felix Müller: Live Coding: Zeebe - Camunda Days Oslo, CPH, Amsterdamcamunda services GmbH Zeebe is the next generation workflow engine developed by Camunda. It takes workflow automation to an entirely new level, with massive throughput and infinite horizontal scalibility. In this session, Zeebe core developer Thorben Lindhauer will demonstrate how to get started with Zeebe.
How to Do Code Reviews at Massive Scale For DevOps
How to Do Code Reviews at Massive Scale For DevOpsPerforce Code review is a critical part of your build process. And when you do code review right, you can streamline your build process and achieve DevOps.
Most code review tools work great when you have a team of 10 developers. But what happens when you need to scale code review to 1,000s of developers? Many will struggle. But you don’t need to.
Join our experts Johan Karlsson and Robert Cowham for a 30-minute webinar. You’ll learn:
-The problems with scaling code review from 10s to 100s to 1,000s of developers along with other dimensions of scale (files, reviews, size).
-The solutions for dealing with all dimensions of scale.
-How to utilize Helix Swarm at massive scale.
Ready to scale code review and streamline your build process? Get started with Helix Swarm, a code review tool for Helix Core.
How to maintain a perfect product architecture in a non-stop start-up
How to maintain a perfect product architecture in a non-stop start-upAdam Kariv Lessons from the trenches - my 2¢ on software architecture.
As a the Mobile Architect in EverythingMe, I know it's hard to maintain the software architecture of our product. It's never as good looking as we want it to be, and it's a constant battle just to keep it barely acceptable... This is how we do it.
SBM Orchestrations - Beginners Guide (FUG Presentation)
SBM Orchestrations - Beginners Guide (FUG Presentation)Serena Software 1. The document discusses orchestrations in Serena Business Manager, including alternatives like web service notifications, connectors to Dimension CM and RM, and PVCS version control.
2. It provides an overview of using orchestrations for process enforcement, automation, and integration across the SDLC from development to operations.
3. The document outlines how to build orchestrations using concepts like processes, loops, variables, and calls to web services, and recommends best practices like creating orchestrations from transitions.
Continuous Integration
Continuous IntegrationVijaya K Continuous integration (CI) helps mitigate risks in software development like bugs, lack of team cohesion, and poor code quality. CI involves daily developer integrations verified by automated builds. It helps build software better, faster, and cheaper by identifying defects earlier through testing early and often. The 7 step CI process includes committing code frequently, never committing broken code, fixing build failures immediately, and building in every target environment. With CI, issues can be found and fixed faster through regular commits, automated testing, and better project visibility. A simple CI pipeline includes building, testing, releasing candidates, and deploying to environments like test and production. A CI starter kit includes an automated build process, test suite, source control, and build
Continuous delivery mobile application development
Continuous delivery mobile application developmentThoughtworks This document discusses continuous delivery for mobile application development. It describes how a team previously spent 9 months developing a mobile app before releasing it live, with another 2 months spent fixing bugs. The document then outlines a continuous delivery process involving continuous integration, implementing a full production pipeline with testing at each stage, configuration management, and enabling push button releases. This approach aims to minimize lead time from idea to live release by keeping software always production ready and releasing tied to business needs rather than IT constraints.
Agile_in_TomTom
Agile_in_TomTomJason Lo This document discusses TomTom's adoption of Agile practices for their navigation software development. It outlines why they moved to Agile from waterfall due to long lifecycles and inability to respond quickly to changing requirements. Key aspects covered include using SAFe for their framework, releasing every 2 months, continuous integration and delivery, and emphasizing team autonomy and self-motivation. Roles like Scrum Master, Product Owner, and DevOps are discussed as important for enabling their Agile processes.
Business Process Management - What is it, and why all the buzz?
Business Process Management - What is it, and why all the buzz?Bonitasoft Learn about:
- The definition of BPM and the history behind its emergence
- Applying BPM method and technology to best advantage
- Using BPM modeling notation to facilitate collaboration between business and IT
- Practical, real world examples of "BPM applied"
Webinar "Load Testing e Performance Monitoring con NeoLoad e NeoSense"
Webinar "Load Testing e Performance Monitoring con NeoLoad e NeoSense"Emerasoft, solutions to collaborate
Similar to Less is more the 7 wastes of lean software development (20)
What scrum masters and product owners should know about software quality and ...
What scrum masters and product owners should know about software quality and ...STX Next The document discusses technical debt in software projects. It defines technical debt as compromises in quality or maintainability that accumulate when developers take shortcuts or make quick fixes rather than implementing clean code. Technical debt comes from decisions to cut corners, such as not refactoring code or thoroughly testing features. Over time, technical debt can lead to slower development, more bugs, and heavier testing needs.
The document recommends calculating technical debt through software metrics like code complexity, duplication, and test coverage. It also suggests effective ways to manage technical debt in agile projects, such as creating a technical debt backlog, educating stakeholders, automating tests, and conducting retrospectives to improve practices and prevent accumulating further debt. Regularly paying down
Lect2 conventional software management
Lect2 conventional software managementmeena466141 The document discusses issues with the conventional "waterfall" model of software development and proposes improvements. It analyzes that the waterfall model is risky and invites failure due to late testing exposing design flaws. It then provides 5 necessary improvements: 1) adding a design phase before analysis, 2) increased documentation, 3) developing the software in two iterations, 4) improved testing planning and 5) increased customer involvement. It also discusses common issues seen in practice with the waterfall model like protracted integration, late risk resolution, and adversarial stakeholder relationships due to a focus on documents over working software.
The Secret of Flow - My AgileIL11 Talk
The Secret of Flow - My AgileIL11 TalkYuval Yeret Journey towards better software development management using lean/kanban flow approaches - especially focused on service delivery in software sustainment.
Trying to provide a somewhat fresh view of how to get to kanban thinking, but based on the current recipes (e.g. David Anderson recipe for success)
From Continuous Integration to Continuous Delivery and DevOps
From Continuous Integration to Continuous Delivery and DevOpsLuca Minudel An overview of Continuous Delivery from a business and a technical point of view.
Includes an overview of:
- business value proposition of CD
- prerequisites and tips for CD implementation
- CD implementation was stories and strategies
- CD technical practices
Debugging,Troubleshooting & Monitoring Distributed Web & Cloud Applications a...
Debugging,Troubleshooting & Monitoring Distributed Web & Cloud Applications a...Theo Jungeblut In the past, applications where created as monolithic entities running on a single server. If this is the past for you, too, you will have experienced the downside of modern distributed and cloud applications, as debugging, troubleshooting, and monitoring is not easily accomplished with traditional approaches.
Within this session, we will explore different possibilities for collecting and analyzing the needed information to solve issues on modern distributed application and discuss the advantages and disadvantages of each approach like debugger, log files, performance counter and third party solutions. The focus of this session will be on Developer and DevOps need, as increased release cycles and third party dependency more and more result in the need for troubleshooting also on production system, rather than in an isolated test environment.
This session requires a solid understanding of distributed applications and knowledge of SOA, but most principles also apply to and can be beneficial for more traditional application design approaches. The used code examples are in .NET but the shown principles generally apply to other languages, too, and shown software is often available for a variety of environments.
Managing technical debt
Managing technical debtFadi Stephan Managing technical debt requires making prudent decisions about design and quality. It is important to 1) register any new debt, 2) assess existing debt, 3) monetize the debt to establish a debt limit, 4) pay down high-interest debt first, and 5) continuously monitor trends to adapt over time. Transparency is key through registering debt, inspection via monetization, and adapting practices as needed.
The Evolution of Application Release Automation
The Evolution of Application Release AutomationXebiaLabs The capabilities provided by today’s Application Release Automation (ARA) tools have advanced exponentially in recent years. Despite these advancements, the enterprise demands new requirements that go beyond application change to automate even more of the release process. The evolving definition of ARA now includes areas that were previously left unaddressed, such as the deployment of database changes and the orchestration of the entire release process. In this on-demand webinar, learn how Datical and XebiaLabs are working together to address the changing needs of the enterprise through the evolution of ARA.
Software Factories in the Real World: How an IBM WebSphere Integration Factor...
Software Factories in the Real World: How an IBM WebSphere Integration Factor...ghodgkinson This document discusses how an automotive retailer set up an efficient software factory using IBM tools like Rational Software Architect and WebSphere Message Broker to integrate a new point of sale system with their SAP backend. The software factory employed techniques like model-driven development and continuous integration to help scale development and keep customers satisfied. Key practices that helped succeed included tighter architectural control using Rational Software Architect models and service definitions, and keeping the distributed team coordinated using Rational Team Concert for planning, source control, and tracking progress across locations. The integrated approach and tools helped the retailer successfully complete the large integration project.
SE-TEXT-BOOK_Material.doc
SE-TEXT-BOOK_Material.docDrPreethiD1 This document provides an overview of software engineering and related topics covered in multiple units. Unit 1 discusses the nature of software, web applications, software engineering, software processes, agile development, and process models. It defines software and discusses its unique characteristics compared to hardware. Unit 1 also covers topics like legacy software, agile development principles, and generic and specialized software process models. Subsequent units cover requirements engineering, software design, user interface design, software testing, and other software engineering topics.
SE-TEXT-BOOK_Material.doc
SE-TEXT-BOOK_Material.docDrPreethiD1 This document provides an overview of software engineering and related topics covered in multiple units. Unit 1 discusses the nature of software, web applications, software engineering, software processes, agile development, and process models. It defines software and discusses its unique characteristics compared to hardware. Unit 1 also covers topics like legacy software, agile development principles, and generic and specialized software process models. Subsequent units cover requirements engineering, software design, user interface design, software testing, and other software engineering principles and practices.
01 intro+
01 intro+im|s The document discusses common problems faced by software projects, including large budget overruns, missed deadlines, and features not being delivered. It notes that 53% of projects are over budget, over time, or deliver fewer features than planned. Reasons for project failures include unclear requirements, changing requirements, underestimating complexity, and lack of testing. The document contrasts the differences between programming small programs versus engineering large, complex software systems. It emphasizes that software engineering requires a disciplined, systematic approach to developing reliable software on time and on budget.
Spi Cost Roi
Spi Cost RoiRam Srivastava The document discusses the benefits of software process improvement (SPI) and achieving higher maturity levels like CMMI Level 5. It provides examples of organizations that saw significant reductions in defects, costs and improvements in productivity after implementing SPI initiatives and achieving higher maturity levels. While SPI requires initial investments, it more than pays for itself through reductions in rework costs and improvements in productivity.
ODASE Introduction
ODASE IntroductionMission Critical IT The document describes ODASEODASE, an ontology-driven architecture and software engineering platform that aims to improve software quality, productivity and flexibility. Key points:
1) It separates application complexity from code through executable business ontologies that define 100% of the business logic.
2) This allows bugs to be eliminated early as the ontologies act as testable specifications for code generators to automatically produce business APIs and software.
3) Customers report being incredibly agile with a pure business focus and radically simplified IT systems through less hand-written code.
Reduce Release Risk with Feature Monitoring
Reduce Release Risk with Feature MonitoringSplit Software As you deploy code more frequently and ship features faster, you still have the risk of a release going wrong that could turn your evening into an all-nighter. We’ve got you.
We’ve built Feature Monitoring to detect issues in your release caused by a recent change, determine which feature caused the fault, alert the team responsible, and allow you to switch off the feature instantly. This is powered by new integrations with Sentry error tracking and a javascript performance monitoring agent. Page load times getting worse? Error rates rising? We’ll identify the change that caused it within 30 minutes.
Tune in to hear how you can start monitoring your next release!
Introduction to TM1 TurboIntegrator Debugger Webinar - Quebit Consulting
Introduction to TM1 TurboIntegrator Debugger Webinar - Quebit ConsultingQueBIT Consulting Today’s webinar is part of a monthly advanced webinar series offered by QueBIT. Register for future webinars by accessing the events page on our website at quebit.com/news-events
AGENDA:
What is the TurboIntegrator Debugger?
Main Features/Main Window Walkthrough
How will the TI debugger help me?
Limitations
Installation and Configuration
AMIS 25: DevOps Best Practice for Oracle SOA and BPM
AMIS 25: DevOps Best Practice for Oracle SOA and BPMMatt Wright DevOps and Cloud are transforming the software release process, one which spans multiple teams across development and operations (including testing, infrastructure management), into a collaborative process, with all teams working together to deliver solutions into production faster.
This session details how to implement a continuous delivery process for Oracle SOA/BPM projects, both on-premise and in the cloud, which transform the release process into an automated, reliable, high quality delivery pipeline that that deliver projects faster, with less risk and less cost.
It details the processes and best practices that need to be established, how to use tools to automate and govern the build, deployment and configuration of code from our first initial environment through to production.
1. Learn how DevOps and Continuous Delivery can stream-line the delivery of integration / bpm projects into production.
2. Learn how DevOps plus the Cloud service can accelerate the implementation of on-premise Oracle SOA .
3. Learn best practice for implementing DevOps or Continuous Delivery for Oracle SOA projects on-cloud and on-premise.
4. How to use tools to automate and govern the build, deployment and configuration of code from dev through to production
5. How to leverage the Cloud for Dev and Test, and the benefits this provides.
Slowing down to Speed up: Agile & Technical Debt - SGPRG 2015
Slowing down to Speed up: Agile & Technical Debt - SGPRG 2015Taghi Paksima Slowing down to Speed up: Agile & Technical Debt - Presented at Global Scrum Gathering 2015, Prague - #SGPRG
How dvcs can reduce your development costs and enhance productivity final
How dvcs can reduce your development costs and enhance productivity finalpsluaces This document discusses how distributed version control systems (DVCS) like Plastic SCM can reduce development costs and increase productivity compared to traditional centralized version control systems. It notes that DVCS allows for parallel development by multiple developers simultaneously working on their own branches, making the development process faster. DVCS also improves code quality by enabling code reviews and unit testing on individual branches before merging. The document provides examples of companies that saw productivity gains and cost savings by adopting Plastic SCM as their DVCS.
What Are The Benefits Of Low Code Development For Businesses
What Are The Benefits Of Low Code Development For Businessessunil Rawat Low-code development can be defined as process of developing solutions, low code application development, and software development tools.
Low-code solutions allow IT users to build blocks into applications and workflows. These building blocks remove the code that underlies actions and commands. IT can use these building blocks to create business apps and workflows without manual code.
Agile software architecture
Agile software architectureScott Hsieh The document discusses how architecture and agile development can seem contradictory, but presents approaches like dual track agile and the zipper model to balance architecture and agility. It explains that the most common causes of software mistakes are changing requirements, poor software management, and accumulating technical debt from unfixed issues. The presentation argues that architecture is needed in agile projects to support adaptability and anticipate changes while minimizing technical debt.
Ad
More from VictorSzoltysek (20)
The Gold Jacket Journey - How I passed 12 AWS Certs without Burning Out (and ...
The Gold Jacket Journey - How I passed 12 AWS Certs without Burning Out (and ...VictorSzoltysek Only a few hundred people on the planet have done this — and even fewer have documented the journey like this.
In just one year, I passed all 12 AWS certifications and earned the ultra-rare AWS Gold Jacket — without burning out, without quitting my job, and without wasting hours on fluff.
My secret? A completely AI-powered study workflow using ChatGPT, custom prompts, and a technique I call DeepResearch — a strategy that pulls high-signal insights from Reddit, blogs, and real-world exam feedback to shortcut the noise and fast-track what actually matters.
This is the slide deck from my live talk — it breaks down everything:
✅ How I used ChatGPT to quiz, explain, and guide me
✅ How DeepResearch helped me prioritize the right content
✅ My top 80/20 study tips, service-specific rules of thumb, and real-world exam traps
✅ The surprising things that still trip up even experienced cloud teams
If you’re considering AWS certifications — or want to learn how to study smarter using AI — this is your blueprint.
Java on AWS Without the Headaches - Fast Builds, Cheap Deploys, No Kubernetes
Java on AWS Without the Headaches - Fast Builds, Cheap Deploys, No KubernetesVictorSzoltysek Java Apps on AWS Without the Headaches: Fast Builds, Cheap Deploys, No Kubernetes
Let’s face it: the cloud has gotten out of hand. What used to be simple—deploying your Java app—has become a maze of slow builds, tedious deploys, and eye-watering AWS bills. But here’s the thing: it doesn’t have to be this way. Every minute you spend waiting on builds or wrestling with unnecessary cloud complexity is a minute you’re not building the features your customers actually care about.
In this talk, I’ll show you how to go from a shiny new Java app to production in under 10 minutes—with fast builds, cheap deploys, and zero downtime. We’ll go deep into optimizing builds with Gradle (it’s time to leave Maven in the dust), parallelization strategies, and smarter caching mechanics that make your CI/CD pipelines fly. From there, we’ll review the dozen+ ways AWS lets you deploy apps and cut through the chaos to find the solutions that work best for lean, fast, cost-effective pipelines. Spoiler: ECS and EKS usually aren’t the answer. Oh, and I’ll even show you how AI tools like AWS Bedrock can help streamline your processes further, so you can automate what should already be automatic.
This talk is for developers fed up with the cost, complexity, and friction of modern cloud setups—or those who long for the simplicity of the Heroku/Beanstalk/PCF days when deploying to the cloud wasn’t a headache. Whether you’re on AWS, Azure, or GCP, you’ll learn actionable, cloud-agnostic tips to build faster, deploy cheaper, and refocus on what matters most: delivering value to your users.
Demystifying GitHub Actions - Harnessing the power of automation to streamlin...
Demystifying GitHub Actions - Harnessing the power of automation to streamlin...VictorSzoltysek Dive into this deck on GitHub Actions, where we blend essential automation tips with fun movie-themed memes! Learn how to optimize your workflows, secure projects, and identify all the film references. Perfect for developers eager to enhance their GitHub skills and add efficiency to their processes. Enjoy and apply these insights for a more streamlined and secure development experience!
ChatGPT and Beyond - Elevating DevOps Productivity
ChatGPT and Beyond - Elevating DevOps ProductivityVictorSzoltysek In the dynamic field of DevOps, the quest for efficiency and productivity is endless. This talk introduces a revolutionary toolkit: Large Language Models (LLMs), including ChatGPT, Gemini, and Claude, extending far beyond traditional coding assistance. We'll explore how LLMs can automate not just code generation, but also transform day-to-day operations such as crafting compelling cover letters for TPS reports, streamlining client communications, and architecting innovative DevOps solutions. Attendees will learn effective prompting strategies and examine real-life use cases, demonstrating LLMs' potential to redefine productivity in the DevOps landscape. Join us to discover how to harness the power of LLMs for a comprehensive productivity boost across your DevOps activities.
AI Mastery 201: Elevating Your Workflow with Advanced LLM Techniques
AI Mastery 201: Elevating Your Workflow with Advanced LLM TechniquesVictorSzoltysek In the past six months, the AI landscape has undergone a massive transformation, ushering in a new era of productivity with the latest in Large Language Models (LLMs) and AI technology. This deep dive unlocks how to:
Create CustomGPT Models: No coding needed to tailor AI for your unique projects. Integrate your own data, including PDFs and Excel sheets, making information handling a breeze. Plus, discover how to call your own actions/integrations for even more personalized utility.
Navigate Advanced Prompting: Overcome AI's memory limits and utilize Retrieval-Augmented Generation for accessing your personalized data, streamlining how you interact with AI.
Stay Ahead with AI Trends: Peek into the evolving world of LLMs, featuring newcomers like Google Gemini, Anthropic Claude, Open Sora, and Twitter Grok, and understand what their advancements mean for your productivity.
Witness Real-Life Transformations: Through examples and prompt demonstrations, see firsthand how these AI strategies revolutionize routine tasks, from data analysis to content creation. Learn to leverage image output and input for advanced practical use cases, adding a new dimension to your productivity toolkit.
No previous coding or AI experience is needed for this talk. Stay ahead in the fast-evolving world of work. Embrace the AI revolution and transform your workflow with advanced LLM techniques. Join us to ensure you're not left behind in the productivity race.
Harnessing ChatGPT - Elevating Productivity in Today's Agile Environment
Harnessing ChatGPT - Elevating Productivity in Today's Agile EnvironmentVictorSzoltysek The fast-paced world of Agile development just got a turbo boost! Dive into this engaging talk on "Innovation at Speed: ChatGPT & the AI Transformation in Agile Development." Over the last few months, AI, including notable tools like Google Bard and Microsoft Co-Pilot, has been leveraged to supercharge Agile workflows. In this session, attendees will get an overview of the current AI landscape and its impact on development. They will learn why AI is the game-changer needed to embrace in the Agile lifecycle, offering that elusive X factor to multiply productivity. Real-world examples will be presented, and the challenges of implementing AI tools like ChatGPT within corporate environments will be discussed.
Simplified DevOps Bliss -with OpenAI API
Simplified DevOps Bliss -with OpenAI APIVictorSzoltysek Are you tired of the ever-increasing complexity in the world of DevOps? Do Docker and Kubernetes scripts, Ansible configurations, and networking woes make your head spin? It's time for a breath of fresh air.
Join us on a transformative journey where we shatter the myth that DevOps has to be overly complicated. Say goodbye to the days of struggling with incomplete scripts and tangled configurations. In this enlightening talk, we'll guide you through the process of rapidly onboarding your new standard microservice into the DevOps and Cloud universe.
We'll unveil the power of GitHub Actions, AWS, OpenAI API, and MS Teams Incoming Web hooks in a way that's both enlightening and entertaining. Additionally, we'll explore how Language Model APIs (LLMs) can be leveraged to enhance and streamline your DevOps workflows. You'll discover that DevOps doesn't have to be a labyrinth of complexity; it can be a streamlined and enjoyable experience.
So, if you're ready to simplify your DevOps journey and embrace a world where AWS, the OpenAI API, and GitHub Actions collaborate seamlessly while harnessing the potential of LLMs, join us and let's make DevOps a breeze!
From SpaceX Launch Pads to Rapid Deployments
From SpaceX Launch Pads to Rapid DeploymentsVictorSzoltysek SpaceX's triumph in the space industry reveals essential principles that can guide our DevOps journey: optimizing for the whole system, embracing failure, and tightening feedback loops. Unfortunately, in the world of DevOps, these principles are often lost in a rush to adopt the latest technologies, such as Kubernetes, without understanding their true value.
This talk will explore how many organizations are caught up in the hype, sacrificing the core of DevOps for superficial implementations. Drawing parallels with SpaceX's development and the audacity of their mission, we'll investigate how to bring DevOps back to its roots.
Prepare for a potentially controversial examination of common practices that may be slowing you down, like mandated pull requests and feature branching. By aligning with the principles that powered SpaceX's success, we'll redefine what DevOps means and how it can transform the way we work.
The Future of JVM Languages 
The Future of JVM Languages VictorSzoltysek A look at the future of JVM languages including Kotlin, Scala, Groovy, and latest Java.
Which language to use ? what are the benefits of higher level abstractions ? and what are the benefits of programming on the JVM ?
Driving Process Improvements - A Guided Approach to Running Effective Retrosp...
Driving Process Improvements - A Guided Approach to Running Effective Retrosp...VictorSzoltysek An alternative and guided approach to running efficient retrospectives that tackle come challenges including : sacred cow, authority bias, bike shedding, imposter syndrome, and the Dunning-Kruger effect.
Spaceships, Pull Requests and Feature Branching - A Principles-Based approac...
Spaceships, Pull Requests and Feature Branching - A Principles-Based approac...VictorSzoltysek Elon Musk’s SpaceX company continues to revolutionize the aerospace industry, has greatly reduced the cost of space travel, and is on track to put mankind on Mars in our life time.
What are the Principles to this Success, and what does it have to do with Pull Requests and Feature Branching ?
We’ll look at these Principles to explain how Pull Requests and Feature Branching are often detrimental to software delivery and are likely slowing you down.
We’ll explore alternatives like Trunk Based Development and Pair Programming and walk through a more efficient coding workflow to help speed up your software delivery project.
Real-World DevOps — 20 Practical Developers Tips for Tightening Your Operatio...
Real-World DevOps — 20 Practical Developers Tips for Tightening Your Operatio...VictorSzoltysek This document provides 20 tips for tightening operational feedback loops in DevOps. Some of the key tips include: adopting a "you build it, you run it" mentality; automatically building on each commit; versioning build artifacts; notifying on broken builds; deploying frequently via CI; and notifying on unknown errors and third party dependency errors. The document emphasizes improving feedback loops through practices like building and deploying more often, deploying to production from trunk, and addressing issues quickly to avoid technical debt.
Real-World Application Observability - 11 Practical Developer Focused Tips
Real-World Application Observability - 11 Practical Developer Focused TipsVictorSzoltysek Application Observability is a confusing space, between all the lingo (SRE, APMs, Tracing, Spans, etc) and technologies (Splunk, Datadog, Micrometer, etc), things often get implementing haphazardly with minimal focus on actual value.
We will cut through buzzwords and fads, and take a high level look at a typical Java Spring Boot / ReactJS Application and provide 11 Practical Developers Focused Tips on implementing and getting REAL value.
Simple, Easy (but often ignored) Strategies will be provided that you can immediately start applying on your project regardless of programming languages used.
Victor's Awesome Retro Deck
Victor's Awesome Retro DeckVictorSzoltysek This document appears to be an agenda for a team retrospective meeting. It includes sections to:
1. Review action items from the last sprint
2. Celebrate wins from the previous sprint
3. Discuss the key trait of successful teams according to Google (psychological safety)
4. Discuss four challenges that can affect effective retrospectives: sacred cows, authority bias, bikeshedding, and imposter syndrome.
The agenda then prompts discussions around psychological safety, issues/challenges/concerns, and identifying process improvements to try in the next sprint.
Software Development in Internet Memes
Software Development in Internet MemesVictorSzoltysek Software development projects can often feel like a never-ending struggle. Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. This meme pokes fun at the complexity of Kubernetes by comparing it to an endless abyss that developers must brave in their work.
Big Bangs, Monorails and Microservices - Feb 2020
Big Bangs, Monorails and Microservices - Feb 2020VictorSzoltysek Only a few things are certain in life: death, taxes, and the fact most software projects will go over-budget, underperform, or worse-yet fail altogether.
With decades of books, conferences, and materials written on the subject, we continue repeating the same fundamental mistakes that lead to these failures — and we still end-up with massive cost overruns or worse still: complete write-offs with nothing to show.
Come take a journey back in time to 1990’s Springfield to get some insights on avoiding these costly mistakes, and to help shed light on why failures like healthgov.org or canada.ca continue happening.
We’ll look on how to pragmatically deal with our obsession with shiny objects, our wishful thinking tendencies, our self-interest with Resume-Driven Design, and a slew of other and often non-technical anti-patterns —in order to help mitigate them, and make a more efficient Springfield.
Making your RDBMS fast! 
Making your RDBMS fast! VictorSzoltysek Victor shares developer-focused database agnostic performance tips from his experiences on consulting on a database migration project for a major telecom.
SQL Tips + Tricks for Developers
SQL Tips + Tricks for DevelopersVictorSzoltysek This document summarizes a lunch and learn session on SQL tips and tricks for developers. It covers topics like using indexes to improve performance, avoiding SQL injection, using transactions properly, null value handling, the N+1 query problem, database statistics and tools like Spring Data repositories, IntelliJ SQL support and database versioning. It also discusses NoSQL vs SQL databases and embedded database options for testing.
Modern day jvm controversies
Modern day jvm controversiesVictorSzoltysek Since it’s introduction over 20 years ago, Java developers have had plenty of strong and often opposing ways of doing things.
Modern day JVM development has only added more options, more divisiveness, and even more heated arguments.
* Constructor or Setter Injection ?
* Dynamic or Static typing ?
* Monolithic or Micro-service application design ?
* Java or Scala or Kotlin ?
* JVM or .NET ?
* Reactive ?
* Are Mutable types and Threads inherently Evil?
* Is Kubernetes / Docker the modern way of JVM deployments?
Let’s dive into these and other issues .. while also stepping back and looking at the Bigger Picture:
What is it really about these choices that improve the bottom line ?
Most importantly .. let’s also settle once and for all:
Maven or Gradle?
The Future of Java - and a look at the evolution of programming languages
The Future of Java - and a look at the evolution of programming languagesVictorSzoltysek More then 20 years after it’s release, Java still tops the popular TIOBE index as the most popular programming language in the world. But is it time for Java to be relegated to the ranks of Cobalt and Fortran ? Itself replaced by something shiner on the JVM stack ?
Take a quick journey back-in-time to explore the progression of programming languages; from Assembly to C to Java. Then dive into 3 solid JVM language alternatives in search of the next big thing, and explore the benefits they bring to the Java space.
Ad
Recently uploaded (20)
Revolutionizing Residential Wi-Fi PPT.pptx
Revolutionizing Residential Wi-Fi PPT.pptxnidhisingh691197 Discover why Wi-Fi 7 is set to transform wireless networking and how Router Architects is leading the way with next-gen router designs built for speed, reliability, and innovation.
Designing AI-Powered APIs on Azure: Best Practices& Considerations
Designing AI-Powered APIs on Azure: Best Practices& ConsiderationsDinusha Kumarasiri AI is transforming APIs, enabling smarter automation, enhanced decision-making, and seamless integrations. This presentation explores key design principles for AI-infused APIs on Azure, covering performance optimization, security best practices, scalability strategies, and responsible AI governance. Learn how to leverage Azure API Management, machine learning models, and cloud-native architectures to build robust, efficient, and intelligent API solutions
Who Watches the Watchmen (SciFiDevCon 2025)
Who Watches the Watchmen (SciFiDevCon 2025)Allon Mureinik Tests, especially unit tests, are the developers’ superheroes. They allow us to mess around with our code and keep us safe.
We often trust them with the safety of our codebase, but how do we know that we should? How do we know that this trust is well-deserved?
Enter mutation testing – by intentionally injecting harmful mutations into our code and seeing if they are caught by the tests, we can evaluate the quality of the safety net they provide. By watching the watchmen, we can make sure our tests really protect us, and we aren’t just green-washing our IDEs to a false sense of security.
Talk from SciFiDevCon 2025
https://www.scifidevcon.com/courses/2025-scifidevcon/contents/680efa43ae4f5
Adobe Photoshop CC 2025 Crack Full Serial Key With Latest
Adobe Photoshop CC 2025 Crack Full Serial Key With Latestusmanhidray Copy & Past Link👉👉💖
💖http://drfiles.net/
Adobe Photoshop is a widely-used, professional-grade software for digital image editing and graphic design. It allows users to create, manipulate, and edit raster images, which are pixel-based, and is known for its extensive tools and capabilities for photo retouching, compositing, and creating intricate visual effects.
Adobe Marketo Engage Champion Deep Dive - SFDC CRM Synch V2 & Usage Dashboards
Adobe Marketo Engage Champion Deep Dive - SFDC CRM Synch V2 & Usage DashboardsBradBedford3 Join Ajay Sarpal and Miray Vu to learn about key Marketo Engage enhancements. Discover improved in-app Salesforce CRM connector statistics for easy monitoring of sync health and throughput. Explore new Salesforce CRM Synch Dashboards providing up-to-date insights into weekly activity usage, thresholds, and limits with drill-down capabilities. Learn about proactive notifications for both Salesforce CRM sync and product usage overages. Get an update on improved Salesforce CRM synch scale and reliability coming in Q2 2025.
Key Takeaways:
Improved Salesforce CRM User Experience: Learn how self-service visibility enhances satisfaction.
Utilize Salesforce CRM Synch Dashboards: Explore real-time weekly activity data.
Monitor Performance Against Limits: See threshold limits for each product level.
Get Usage Over-Limit Alerts: Receive notifications for exceeding thresholds.
Learn About Improved Salesforce CRM Scale: Understand upcoming cloud-based incremental sync.
TestMigrationsInPy: A Dataset of Test Migrations from Unittest to Pytest (MSR...
TestMigrationsInPy: A Dataset of Test Migrations from Unittest to Pytest (MSR...Andre Hora Unittest and pytest are the most popular testing frameworks in Python. Overall, pytest provides some advantages, including simpler assertion, reuse of fixtures, and interoperability. Due to such benefits, multiple projects in the Python ecosystem have migrated from unittest to pytest. To facilitate the migration, pytest can also run unittest tests, thus, the migration can happen gradually over time. However, the migration can be timeconsuming and take a long time to conclude. In this context, projects would benefit from automated solutions to support the migration process. In this paper, we propose TestMigrationsInPy, a dataset of test migrations from unittest to pytest. TestMigrationsInPy contains 923 real-world migrations performed by developers. Future research proposing novel solutions to migrate frameworks in Python can rely on TestMigrationsInPy as a ground truth. Moreover, as TestMigrationsInPy includes information about the migration type (e.g., changes in assertions or fixtures), our dataset enables novel solutions to be verified effectively, for instance, from simpler assertion migrations to more complex fixture migrations. TestMigrationsInPy is publicly available at: https://github.com/altinoalvesjunior/TestMigrationsInPy.
EASEUS Partition Master Crack + License Code
EASEUS Partition Master Crack + License Codeaneelaramzan63 Copy & Paste On Google >>> https://dr-up-community.info/
EASEUS Partition Master Final with Crack and Key Download If you are looking for a powerful and easy-to-use disk partitioning software,
Salesforce Data Cloud- Hyperscale data platform, built for Salesforce.
Salesforce Data Cloud- Hyperscale data platform, built for Salesforce.Dele Amefo Salesforce Data Cloud- Hyperscale data platform, built for Salesforce.
Secure Test Infrastructure: The Backbone of Trustworthy Software Development
Secure Test Infrastructure: The Backbone of Trustworthy Software DevelopmentShubham Joshi A secure test infrastructure ensures that the testing process doesn’t become a gateway for vulnerabilities. By protecting test environments, data, and access points, organizations can confidently develop and deploy software without compromising user privacy or system integrity.
Microsoft AI Nonprofit Use Cases and Live Demo_2025.04.30.pdf
Microsoft AI Nonprofit Use Cases and Live Demo_2025.04.30.pdfTechSoup In this webinar we will dive into the essentials of generative AI, address key AI concerns, and demonstrate how nonprofits can benefit from using Microsoft’s AI assistant, Copilot, to achieve their goals.
This event series to help nonprofits obtain Copilot skills is made possible by generous support from Microsoft.
What You’ll Learn in Part 2:
Explore real-world nonprofit use cases and success stories.
Participate in live demonstrations and a hands-on activity to see how you can use Microsoft 365 Copilot in your own work!
Solidworks Crack 2025 latest new + license code
Solidworks Crack 2025 latest new + license codeaneelaramzan63 Copy & Paste On Google >>> https://dr-up-community.info/
The two main methods for installing standalone licenses of SOLIDWORKS are clean installation and parallel installation (the process is different ...
Disable your internet connection to prevent the software from performing online checks during installation
What Do Contribution Guidelines Say About Software Testing? (MSR 2025)
What Do Contribution Guidelines Say About Software Testing? (MSR 2025)Andre Hora Software testing plays a crucial role in the contribution process of open-source projects. For example, contributions introducing new features are expected to include tests, and contributions with tests are more likely to be accepted. Although most real-world projects require contributors to write tests, the specific testing practices communicated to contributors remain unclear. In this paper, we present an empirical study to understand better how software testing is approached in contribution guidelines. We analyze the guidelines of 200 Python and JavaScript open-source software projects. We find that 78% of the projects include some form of test documentation for contributors. Test documentation is located in multiple sources, including CONTRIBUTING files (58%), external documentation (24%), and README files (8%). Furthermore, test documentation commonly explains how to run tests (83.5%), but less often provides guidance on how to write tests (37%). It frequently covers unit tests (71%), but rarely addresses integration (20.5%) and end-to-end tests (15.5%). Other key testing aspects are also less frequently discussed: test coverage (25.5%) and mocking (9.5%). We conclude by discussing implications and future research.
Avast Premium Security Crack FREE Latest Version 2025
Avast Premium Security Crack FREE Latest Version 2025mu394968 🌍📱👉COPY LINK & PASTE ON GOOGLE https://dr-kain-geera.info/👈🌍
Avast Premium Security is a paid subscription service that provides comprehensive online security and privacy protection for multiple devices. It includes features like antivirus, firewall, ransomware protection, and website scanning, all designed to safeguard against a wide range of online threats, according to Avast.
Key features of Avast Premium Security:
Antivirus: Protects against viruses, malware, and other malicious software, according to Avast.
Firewall: Controls network traffic and blocks unauthorized access to your devices, as noted by All About Cookies.
Ransomware protection: Helps prevent ransomware attacks, which can encrypt your files and hold them hostage.
Website scanning: Checks websites for malicious content before you visit them, according to Avast.
Email Guardian: Scans your emails for suspicious attachments and phishing attempts.
Multi-device protection: Covers up to 10 devices, including Windows, Mac, Android, and iOS, as stated by 2GO Software.
Privacy features: Helps protect your personal data and online privacy.
In essence, Avast Premium Security provides a robust suite of tools to keep your devices and online activity safe and secure, according to Avast.
Societal challenges of AI: biases, multilinguism and sustainability
Societal challenges of AI: biases, multilinguism and sustainabilityJordi Cabot Towards a fairer, inclusive and sustainable AI that works for everybody.
Reviewing the state of the art on these challenges and what we're doing at LIST to test current LLMs and help you select the one that works best for you
Get & Download Wondershare Filmora Crack Latest [2025]![Get & Download Wondershare Filmora Crack Latest [2025]](https://cdn.slidesharecdn.com/ss_thumbnails/revolutionizingresidentialwi-fi-250422112639-60fb726f-250429170801-59e1b240-thumbnail.jpg?width=560&fit=bounds)
Get & Download Wondershare Filmora Crack Latest [2025]saniaaftab72555 Copy & Past Link 👉👉
https://dr-up-community.info/
Wondershare Filmora is a video editing software and app designed for both beginners and experienced users. It's known for its user-friendly interface, drag-and-drop functionality, and a wide range of tools and features for creating and editing videos. Filmora is available on Windows, macOS, iOS (iPhone/iPad), and Android platforms.
Landscape of Requirements Engineering for/by AI through Literature Review
Landscape of Requirements Engineering for/by AI through Literature ReviewHironori Washizaki Hironori Washizaki, "Landscape of Requirements Engineering for/by AI through Literature Review," RAISE 2025: Workshop on Requirements engineering for AI-powered SoftwarE, 2025.
Kubernetes_101_Zero_to_Platform_Engineer.pptx
Kubernetes_101_Zero_to_Platform_Engineer.pptxCloudScouts Presentacion de la primera sesion de Zero to Platform Engineer
Exploring Wayland: A Modern Display Server for the Future
Exploring Wayland: A Modern Display Server for the FutureICS Wayland is revolutionizing the way we interact with graphical interfaces, offering a modern alternative to the X Window System. In this webinar, we’ll delve into the architecture and benefits of Wayland, including its streamlined design, enhanced performance, and improved security features.
Exploring Code Comprehension in Scientific Programming: Preliminary Insight...
Exploring Code Comprehension in Scientific Programming: Preliminary Insight...University of Hawai‘i at Mānoa This presentation explores code comprehension challenges in scientific programming based on a survey of 57 research scientists. It reveals that 57.9% of scientists have no formal training in writing readable code. Key findings highlight a "documentation paradox" where documentation is both the most common readability practice and the biggest challenge scientists face. The study identifies critical issues with naming conventions and code organization, noting that 100% of scientists agree readable code is essential for reproducible research. The research concludes with four key recommendations: expanding programming education for scientists, conducting targeted research on scientific code quality, developing specialized tools, and establishing clearer documentation guidelines for scientific software.
Presented at: The 33rd International Conference on Program Comprehension (ICPC '25)
Date of Conference: April 2025
Conference Location: Ottawa, Ontario, Canada
Preprint: https://arxiv.org/abs/2501.10037
Exploring Code Comprehension in Scientific Programming: Preliminary Insight...
Exploring Code Comprehension in Scientific Programming: Preliminary Insight...University of Hawai‘i at Mānoa
Less is more the 7 wastes of lean software development
- 1. LESS > MORE Victor Szoltysek [email protected] Platform Architect - Pivotal
- 3. #1 - MORE SPEED
- 4. #2 - LESS COST
- 5. #3 - LESS RISK
- 8. IDENTIFYING AND ELIMINATING WASTE
- 9. NIKE ADOPTION SUCCESS 50% DEFECT RATES REDUCTION 15% PRODUCTIVITY INCREASE 40% REDUCTION IN LEAD TIME
- 10. X FACTOR IN SOFTWARE
- 11. 1. Partially Done Work 2. Extra Features 3. Extra Processing 4. Task Switching 5. Waiting, Delays 6. Handoffs 7. Defects 7 THE WASTES OF LEAN SOFTWARE DEVELOPMENT
- 12. 1. Partially Done Work 2. Extra Features 3. Extra Processing 4. Task Switching 5. Waiting, Delays 6. Handoffs 7. Defects 7 THE WASTES OF LEAN SOFTWARE DEVELOPMENT
- 13. WASTE # 1- PARTIALLY DONE WORK
- 15. WASTE #2 - EXTRA FEATURES
- 17. Replacement Plans and Aspirations
- 18. Actual Result
- 19. What was Actually Needed
- 20. LESS CODE IS LESS LIABILITY
- 21. MORE IMMEDIATE DELIVERY OF BUSINESS VALUE (MINIMUM VIABLE PRODUCT)
- 22. MORE SIMPLICITY (KEEP IT SIMPLE SILLY)
- 23. LESS PREMATURE OPTIMIZATION + MODURALIZATION
- 26. WASTE #3 - EXTRA PROCESSING
- 27. LESS MEETINGS
- 29. LESS NOISE
- 30. WASTE #4 - TASK SWITCHING
- 32. WASTE #5 - WAITING, DELAYS
- 33. LESS TICKETS
- 34. LESS TEAM SILOS
- 36. MORE CLOUD
- 41. LESS BRANCHING
- 42. LESS MANUAL CODE REVIEWS
- 43. WASTE #6 - HANDOFFS
- 44. MORE EMBEDDED TEAM MEMBERS
- 45. LESS OFFSHORE
- 46. MORE CO-LOCATION
- 47. MORE 2 PIZZA TEAMS
- 48. WASTE #7 - DEFECTS
- 49. MORE IMMEDIATE BUG FIXING
- 51. 1. Excessive Modularization (Microservices / SCM Repos) 2. Long Lived Branches 3. Many Team Handoffs to get too production 4. Long Lead Times to get to production 5. Partially Allocated Resources 6. Lower Level Abstractions (i.e. K8S) when higher level (PaaS) might be sufficient 7. Optimizing without metrics (non-blocking, reactive, web-scale, etc) 8. Set Term Project Staffing instead of Long Term Product Staffing 9. Single Page Apps (SPA’s) when Simple Server Side Rendering is sufficient 10. Reinventing the Wheel (Common Codes, Libraries, Platforms, etc) 11. Treating new technologies as Silver Bullets (Containers, Scala, NoSQL, etc) OBSERVED TOP SOFTWARE WASTE SMELLS IN CORPORATE
- 52. DO MORE WITH LESS Victor Szoltysek [email protected]