The document discusses agile engineering and federated application lifecycle management (ALM). It defines agile practices like Scrum, Lean, XP and Kanban. It also discusses challenges with agility like testing overhead and keeping up with emerging technologies. Federated ALM is defined as integrating metadata, workflows and processes across development stages with customizable application development and integration flows.
Is Agile Development right for you? Many proponents would say, of course it is. But it can also be a little scary, especially if you come from a traditional approach. This presentation describes two case studies in which Agile development was successful, and some situations in which it may not be the best choice.
Agile software delivery strategies have taken organizations by storm, and those very same organizations are now scaling agile strategies across the entire IT organization as well as on very complex projects. Agile strategies are even being applied on enterprise architecture teams and are proving to be successful in practice. This presentation overviews IBM s Agile Scaling Model (ASM) and how to take an agile approach to enterprise architecture. It also summarizes industry data exploring the effectiveness of agile strategies and of various enterprise architecture strategies.
Scrum and Agile Engineering Practices - What every ScrumMaster needs to know
Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process.
Introduction to Disciplined Agile Delivery (DAD) : Presented by Dr. Sanjay Sa...oGuild .
Introduction to Disciplined Agile (DA): Learn about the four delivery lifecycles supported by DA; how DA is a hybrid that shows how proven practices from a range of sources fits together; how to take a flexible, non-prescriptive approach to agile development; the importance of being enterprise aware.
Disciplined Agile roles: Team Lead (ScrumMaster), Product Owner, Architecture Owner, Team Member, Stakeholder + five more optional scaling roles.
Inception Phase: Covers key activities for initiating a DA team, including initial requirements modelling, initial architecture modelling, initial release planning, strategies for your physical and virtual work environments, initial risk identification, and driving to a shared vision with your stakeholders.
Construction Phase: Describes many technical strategies for building consumable increments of your solution, including test-driven development (TDD), acceptance TDD, how to initiate an iteration/sprint, look-ahead modelling and planning, spikes, regular coordination meetings, continuous integration, continuous deployment, whole-team testing, parallel independent testing, information radiators, Kanban boards, burn up charts, and many more. In this module we also look at agile construction from a traditional point of view, showing how activities such as architecture, analysis, design, testing, management, and user experience (UX) are addressed all the way through the lifecycle.
Transition Phase: Overviews strategies for releasing the solution to your stakeholders.
Because transitioning to agile can be difficult—and often wrenching—for teams, many organizations are turning to kanban practices. Kanban, which involves just-in-time software delivery, offers a more gradual evolution to agile and is adaptable to many company cultures and environments. With kanban, developers pull work from a queue—taking care not to exceed a threshold for simultaneous tasks—while making progress visible to all. Alan Shalloway shares eight steps to adopt kanban in your team and organization. He begins with a value stream map of existing processes to establish an initial kanban board, providing transparency into the state of the current workflow. Another step is to establish explicit policies to define workflow changes and engender project visibility. Because kanban can easily be expanded to cover many parts of development, another step is to increase stakeholder involvement in the process. Join this interactive session to practice these key steps with hands-on exercises. By the end, you will have an initial plan for implementing kanban in your organization.
Apply Scrum to Your Hardware & Manufacturing Projects for Better Results by H...SmitsMC LLC
Myth: You can't iterate hardware. Really? Let's talk about John Deere. In 2012, we documented that it typically took them 18 - 36 months to develop a working prototype. After working with Scrum, they had a working prototype in 8 MONTHS. This presentation demonstrates more stories like this one.
Is Agile Development right for you? Many proponents would say, of course it is. But it can also be a little scary, especially if you come from a traditional approach. This presentation describes two case studies in which Agile development was successful, and some situations in which it may not be the best choice.
Agile software delivery strategies have taken organizations by storm, and those very same organizations are now scaling agile strategies across the entire IT organization as well as on very complex projects. Agile strategies are even being applied on enterprise architecture teams and are proving to be successful in practice. This presentation overviews IBM s Agile Scaling Model (ASM) and how to take an agile approach to enterprise architecture. It also summarizes industry data exploring the effectiveness of agile strategies and of various enterprise architecture strategies.
Scrum and Agile Engineering Practices - What every ScrumMaster needs to know
Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process.
Introduction to Disciplined Agile Delivery (DAD) : Presented by Dr. Sanjay Sa...oGuild .
Introduction to Disciplined Agile (DA): Learn about the four delivery lifecycles supported by DA; how DA is a hybrid that shows how proven practices from a range of sources fits together; how to take a flexible, non-prescriptive approach to agile development; the importance of being enterprise aware.
Disciplined Agile roles: Team Lead (ScrumMaster), Product Owner, Architecture Owner, Team Member, Stakeholder + five more optional scaling roles.
Inception Phase: Covers key activities for initiating a DA team, including initial requirements modelling, initial architecture modelling, initial release planning, strategies for your physical and virtual work environments, initial risk identification, and driving to a shared vision with your stakeholders.
Construction Phase: Describes many technical strategies for building consumable increments of your solution, including test-driven development (TDD), acceptance TDD, how to initiate an iteration/sprint, look-ahead modelling and planning, spikes, regular coordination meetings, continuous integration, continuous deployment, whole-team testing, parallel independent testing, information radiators, Kanban boards, burn up charts, and many more. In this module we also look at agile construction from a traditional point of view, showing how activities such as architecture, analysis, design, testing, management, and user experience (UX) are addressed all the way through the lifecycle.
Transition Phase: Overviews strategies for releasing the solution to your stakeholders.
Because transitioning to agile can be difficult—and often wrenching—for teams, many organizations are turning to kanban practices. Kanban, which involves just-in-time software delivery, offers a more gradual evolution to agile and is adaptable to many company cultures and environments. With kanban, developers pull work from a queue—taking care not to exceed a threshold for simultaneous tasks—while making progress visible to all. Alan Shalloway shares eight steps to adopt kanban in your team and organization. He begins with a value stream map of existing processes to establish an initial kanban board, providing transparency into the state of the current workflow. Another step is to establish explicit policies to define workflow changes and engender project visibility. Because kanban can easily be expanded to cover many parts of development, another step is to increase stakeholder involvement in the process. Join this interactive session to practice these key steps with hands-on exercises. By the end, you will have an initial plan for implementing kanban in your organization.
Apply Scrum to Your Hardware & Manufacturing Projects for Better Results by H...SmitsMC LLC
Myth: You can't iterate hardware. Really? Let's talk about John Deere. In 2012, we documented that it typically took them 18 - 36 months to develop a working prototype. After working with Scrum, they had a working prototype in 8 MONTHS. This presentation demonstrates more stories like this one.
Ruby on rails web application development is becoming the popular choice for web applications development. It is popularly known as the "Language of the Cloud". Not only this Ruby on Rails also supports Agile Development.
Agile development has become a well-known and effective software development methodology. But can you take Agile, and apply it to other areas of your business, for example to hardware development?
To explore this, once again Belatrix is delighted to welcome Agile expert, Hubert Smits, to share his expertise and insights.
by Scott Ambler, Chief Methodologist for Agile, IBM and Mark Lines, Agile Mentor and cofounder of UPMentors
Once considered viable only for small, co-located teams, agile software development practices have caught the attention of larger teams seeking improvements in product quality, team efficiency, and on-time delivery. This paper introduces an approach to agile that incorporates the added discipline larger teams need for success in software and systems delivery.
Continuous Delivery of Agile ArchitectureBrad Appleton
by Brad Appleton, APLN Chicago 2018 Conference, April 2018,
Agile Development & DevOps have necessitated revisititing how architecture changes over time: collaboration, design thinking, technical debt, emergent design, evolutionary architecture, agile infrastructure, and continuous delivery have all played a key role in how we can integrate architecture into agile delivery methods.
This presentation explores proven ways to continuously plan, build & evolve software architectures to support continual change as part of the continuous value-delivery pipeline.
Loras College 2014 Business Analytics Symposium | Aaron Lanzen: Creating Busi...Cartegraph
Cisco Services is providing a behind-the-scenes perspective of its decision management and smart analytics programs. Success for Cisco is more than the technology or any one project. It's a mix of art, philosophy and technology that allows analytics to keep adding value to the business. You will hear how the program has evolved over the last 6 years and will explore different levels of smart analytics. Along the way, you will hear how the team grew a simple idea into a patent-pending resource allocation model.
For more information on the Loras College 2014 Business Analytics Symposium, the Loras College MBA in Business Analytics or the Loras College Business Analytics Certificate visit www.loras.edu/mba or www.loras.edu/bigdata.
IT Governance and Compliance in an Agile WorldTechWell
Establishing IT governance and compliance practices is essential for organizations that have regulatory or audit requirements. The good news is that you can be agile and still comply with Sarbanes-Oxley, CFR 21, HIPAA, and other regulatory imperatives. Done well, IT controls actually help you improve both productivity and quality. Bob Aiello describes how to implement IT controls in frameworks such as ISACA Cobit and ITIL v3 that many regulatory frameworks require-while maintaining agile practices. Bob's guidance includes specific examples of establishing IT controls: separation of duties, work-item to change-set traceability, physical and functional configuration audits, and more. Bob explains how these practices help government, defense, and corporations scale agile practices where audit and regulatory compliance is a must. In fact, Bob attests to the fact that a disciplined approach to agile can improve the productivity and quality of most all agile development efforts.
Artificial intelligence for faster and smarter software testing - Galway Mee...SmartBear
How Artificial Intelligence (AI) is changing software quality
Hybrid test automation framework to test identified and unidentified UI properties
Demonstration of a use case with AI in UI test automation for any skill level
Evolving toward Microservices - O’Reilly SACON KeynoteChristopher Grant
O’Reilly Software Architecture Conference Keynote 4/2016
Evolving toward Microservices
How HomeDepot.com made the switch
Video published at: https://www.oreilly.com/ideas/evolving-toward-microservices-how-home-depot-made-the-transition
Agile Portfolio Based Release Trains by Ralph JochamGeorge Psistakis
"Agile Portfolio Based Release Trains" by Ralph Jocham, SCRUM.org Certified SCRUM Trainer and founder of Effective Agile
#AgileGreece Meetup
http://www.meetup.com/Agile-Greece/
Agile DC 2013 - Comparing Scaled Agile Framework (SAFe) with Disciplined Agil...Greg Pfister
Building upon well established Scrum, XP, and lean software development methods, agile scaling frameworks such as Dean Leffingwell's Scaled Agile Framework (SAFe) and Scott Ambler's Disciplined Agile Delivery (DAD) address large, complex software delivery initiatives through their full delivery lifecycle from project initiation to production. These frameworks have received significant interest in both federal government and private industries, recognizing the need for continued team-based iterative and incremental adaptive approaches to software development, balanced with scaling processes and factors at the Program and Portfolio levels and organizational governance models and guidance for large enterprise engagements. This session will provide a brief overview of these two agile scaling models, address the benefits of what both are trying to accomplish, and compare and contrast specific similarities and differences.
IIA3: Coding Like a Unicorn (Predix Transform 2016)Predix
http://predixtransform.com
The way software is developed and run in production has changed dramatically over the past decade. These changes are just now going mainstream. Getting your advice strictly from unicorn companies is like getting dieting advice from celebrities: the tips will work if you have unlimited resources, few constraints, and, well, are already successful. Learn what those who work in the real world do to get the benefits of being cloud native!
SymEx 2015 - How to Make Your Major IT Projects Fly with the Help of IT Gove...PMI Indonesia Chapter
This presentation by Markus Walter will introduce an innovative approach how to handle major IT programs and projects, which explicitly have their own rules and characteristics. Addressing these “Elephant”-projects from a broader perspective dramatically increases the change for successful execution, supports stakeholder expectation management and positively affects the company’s Project Management culture. IT Governance may be applied to gain this oversight. Established frameworks, like PMBok, COBIT, ITIL and TOGAF, help to put major projects in the right and effective context. The presentation kicks-off with the analysis of challenges IT projects are facing in the real-world Project Management environment and the role of IT Governance to provide benefit. Therefore IT Governance is de-mystified and a mapping to the PMBoK will be discussed. A show case demonstrates the application of this approach in practice and provided further insights. The presentation closes by sharing Lessons Learned and communicating practical take away.
Agile development way works good for small projects and also works good for big project in the beginning. But most of time, the big projects face the same situation as projects not using Agile way. Adapt process and practice in system module design wise, team structure wise, project plan wise help big projects live better.
How to Achieve Gapless End-to-End Traceability in Hardware and Software Devel...Intland Software GmbH
Maintaining traceability throughout the lifecycle helps a great deal in staying in control of your development processes, whether it’s a hardware or software product that you are working on. It could help improve processes, product quality, transparency, and cost control. Watch this webinar recording to learn how codeBeamer can help you ensure traceability between all your work items across the entire lifecycle, even across projects.
Ruby on rails web application development is becoming the popular choice for web applications development. It is popularly known as the "Language of the Cloud". Not only this Ruby on Rails also supports Agile Development.
Agile development has become a well-known and effective software development methodology. But can you take Agile, and apply it to other areas of your business, for example to hardware development?
To explore this, once again Belatrix is delighted to welcome Agile expert, Hubert Smits, to share his expertise and insights.
by Scott Ambler, Chief Methodologist for Agile, IBM and Mark Lines, Agile Mentor and cofounder of UPMentors
Once considered viable only for small, co-located teams, agile software development practices have caught the attention of larger teams seeking improvements in product quality, team efficiency, and on-time delivery. This paper introduces an approach to agile that incorporates the added discipline larger teams need for success in software and systems delivery.
Continuous Delivery of Agile ArchitectureBrad Appleton
by Brad Appleton, APLN Chicago 2018 Conference, April 2018,
Agile Development & DevOps have necessitated revisititing how architecture changes over time: collaboration, design thinking, technical debt, emergent design, evolutionary architecture, agile infrastructure, and continuous delivery have all played a key role in how we can integrate architecture into agile delivery methods.
This presentation explores proven ways to continuously plan, build & evolve software architectures to support continual change as part of the continuous value-delivery pipeline.
Loras College 2014 Business Analytics Symposium | Aaron Lanzen: Creating Busi...Cartegraph
Cisco Services is providing a behind-the-scenes perspective of its decision management and smart analytics programs. Success for Cisco is more than the technology or any one project. It's a mix of art, philosophy and technology that allows analytics to keep adding value to the business. You will hear how the program has evolved over the last 6 years and will explore different levels of smart analytics. Along the way, you will hear how the team grew a simple idea into a patent-pending resource allocation model.
For more information on the Loras College 2014 Business Analytics Symposium, the Loras College MBA in Business Analytics or the Loras College Business Analytics Certificate visit www.loras.edu/mba or www.loras.edu/bigdata.
IT Governance and Compliance in an Agile WorldTechWell
Establishing IT governance and compliance practices is essential for organizations that have regulatory or audit requirements. The good news is that you can be agile and still comply with Sarbanes-Oxley, CFR 21, HIPAA, and other regulatory imperatives. Done well, IT controls actually help you improve both productivity and quality. Bob Aiello describes how to implement IT controls in frameworks such as ISACA Cobit and ITIL v3 that many regulatory frameworks require-while maintaining agile practices. Bob's guidance includes specific examples of establishing IT controls: separation of duties, work-item to change-set traceability, physical and functional configuration audits, and more. Bob explains how these practices help government, defense, and corporations scale agile practices where audit and regulatory compliance is a must. In fact, Bob attests to the fact that a disciplined approach to agile can improve the productivity and quality of most all agile development efforts.
Artificial intelligence for faster and smarter software testing - Galway Mee...SmartBear
How Artificial Intelligence (AI) is changing software quality
Hybrid test automation framework to test identified and unidentified UI properties
Demonstration of a use case with AI in UI test automation for any skill level
Evolving toward Microservices - O’Reilly SACON KeynoteChristopher Grant
O’Reilly Software Architecture Conference Keynote 4/2016
Evolving toward Microservices
How HomeDepot.com made the switch
Video published at: https://www.oreilly.com/ideas/evolving-toward-microservices-how-home-depot-made-the-transition
Agile Portfolio Based Release Trains by Ralph JochamGeorge Psistakis
"Agile Portfolio Based Release Trains" by Ralph Jocham, SCRUM.org Certified SCRUM Trainer and founder of Effective Agile
#AgileGreece Meetup
http://www.meetup.com/Agile-Greece/
Agile DC 2013 - Comparing Scaled Agile Framework (SAFe) with Disciplined Agil...Greg Pfister
Building upon well established Scrum, XP, and lean software development methods, agile scaling frameworks such as Dean Leffingwell's Scaled Agile Framework (SAFe) and Scott Ambler's Disciplined Agile Delivery (DAD) address large, complex software delivery initiatives through their full delivery lifecycle from project initiation to production. These frameworks have received significant interest in both federal government and private industries, recognizing the need for continued team-based iterative and incremental adaptive approaches to software development, balanced with scaling processes and factors at the Program and Portfolio levels and organizational governance models and guidance for large enterprise engagements. This session will provide a brief overview of these two agile scaling models, address the benefits of what both are trying to accomplish, and compare and contrast specific similarities and differences.
IIA3: Coding Like a Unicorn (Predix Transform 2016)Predix
http://predixtransform.com
The way software is developed and run in production has changed dramatically over the past decade. These changes are just now going mainstream. Getting your advice strictly from unicorn companies is like getting dieting advice from celebrities: the tips will work if you have unlimited resources, few constraints, and, well, are already successful. Learn what those who work in the real world do to get the benefits of being cloud native!
SymEx 2015 - How to Make Your Major IT Projects Fly with the Help of IT Gove...PMI Indonesia Chapter
This presentation by Markus Walter will introduce an innovative approach how to handle major IT programs and projects, which explicitly have their own rules and characteristics. Addressing these “Elephant”-projects from a broader perspective dramatically increases the change for successful execution, supports stakeholder expectation management and positively affects the company’s Project Management culture. IT Governance may be applied to gain this oversight. Established frameworks, like PMBok, COBIT, ITIL and TOGAF, help to put major projects in the right and effective context. The presentation kicks-off with the analysis of challenges IT projects are facing in the real-world Project Management environment and the role of IT Governance to provide benefit. Therefore IT Governance is de-mystified and a mapping to the PMBoK will be discussed. A show case demonstrates the application of this approach in practice and provided further insights. The presentation closes by sharing Lessons Learned and communicating practical take away.
Agile development way works good for small projects and also works good for big project in the beginning. But most of time, the big projects face the same situation as projects not using Agile way. Adapt process and practice in system module design wise, team structure wise, project plan wise help big projects live better.
How to Achieve Gapless End-to-End Traceability in Hardware and Software Devel...Intland Software GmbH
Maintaining traceability throughout the lifecycle helps a great deal in staying in control of your development processes, whether it’s a hardware or software product that you are working on. It could help improve processes, product quality, transparency, and cost control. Watch this webinar recording to learn how codeBeamer can help you ensure traceability between all your work items across the entire lifecycle, even across projects.
DOES14 - Gary Gruver - Macy's - Transforming Traditional Enterprise Software ...Gene Kim
Gary Gruver, Vice President of QE, Release and Operations, Macy's, at DevOps Enterprise Summit 2014
Transforming Traditional Enterprise Software Development Processes by applying DevOps and Agile Principles at Scale
How to transform traditional Enterprise Software development processes by applying DevOps and Agile principles at scale instead of the more typical approach of scaling scrum. This approach starts with clarity in business objectives for the transformation. Next it highlights the importance of creating an Enterprise level continuous improvement process, which is very different from an aggregation of team level continuous improvement process. One of the most important steps for creating an Agile Enterprise is keeping code releasable across the Enterprise. This presentation will go deep on the fundamentals of Devops, CI, and CD based on what has been found to be successful transforming legacy organizations. The final step will provide a framework for re-thinking the planning process to provide an Enterprise level backlog and long-term commitments.
DevOps Will Save The World! : Public Safety, Public Policy, and DevOps In Context
Joshua Corman, CTO, Sonatype
Link to video: https://www.youtube.com/watch?v=K-hskShNyoo
Building a Service Delivery Platform - JCICPH 2014Andreas Rehn
This talk will walk through the critical parts of a tool chain that forms the service delivery platform, a robust, secure solution with Jenkins as the main orchestrator that scales with many teams and hundreds of pipelines. I will show a tool chain with Git, Jenkins, Jenkins Job Builder, Puppet, Graphite, Logstash and more that is proven in battle. I will share insights and details on good ways of building a platform for pipelines that recognizes the individual teams needs for fast feedback, traceability and visibility in the delivery process.
Agile and Automation have been growing up together over the past decade. Neither practice nor toolset evolves in a vacuum. Rather, they inform each-other.
This presentation looks at this history, with an eye towards where the current trends are pushing us.
DevOps is not a new technology or a product. It’s an approach or culture of software development that seeks stability and performance at the same time that it speeds software deliveries to the business. In this sharing, we will discuss what DevOps is from CAMS model that represents culture, automation, measurement and sharing. In addition, I will share some practical experiences in Trend Micro.
Balancing the tension between Lean and AgileJames Coplien
Many people equate Lean and agile or claim that one is a subset of the other. In fact, they have almost opposite emphases: thinking versus doing; teams versus individuals; planning versus reacting; and many more. This talk will help you clarify the distinction in a way that will help you focus soberly on how to improve your environment, team, product and process, by going beyond the buzzwords to the fundamental building blocks.
Some history, background and information about the building of software at LinkedIn. This presentation was delivered at the Gradle Summit 2013 so it has a Gradle focus, but covers many other types of tooling and integration.
Continuous Integration promises faster delivery of higher quality software through an integrated automated build, test, and release management.
The greater challenge lies not within a project or team, but as you look to scale this across a larger organization or enterprise-wide. How do you allow teams to choose the tools and processes, yet ensure all stakeholders have full visibility and traceability across all your delivery pipelines and in real time?
In this webinar, we will demonstrate how you can implement a CI environment leveraging popular open source tools (or any tool) using TeamForge.
apidays LIVE Paris - Growing an API Culture by Saul Caganoff & Liz Douglassapidays
apidays LIVE Paris - Responding to the New Normal with APIs for Business, People and Society
December 8, 9 & 10, 2020
Growing an API Culture
Saul Caganoff, Principal at Deloitte Platform Engineering
Liz Douglass, Partner at Deloitte
apidays LIVE Australia 2020 - Growing an API Culture by Liz Douglass & Saul C...apidays
apidays LIVE Australia 2020 - Building Business Ecosystems
Growing Domain APIs - "T'aint what you do..."
Liz Douglass, Partner at Deloitte & Saul Caganoff, Principal at Deloitte
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Agile is based on a collection of practices that have been found to work, some of them very old.
Automation allows fewer people to do more work, but that doesn’t necessarily mean more product, it may simply mean higher quality product.
No, no they don’t. Quite the contrary actually.
Continuous integration is the goal because it is the ultimate enabler for successful Agility. Without continuous or at least frequent integration including automated build, and automated testing for at least Integration and Unit tests an agile transformation will fail to provide the long term benefits organizations need.
I tried to count the number of different tools used for software development, my line count from cutting and pasting them out of wikipedia hit 2694 before I gave up. Software these days is similar in a great many ways to the Space Race, or Arms Races of the past.
Devops is a reaction to the frequent and continuous deployment that Agile teams work towards (and are achieving), and why this is a problem using anecdotes about product increment deliveries.
Servers lurking in basements running unauthorized software?
IT organizations are rapidly moving an end-to-end IT process that is collaborative, agile, distributed and in the cloud. However the legacy tools most companies are using have the following issues:
Limited Business Agility - The legacy tools are built around LAN based SCM tools that simply don’t work well in fast changing application cycles desired by more modern agile working teams. This is one of the reasons we have seen the market leading adoption of Subversion which was built for distributed teams and agile development and the increasing reduction of Rational Clear Case usage. In addition, the SDLC tools were optimized for waterfall development. But from a traceability perspective, even with solid requirements and structured waterfall practices, it’s difficult to trace these requirements accurately through the ALM lifecycle because within a project, team members work in different tools as a function of their task – most times these tools are silo’d
Lack of Enterprise Scalability and Visibility - Processes, tools, and data are often incompatible with other project teams, making visibility and sharing even more difficult. Distributed teams are disconnected and the ability to collaborate and re-use is difficult, at best. Without a scalable connected platform, clients and business users are left on the outside of the development process, reducing the odds that whatever is ultimately deployed is correct – which of course leads to excess costs, waste, overruns, and customer satisfaction issues.
Difficult to Modernize – IT organizations struggle with the need to reduce maintenance costs and allocate these resources to client focused innovation and higher margins. As legacy tools lack centralization, this has led to application sprawl with one-offs, redundant and aged apps, and an increasing year over year cost of maintenance and support.
To put it simple, scaling Agility is hopeless without the right infrastructure. Let’s have a quick look, why this is the case.
It’s easy to get lost in the details, and loose oversights. That applies certainly to senior management, as they lack insights into project status, and into risk factors. That can lead to costly surprises. But also business product managers and chief architects lack vital visibility, across interdependent projects. For example, often they cannot answer even basic questions like: “In which release will defect ABC be fixed?” or “How many user stories have we delivered in the current build, and how many source code files did we touch?”
Security is another key issues, especially as you work across organizational boundaries, or have to deal with increasingly fickly workforce. There is the risk of giving too much permissions and access to code base and documentations, resulting in overwhelmed developers or (at worst) loss of IP and potentially even legal compliance violations. But there also is risk of providing too little access too late, frustrating staff and impeding their ability to deliver.
Ineffective collaboration… While technology can help, this continuous to be especially the case, if tools don’t work across the firewall divide, or are simply not scalable from a performance and throughput perspective.
Unaware how code changes affect production. Early and continuous delivery of valuable software is the #1 principle behind the Agile Manifesto. That’s why Agile practices demand looking beyond code, to build and test. Continuous integration (CI) and test-driven development are accepted as critical elements to accelerate the software delivery process. However, exclusive focus on automating the build and test process in not enough. Without the right visibility, development teams cannot deal timely with defects, and don’t understand how code affects production, resulting in technical debt.
Finally, uncontrolled high cost of development It infrastructure management by cobbling together an arsenal of incompatible products and tools.
To put it simple, scaling Agility is hopeless without the right infrastructure. Let’s have a quick look, why this is the case.
It’s easy to get lost in the details, and loose oversights. That applies certainly to senior management, as they lack insights into project status, and into risk factors. That can lead to costly surprises. But also business product managers and chief architects lack vital visibility, across interdependent projects. For example, often they cannot answer even basic questions like: “In which release will defect ABC be fixed?” or “How many user stories have we delivered in the current build, and how many source code files did we touch?”
Security is another key issues, especially as you work across organizational boundaries, or have to deal with increasingly fickly workforce. There is the risk of giving too much permissions and access to code base and documentations, resulting in overwhelmed developers or (at worst) loss of IP and potentially even legal compliance violations. But there also is risk of providing too little access too late, frustrating staff and impeding their ability to deliver.
Ineffective collaboration… While technology can help, this continuous to be especially the case, if tools don’t work across the firewall divide, or are simply not scalable from a performance and throughput perspective.
Unaware how code changes affect production. Early and continuous delivery of valuable software is the #1 principle behind the Agile Manifesto. That’s why Agile practices demand looking beyond code, to build and test. Continuous integration (CI) and test-driven development are accepted as critical elements to accelerate the software delivery process. However, exclusive focus on automating the build and test process in not enough. Without the right visibility, development teams cannot deal timely with defects, and don’t understand how code affects production, resulting in technical debt.
Finally, uncontrolled high cost of development It infrastructure management by cobbling together an arsenal of incompatible products and tools.
If it isn’t easy then it doesn’t get done.
Best of Breed is a concept is a marketer’s fantasy. Software tools must be constantly evaluated and replaced as needed. No one tool is the king forever, and more then that no one tool is perfect for every team. Team’s must be empowered to select the correct tools for the work that they are doing.