The document discusses the three levels of agile planning: release, iteration, and task planning. It describes the process for defining a release plan including estimating velocity, organizing stories into iterations, and allowing for plan variations. Iteration planning and task planning are also summarized, including when they occur, who is involved, and an example task board.
Session Abstract:
Agile framework is based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. It’s a set of values and principles that help teams respond to unpredictability through incremental, iterative work cadences and continuous feedback.
Scrum is the most popular methodology under the Agile umbrella. Scrum emphasizes empirical feedback, team self-management, and striving to build shippable product increments within short iterations.
Kanban is another popular flavor of Agile that focuses on visualizing and managing the flow of work, in order to balance demand with available capacity and remove bottlenecks.
Learning Objectives:
> Gain a broad understanding of the Agile framework
> Discover Scrum and Kanban, the two most widely used Agile methodologies, and see how they can be used in construction industry
> Find out how Scrum and Kanban can be combined to have the best of both worlds (Scrumban)
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
Given that Agile is an iterative and incremental process, it should come as no surprise that there are different levels of Agile planning to help deliver value early while working toward a larger goal. To find success with Agile, it’s important to understand how to effectively plan at the release, iteration, story, and task levels.
What you’ll learn in this presentation:
• The basics of release and iteration planning.
• The differences between a release and an iteration.
• The basics of task planning.
Sprint Planning in Scrum and How to do it without Tearing Your Eyes OutJason Knight
There are 4 formal events in Scrum:
Sprint Planning
The Daily Scrum
The Sprint Review
Sprint Retrospective
This talk walks through the Scrum Guide's description of Sprint Planning, an example Sprint Planning event, and some suggestions of how to run an effective Sprint Planning session without tearing your eyes out.
Session Abstract:
Agile framework is based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. It’s a set of values and principles that help teams respond to unpredictability through incremental, iterative work cadences and continuous feedback.
Scrum is the most popular methodology under the Agile umbrella. Scrum emphasizes empirical feedback, team self-management, and striving to build shippable product increments within short iterations.
Kanban is another popular flavor of Agile that focuses on visualizing and managing the flow of work, in order to balance demand with available capacity and remove bottlenecks.
Learning Objectives:
> Gain a broad understanding of the Agile framework
> Discover Scrum and Kanban, the two most widely used Agile methodologies, and see how they can be used in construction industry
> Find out how Scrum and Kanban can be combined to have the best of both worlds (Scrumban)
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
Given that Agile is an iterative and incremental process, it should come as no surprise that there are different levels of Agile planning to help deliver value early while working toward a larger goal. To find success with Agile, it’s important to understand how to effectively plan at the release, iteration, story, and task levels.
What you’ll learn in this presentation:
• The basics of release and iteration planning.
• The differences between a release and an iteration.
• The basics of task planning.
Sprint Planning in Scrum and How to do it without Tearing Your Eyes OutJason Knight
There are 4 formal events in Scrum:
Sprint Planning
The Daily Scrum
The Sprint Review
Sprint Retrospective
This talk walks through the Scrum Guide's description of Sprint Planning, an example Sprint Planning event, and some suggestions of how to run an effective Sprint Planning session without tearing your eyes out.
Prioritization Techniques for Agile TeamsTarang Baxi
Have you ever been in a prioritization discussion where the only priorities are High, Higher, and Highest? Or tried using MoSCoW to prioritize user stories only to find
that 80% of the cards are 'Must Have'?
In this tutorial, we introduce a gamut of different prioritization methods, ranging from simple techniques like stacked ranking or MoSCoW that classify items along a single dimension to multi-dimensional techniques like priority quadrants, Story Maps, and Innovation Games®. We cover pruning feature trees, spending fake currency, and using visual metaphors, while truly identifying what the most important stuff really is. This was most recently presented at the Agile India 2013 conference in Bangalore.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
Backlog refinement is not a Scrum event, but instead is an ongoing activity during the Sprint required to decompose, describe, estimate, and order backlog items in the Product Backlog.
This material is divided into two sections. The first section reviews the basics of backlog refinement, covering various options for conducting the activity. The second section covers tips for maintaining a healthy backlog and potential anti-patterns.
This material was presented at Agile New England in July and August 2022 as "101" introduction and "202" advanced sessions.
Preparing and running a fully remote PI Planning session is complex and different than an in-person event. This slide deck was used during an Applied Frameworks' webinar with John Mulligan and Kevin Rosengren, both principal consultants, who talked about how best to prepare for remote PI Planning from the perspective of an RTE and ScrumMaster.
The basics of Agile and Waterfall Project management methodologies. Description when each approach can be applied.
Advices How to create a Product backlog and how to colect requirements. Sprint planning, Burndown chart, Demonstration, Retrospective, Tasks board examples.
Introduction to Agile Estimation & PlanningAmaad Qureshi
Presented by Natasha Hill & Amaad Qureshi
In this session, we will be covering the techniques of estimating Epics, Features and User Stories on an Agile project and then of creating iteration and release plans from these artefacts.
Agenda
1. Why traditional estimation approaches fail
2. What makes a good Agile Estimating and Planning approach.
3. Story points vs. Ideal Days
4. Estimating product backlog items with Planning Poker
5. Iteration planning - looking ahead and estimating no more than a few week ahead.
6. Release planning - creating a longer term plan, typically looking ahead, 3-6 months
7. Q&A
What you’ll learn in this presentation;
How estimates are used on Agile projects.
How to define estimates.
The basics of planning poker to help estimate.
Estimating user stories is central to the Agile planning process. An estimate is a measure of the relative size, in terms of effort, of a story. These estimates help answer questions such as:
• How many stories can we fit into the release?
• How many stories will be completed in the next iteration?
• What are the impacts of adding, removing and changing stories?
What you’ll learn in this presentation:
• How estimates are used on Agile projects.
• How to define estimates.
• The basics of planning poker to help estimate.
Prioritization Techniques for Agile TeamsTarang Baxi
Have you ever been in a prioritization discussion where the only priorities are High, Higher, and Highest? Or tried using MoSCoW to prioritize user stories only to find
that 80% of the cards are 'Must Have'?
In this tutorial, we introduce a gamut of different prioritization methods, ranging from simple techniques like stacked ranking or MoSCoW that classify items along a single dimension to multi-dimensional techniques like priority quadrants, Story Maps, and Innovation Games®. We cover pruning feature trees, spending fake currency, and using visual metaphors, while truly identifying what the most important stuff really is. This was most recently presented at the Agile India 2013 conference in Bangalore.
Join BostonPHP and Michael Bourque as he presents the concept of Scrum and shows why so many people are now deploying scrum to their development projects. Michael will take us through the process and talk about how his company, Parametric Technology Inc. (PTC) , is successfully applying Scrum.
Backlog refinement is not a Scrum event, but instead is an ongoing activity during the Sprint required to decompose, describe, estimate, and order backlog items in the Product Backlog.
This material is divided into two sections. The first section reviews the basics of backlog refinement, covering various options for conducting the activity. The second section covers tips for maintaining a healthy backlog and potential anti-patterns.
This material was presented at Agile New England in July and August 2022 as "101" introduction and "202" advanced sessions.
Preparing and running a fully remote PI Planning session is complex and different than an in-person event. This slide deck was used during an Applied Frameworks' webinar with John Mulligan and Kevin Rosengren, both principal consultants, who talked about how best to prepare for remote PI Planning from the perspective of an RTE and ScrumMaster.
The basics of Agile and Waterfall Project management methodologies. Description when each approach can be applied.
Advices How to create a Product backlog and how to colect requirements. Sprint planning, Burndown chart, Demonstration, Retrospective, Tasks board examples.
Introduction to Agile Estimation & PlanningAmaad Qureshi
Presented by Natasha Hill & Amaad Qureshi
In this session, we will be covering the techniques of estimating Epics, Features and User Stories on an Agile project and then of creating iteration and release plans from these artefacts.
Agenda
1. Why traditional estimation approaches fail
2. What makes a good Agile Estimating and Planning approach.
3. Story points vs. Ideal Days
4. Estimating product backlog items with Planning Poker
5. Iteration planning - looking ahead and estimating no more than a few week ahead.
6. Release planning - creating a longer term plan, typically looking ahead, 3-6 months
7. Q&A
What you’ll learn in this presentation;
How estimates are used on Agile projects.
How to define estimates.
The basics of planning poker to help estimate.
Estimating user stories is central to the Agile planning process. An estimate is a measure of the relative size, in terms of effort, of a story. These estimates help answer questions such as:
• How many stories can we fit into the release?
• How many stories will be completed in the next iteration?
• What are the impacts of adding, removing and changing stories?
What you’ll learn in this presentation:
• How estimates are used on Agile projects.
• How to define estimates.
• The basics of planning poker to help estimate.
A keynote to help people involved in software product development to execute the right agile and lean practices in order to see a successful relationship among stakeholders.
- Agile values and manifesto
- Scrum in details
- Themes, epics, and user stories
- Combining and splitting user stories.
- What could go wrong in Scrum and why?
- Overview in Other Agile methodologies:
- XP Agile Methodology
- KanBan Agile Methodology.
In this quality assurance training session, you will learn Agile in QA. Topics covered in this course are:
• Introduction to Agile
• Agile - Manifesto
• Agile over Traditional Method
• Principles of Agile
• Roles in Agile
• What is a User Story?
• Relationship of User Stories and Tasks
• How an Agile Team Plans its Work?
• When a Story is Done
To know more, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-quality-assurance-qa-training-with-hands-on-exercises/
A retrospective is a meeting to look back over an iteration, release, or project, specifically to discuss what worked well, what could be improved, and most importantly, how to translate the lessons learned into actionable change. Retrospectives are a forum for the team to improve upon their process. They’re an integral part of Scrum and Extreme Programming (XP).
Managing a team and project are quite synonymous. Especially, teams require effective distribution of responsibility / roles. Once that is setup, a proper process guides people to make progress. All this fits into a product lifecycle, which is essential to develop the right product, in the right way, and deliver it at the right time.
Hello Class- This is a very rough draft of the assignment. I have SusanaFurman449
Hello Class- This is a very rough draft of the assignment. I have broken down each section and potential opportunities for you. This is not all inclusive as you can be creative but you must meet the deliverables of this assignment.
Scope and Schedule: At the end of week 4, you are to finalize the initially approved scope from week two and start building the project schedule. In this week, you are also to work on building the project Work-Breakdown Structure (WBS). Project scope and schedule will include the following components:
- Finalized project scope
- Project requirements – in more details
- WBS structure
- Developed project schedule
- Identify key milestones and deliverables
- Outline project resources and assign them to tasks accordingly.
- Stakeholder engagement – communication plan
Make sure that there is a heading for each section.
Title Page – Name, date, etc
· Finalized Project Scope: Chapter 7 Scope Planning,
I just want a summary of what your final scope is.
· Project Requirements – Details
· WBS Structure- (Week 3) Chapter 7 Video, How to construct a WBS?
·
· Developed Project Schedule – Chapter 8 Video – Develop Project Schedule, Chapter 8 Reading Scheduling Projects – May ways to show schedule just pick one.
Develop Project Schedule
Once you have an estimated duration for each activity in the network must determine (based on durations and sequence) whether the project can be realistically finished by the required completion time.
· In order to do this, the contractor should estimate the duration of each activity.
· He or she should establish an overall window of time for the project.
Develop a project schedule that provides a timetable for each activity and shows:
· The earliest times (or dates) at which each activity can start and finish, based on the project estimated start time (or date)
· The latest times (or dates) by which each activity must start and finish in order to complete the project by its required completion time (or date)
· Incorporate Changes into Schedule
· Throughout a project, changes may occur that impact the schedule.
· Changes might be initiated by the customer or the project team, or they might be the result of an unanticipated occurrence.
· Changes requested early in the project may have less of an impact on schedule and budget than those requested later in the project.
· When the customer requests a change, the contractor or project team should estimate the impact on the project schedule and budget and then obtain customer approval before proceeding.
· If the customer approves the proposed revisions to the project schedule and budget, then any additional activities, revised estimated durations, and revised estimated resources and associated costs should be incorporated into the project schedule and budget.
· With respect to the project schedule, changes can result in the addition or deletion of activities, re-sequencing of activities, changes to estimated durations for specific activi ...
Challenges in Traditional Organizations
• Impact on Agile Process
• Tweaking Agile For Your Situation
Development in short iterative cycles builds better trust
relationship and a stronger engagement between the
product owner/ customer and the development team.
Stay tuned for our upcoming webinars at https://www.synerzip.com/webinars/ that might be of your interest.
Agile and Scrum Overview for PMs, Designers and Developers Aaron Roy
This is an overview of the flavor of agile/scrum I had my team use at Bond in Q2 2017. We heavily emphasized the importance of having a shared language between cross-functional teams and this deck was meant as a primer that could be shared between product managers, designers, and developers.
Similar to Agile Release & Iteration Planning (20)
Software quality assurance (SQA) is defined as a planned and systematic approach to the evaluation of the quality of and adherence to software product standards, processes, and procedures.This systematic approach is actually quite different in Agile and non-Agile environments. There are several key differences in these approaches that we’ll address in this presentation.
The process of adopting Agile in any organization is challenging in many ways. It is especially challenging in larger organizations because of complex infrastructures, numerous legacy systems and mature organizational cultures. These larger organizations often underestimate the difficulty of getting Agile right.
This presentation will focus on the common challenges of Agile adoption. Tips are provided to help improve the chances of Agile adoption success.
Implementing Agile is not as simple as introducing and applying a methodology. Agile also requires a comprehensive culture change and mindset shift—a process that grows in difficulty with an organization’s size and scope.
In keeping with Agile’s inherent “get it done” philosophy, organizations should consider some key steps to get their own Agile initiative moving.
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
Agile has an inherent focus on teams. The Agile principle, “Individuals and interactions over processes and tools” stresses the importance of how people work together. Therefore, strong Agile team dynamics is a key component of a high functioning Agile organization.
In this presentation, you’ll learn about the signs to look for in a dynamic Agile team room and how to get a team performant – and happy.
Gathering and defining software requirements is difficult.
One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want.
While user stories help convert concepts into functions, writing good user stories is easier said than done.
There are dozens of myths about Agile development. But before jumping into specific misconceptions, let’s have a look at some common business challenges:
For senior-level execs: do you value revenue growth or cost containment?
For project managers: do you value team efficiency or effectiveness?
For developers: do you value code quantity or quality?
In each scenario, you probably struggled to make a choice given that your two options were not mutually exclusive.
Posing the question this way creates a false dilemma since you likely value both options but to varying degrees. So the better question is, of the two options, which do you value more?
More organizations are recognizing the many benefits that Agile delivers.
As organizations start embracing the approach, there are gaps in understanding about what it is, what it involves and what value it brings.
What is Agile Development is the first in a series of Agile eBooks from Intelliware Development intended to help eliminate those gaps.
2015 will be the year that wearables take off. Much of the excitement around wearables will be directly tied to the launch of the Apple Watch, but this will also be the year that enterprises recognize the business opportunity of wearables. Here are some calls to action that enterprises should consider in 2015:
1. Consider if and how Apple Watch might supplement your organization’s current mobile offerings;
2. Consider the use of wearable devices to aid internal or customer-facing processes;
3. Be up-front about data collection and conscious of potential privacy concerns; and
4. Recognize that the next two years will see a lot of churn in the wearable space; don’t wait for the space to settle but, instead, charter early wearable pilots with the knowledge that some initial investment might be throwaway.
Agile Testing: A pragmatic overview and new entry in Intelliware’s Agile Methodology Series.
What you’ll learn in this presentation:
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
The presentation covers:
- Why do we use Agile testing?
- What Agile testing isn’t
- What Agile testing is: unit testing and test-driven development (TDD)
- High-level properties of good tests
- Testing in different languages
- Test suites and code coverage
- Using mock objects to help isolate units
- Beyond unit testing
When developing software, user experience isn’t a feature or an attribute of the product. It’s not something you create a story for and complete in a sprint. In the context of development, UX is a way of thinking. In the context of UAT, UX is judgement.
When you adopt this philosophy, you see that UX is everyone’s responsibility and it’s everywhere. The same problems we solve while shopping at the grocery store, commuting to work, or ordering something from a restaurant, can be applied to the applications that we build. It’s an old discipline under a new name.
How then, do we train ourselves to see the world, and by extension our applications, in this manner? And how can we leverage problems we’ve already solved in the digital space?
In this presentation, you’ll learn about:
What is User Experience?
What is a User Experience Designer?
Wayfinding
Controls
Choice Architecture
Branding
Layouts
What is code? Why code? When should I start
coding? How can I get started? Where do I go? If you're asking yourself any of these questions, this infographic is for you!
It should come as no surprise to anyone involved with HL7 v3 implementations in Canada that the v3 standard is now almost-universally considered to be a failure. As an e-Health implementer, I’ve certainly felt the pain of HL7 v3, but I held my nose and used it anyway because I believed in the original goals of v3: standards-based data integration and electronic health records. They’re goals I still believe in.
The good news is that I don’t have to hold my nose any longer. HL7’s Fast Healthcare Interoperability Resources (FHIR) has learned from the mistakes of HL7 v3, and is surprisingly delightful. At the high level, I’d argue HL7 v3 failed for these reasons:
1. The models and messages of HL7 v3 were a much higher degree of complexity than was found in almost any other XML-based messaging standard.
2. That complexity could not be easily mitigated with easy access to clear documentation, as implementation documentation needed to be cobbled together from many different sources (e.g.: “universal” documents from the HL7 organization, pan-Canadian standards from Canada Health Infoway, and jurisdiction-specific documents from a repository implementation team).
3. The HL7 v3 standards lacked a useful extension model. The official process of “constraining” the standard for a particular jurisdiction was seldom sufficient, and essentially all of the jurisdictions ended up implementing systems that diverged from the published standards to support legitimate operational needs.
4. The defined HL7 v3 data types introduced a number of complications for implementing compliant HL7 v3 systems.
5. Finally, terminology is a surprisingly complex area.
This document will discuss some of these topics in more detail, and describe some of the ways in which the FHIR™ standard has corrected the failings of HL7 v3.
Software is eating the world. The figures to support this are quite compelling. In this presentation, we present 21 compelling facts, figures, and stats about the software development industry. These are focused on 4 categories: the software market, software developers, software problems and custom software. We provide answers to questions such as:
- What is the global IT spend?
- What is the global software spend?
- How fast is the software as a service (SaaS) market growing?
- What percentage of venture capital investments are in software companies?
- How many developers are there in the world? How many Java developers?
- What percentage of (large) software projects run over time and budget?
- What is the growth rate of software productivity?
- What percent of software spend is on custom software?
- What is the average annual custom software spend by large UK financial services companies?
- What percentage of companies spend more than half of their software budget on customer software?
- And more.
Agile has an inherent focus on teams. The Agile principle, “Individuals and interactions over processes and tools” stresses the importance of how people work together. Therefore, strong Agile team dynamics is a key component of a high functioning Agile organization.
In this presentation, you’ll learn about the signs to look for in a dynamic Agile team room and how to get a team performant - and happy.
The 11 Signs of Good Agile Room Dynamics
1. Deliverables are everyone’s responsibility.
2. Team Lead and Architect roles may be designated, but delivery is everyone’s responsibility.
3. Everyone is engaged & respected.
4. Healthy debate and conflict happens – and compromise.
5. Whiteboard sessions.
6. Members help each other.
7. Team members have confidence in each others’ abilities.
8. No egos.
9. Buzz in the room.
10. Celebrations of small successes.
11. Music.
How to Maintain Healthy Agile Project Room Dynamics
These are the things that Agile Teams implement to maintain healthy project room dynamics:
1. Group negotiation of team rules.
2. Team lunches.
3. Storming as a given.
4. Pairing negotiation.
5. Always listen in.
6. Conflict amongst team members.
7. Decisions.
8. Engage the larger development team.
9. Incorporating new team members.
10. Humour & food.
Codes and Terminology are topics that are easy to introduce, but tricky to understand in full complexity. IT Professionals encounter “codes” all the time. e-Health’s notion is really no different.
This presentation focused on following aspects of HL7v3:
» Concepts
» Code Data Types
» Concept Domains, Code Systems and Value Sets
» Implementation Concerns
Gathering and defining software requirements is difficult. One Agile technique to help address this challenge is writing user stories, which are short descriptions of functions that an end-user would want. While user stories help convert concepts into functions, writing good user stories is easier said than done.
What you’ll learn in this presentation:
• The basics of user stories.
• How user stories fit into the overall Agile planning process.
• How to write a user story.
Raul Vieira of Intelliware's Mobile Centre of Excellence discusses best practices for mobilizing your enterprise using Liferay.
For more information on the 2013 Toronto Liferay Roadshow, visit:
About 15% of the world's population, or 1 billion people, live with a disability. With internet penetration steadily growing at double-digit annual rates, the inclusive practice of making websites usable by people of all abilities and disabilities is becoming increasingly important. Organizations, such as the World Wide Web Consortium (W3C), have set guidelines on how to create accessible websites.
Governments across the world have taken notice of web accessibility. In Ontario, Canada, the Provincial Government has created the "Accessibility for Ontarians with Disabilities Act" (AODA), which includes accessibility for websites.
This presentation was designed to help Ontario municipalities with web accessibility. Check it out if any of these questions are of interest to you:
- Why make our municipal website accessible?
- When do we have to make it accessible?
- What makes it accessible?
- How to make it accessible?
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
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.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
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.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
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.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
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
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
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.