a critical view on business changes in our age, and the impact they are having on structures and organizations which were defined in another century and are not anymore suited for today purposes. Who has the courage to challenge those structure and fully embrace change and uncertainty? How can an agile approach help to better support those changes?
Application Lifecycle Management and Agile, friends... or foes? (Andrea Toma...Andrea Tomasini
The whole idea of ALM stems from the need to manage in an integrated manner the relationship between business processes and engineering processes. Attempting to integrate practices, information and tools for disciplines such as Requirement Engineering, Project Management, Configuration Management has long been a driver, with the important goal of achieving more transparency, and also more control. Centralization of information into a single authoritative repository moved many original ALM initiatives, but how does that fit with more modern Agile approaches? Is it really possible to have Agile ALM? What would we keep of ALM and what of Agile? Are ALM and Agile friends... or foes? This keynote will offer an agile and pragmatic perspective to Application Lifecycle Management, pinning down the needs, the trade-offs and the reasons to use, or not to use supporting tools
Agility and Compliance (Andrea Tomasini, agile42)Andrea Tomasini
Implementing agility in a strongly Regulated environment is sometimes a challenge. Many teams and company do find ways, but most of these are against the agile principles or are turning out to be big impediments. Mostly the problem being that from compliance authorities we get told HOW to do things and not WHAT they will measure to prove quality and compliance. Can we do better? Sure we can, transparency is the key...
Adopting Scrum: an enterprise transformation (Andrea Tomasini, agile42)Andrea Tomasini
Using Scrum as a Pattern Language for Enterprise Transformation
How Scrum Patterns can be used also to introduce Scrum itself into a company. After many years of experience and many attempts to systematically make Scrum introduction into medium and large Enterprises, agile42 shares with you tools and methods used in some of the most successful agile transition.
Why Scrum can\'t fail? A very challenging question that I have been asked to answer at the House of Open Scrum in Munich, a free and open event to propagate Scrum to the masses :-) That\'s my answer... I hope you enjoy it ;-)
Keynote stop scaling... start growing an agile organization!Andrea Tomasini
Companies of all sizes need to grow their own agile way of working, becoming more agile is a journey, not a destination. Unfortunately, though, most of the time agile success is left in the hands of unlikely heroes, people who are passionate about agile, but likely lack the type of power and decision making required to move to the next level. Because becoming agile requires a radical mind-shift, it takes time, and time is what most organizations seem unwilling to invest. This is where our unlikely heroes come into play, pulling the “Agile Initiative” forward with their passion. Even more unfortunately, despite the great efforts of these individuals, the organization is not willing to wait, and instead, falls into the “implement that model” in a couple of months mindset. Does this work? Well, if it does, we still need to hear that it was fast and painless… On the other hand, more and more organizations are beginning to understand that becoming more agile is an individual journey, and has to be tightly coupled with the company business goals and culture, it can’t be standardized, or the company will likely lose their business advantage and uniqueness. In this keynote I am going to share stories about some of these companies, that having tried unsuccessfully to find more heroes, understood that becoming agile is a cultural shift that needs to be supported by the whole organization, and agreed to follow a growing approach rather than an implementing approach. Principles and tools which helped these organizations to grow their agility as well as stories of their journey will be shared as an example of how change can happen without heroic actions or old style “Change Initiatives”.
How to grow your organization resilience and anti-fragilityAndrea Tomasini
Bringing agility to an organizational level requires a set of new skills and practices to emerge. While we have plenty of example on how agility can impact teams performance, by adopting well proven practices, there is still a lot of uncertainty in what to bring to an organizational level. Inspecting and adapting as an organization requires different structures and a more strategic approach, if we want to maximize the learning effect. Chaotic and uncontrolled experimentation and local adaptations can rapidly tear an organization apart. Focus on value and customers are important to set a common direction, but to roll out a shared strategy we need a solid and coherent cultural context, or the strategy will fail. Explicitly measuring and designing culture is a key enabler towards agility and can provide incredible advantages to an organization development. Understanding how to lead such change and enabling people to participate in creating rapid value, is the one thing that might save your company in the rough waters of today's market... Are you ready for the challenge?
The agile reading glasses: foundation principles and history being agile appr...Andrea Tomasini
A quick journey through the foundation of agile and the history behind it. Starting from the process control theory, moving forward through iterative and incremental approach, and the pull principle. Moving on to the continuous improvement focus, stemming from the Lean Thinking and the work done by the fore runners of the Toyota Production System (TPS). Finally discussing how agile thinking can help establishing self-organization and focus on customer value, motivating both the workers and the clients, by establishing healthier short-feedback cycle, with collaboration focused on learning faster together.
Agile Embedded Software Development, what's wrong with it?Andrea Tomasini
We are in 2014 and still someone is challenging the fact that you can't use an Agile approach to develop embedded systems, why? What's wrong with embedded software development? Well, there are somethings which makes it harder than needed: Dependencies with hardware releases, fixed delivery dates, inadequate software tools, limited adaptation possibility due to hardware costs... and yes, one more thing, really special: culture!
We would like to focus this keynote in analyzing some example cases that include the “limitations” listed above and also give you some hints on how to solve them. Finally we will also attack the “culture” issue. This is especially important for companies which grew out of hardware development and do not have a solid culture that include software, and therefore are stuck with waterfall development process and a traditional view on professional barriers for their employees. These companies are usually the ones not understanding that the complexity for years gone away from pure hardware, and landed in integrated product development. Without more focus in increasing quality of the process and the techniques to build - especially mission critical - functionality, the cost of failure are going to be very high, as the amount of bugs exposed to the users will rise and the competition sharpens at the same time.
Application Lifecycle Management and Agile, friends... or foes? (Andrea Toma...Andrea Tomasini
The whole idea of ALM stems from the need to manage in an integrated manner the relationship between business processes and engineering processes. Attempting to integrate practices, information and tools for disciplines such as Requirement Engineering, Project Management, Configuration Management has long been a driver, with the important goal of achieving more transparency, and also more control. Centralization of information into a single authoritative repository moved many original ALM initiatives, but how does that fit with more modern Agile approaches? Is it really possible to have Agile ALM? What would we keep of ALM and what of Agile? Are ALM and Agile friends... or foes? This keynote will offer an agile and pragmatic perspective to Application Lifecycle Management, pinning down the needs, the trade-offs and the reasons to use, or not to use supporting tools
Agility and Compliance (Andrea Tomasini, agile42)Andrea Tomasini
Implementing agility in a strongly Regulated environment is sometimes a challenge. Many teams and company do find ways, but most of these are against the agile principles or are turning out to be big impediments. Mostly the problem being that from compliance authorities we get told HOW to do things and not WHAT they will measure to prove quality and compliance. Can we do better? Sure we can, transparency is the key...
Adopting Scrum: an enterprise transformation (Andrea Tomasini, agile42)Andrea Tomasini
Using Scrum as a Pattern Language for Enterprise Transformation
How Scrum Patterns can be used also to introduce Scrum itself into a company. After many years of experience and many attempts to systematically make Scrum introduction into medium and large Enterprises, agile42 shares with you tools and methods used in some of the most successful agile transition.
Why Scrum can\'t fail? A very challenging question that I have been asked to answer at the House of Open Scrum in Munich, a free and open event to propagate Scrum to the masses :-) That\'s my answer... I hope you enjoy it ;-)
Keynote stop scaling... start growing an agile organization!Andrea Tomasini
Companies of all sizes need to grow their own agile way of working, becoming more agile is a journey, not a destination. Unfortunately, though, most of the time agile success is left in the hands of unlikely heroes, people who are passionate about agile, but likely lack the type of power and decision making required to move to the next level. Because becoming agile requires a radical mind-shift, it takes time, and time is what most organizations seem unwilling to invest. This is where our unlikely heroes come into play, pulling the “Agile Initiative” forward with their passion. Even more unfortunately, despite the great efforts of these individuals, the organization is not willing to wait, and instead, falls into the “implement that model” in a couple of months mindset. Does this work? Well, if it does, we still need to hear that it was fast and painless… On the other hand, more and more organizations are beginning to understand that becoming more agile is an individual journey, and has to be tightly coupled with the company business goals and culture, it can’t be standardized, or the company will likely lose their business advantage and uniqueness. In this keynote I am going to share stories about some of these companies, that having tried unsuccessfully to find more heroes, understood that becoming agile is a cultural shift that needs to be supported by the whole organization, and agreed to follow a growing approach rather than an implementing approach. Principles and tools which helped these organizations to grow their agility as well as stories of their journey will be shared as an example of how change can happen without heroic actions or old style “Change Initiatives”.
How to grow your organization resilience and anti-fragilityAndrea Tomasini
Bringing agility to an organizational level requires a set of new skills and practices to emerge. While we have plenty of example on how agility can impact teams performance, by adopting well proven practices, there is still a lot of uncertainty in what to bring to an organizational level. Inspecting and adapting as an organization requires different structures and a more strategic approach, if we want to maximize the learning effect. Chaotic and uncontrolled experimentation and local adaptations can rapidly tear an organization apart. Focus on value and customers are important to set a common direction, but to roll out a shared strategy we need a solid and coherent cultural context, or the strategy will fail. Explicitly measuring and designing culture is a key enabler towards agility and can provide incredible advantages to an organization development. Understanding how to lead such change and enabling people to participate in creating rapid value, is the one thing that might save your company in the rough waters of today's market... Are you ready for the challenge?
The agile reading glasses: foundation principles and history being agile appr...Andrea Tomasini
A quick journey through the foundation of agile and the history behind it. Starting from the process control theory, moving forward through iterative and incremental approach, and the pull principle. Moving on to the continuous improvement focus, stemming from the Lean Thinking and the work done by the fore runners of the Toyota Production System (TPS). Finally discussing how agile thinking can help establishing self-organization and focus on customer value, motivating both the workers and the clients, by establishing healthier short-feedback cycle, with collaboration focused on learning faster together.
Agile Embedded Software Development, what's wrong with it?Andrea Tomasini
We are in 2014 and still someone is challenging the fact that you can't use an Agile approach to develop embedded systems, why? What's wrong with embedded software development? Well, there are somethings which makes it harder than needed: Dependencies with hardware releases, fixed delivery dates, inadequate software tools, limited adaptation possibility due to hardware costs... and yes, one more thing, really special: culture!
We would like to focus this keynote in analyzing some example cases that include the “limitations” listed above and also give you some hints on how to solve them. Finally we will also attack the “culture” issue. This is especially important for companies which grew out of hardware development and do not have a solid culture that include software, and therefore are stuck with waterfall development process and a traditional view on professional barriers for their employees. These companies are usually the ones not understanding that the complexity for years gone away from pure hardware, and landed in integrated product development. Without more focus in increasing quality of the process and the techniques to build - especially mission critical - functionality, the cost of failure are going to be very high, as the amount of bugs exposed to the users will rise and the competition sharpens at the same time.
Why practices are not as important as principles?Andrea Tomasini
You might wonder why is not that easy to adopt agile engineering practices and achieve technical excellence. When we think at practices we tend to think at simple things: pinning on the fridge with a magnet the list of shopping items to buy, having a clear prioritised list of things to do, and work that in order… why is then that with Agile practices is not working that easy? What is that Teams are not getting right? Is it that we don’t have the right Software tools? Or we are not collocated? The Agile dilemma is: “To effectively apply practices, you need to understand the principle, to understand the principles you need to practice!”, simply… complicated!
Why self-organization might not work, and what has that to do with the compan...Andrea Tomasini
On the way toward becoming more agile, we often stumble on issues which are sometimes simple in hindsight, but when we are at it, they seem impossible challenges. We might start with an agile team, probably following the Scrum framework and having quite some fun while learning and delivering more value with our colleagues. At a certain point though the expected “hyper productivity” that some folks in the agile world are talking about doesn’t seem to be something achievable at all, and we comfortably think, that must be just marketing, or even the effect of the Chinese Whispers. But if we reflect ourselves on it, and have the courage to look deep and understand why things aren’t going the way they should, we often come to learn a lot. Question such as: “By the way, why do we still have Team Leader in a self-organizing team?” or “What is the role of a Tech Lead in a Scrum team?” up to “Why are we still estimating and planning upfront if we are doing agile development?” inevitably pop up. Is it a trust issue? is it a cultural problem? or is it an organizational design issue? Maybe the answer, as many times happen in complex situation is a mixture or neither of those.
Explore together with me what implications these dimensions have on the way teams will develop further or not develop. Also how do other companies around the world relate to this challenges, and maybe you can learn something from that…
Improve the chances of success of your organization with Resilience and Antif...Andrea Tomasini
Explicitly measuring and designing culture is an enabler towards agility and can provide incredible advantages to an organization development. Understanding how to lead such change is the one thing that might save your company in the rough waters of todays market. Are you ready for the challenge?
From a Product Vision to a running software... and back again, and agile coac...Andrea Tomasini
Eliciting Requirements and breaking them down into actionable tasks is a challenge that requires both creativity and a systematic and analytical approach. Applying agility to Requirement Engineering, means much more than focusing on full bandwidth communication instead of documentation... Discovering a more empirical approach to Requirement Engineering - an approach that allows you to focus systematically on what needs to be done, as well as allowing creative tension to emerge and find the simplest and more concrete solutions for your Requirements engineering
Herding cats, or the art of scaling agile teamsDave Sharrock
Managing the evolution of a single product working with a small number of teams is somewhat straightforward. Working from a single backlog, the product roadmap becomes relatively easy to visualize, and planning and tracking is simple. As we increase the complexity of the product, things become harder. Different teams require different backlogs. Different products require work from different teams. Before you know it, there are lots of independent moving parts, and coordination costs increase and dependencies dominate. In this talk, we consider core principles and practices for scaling in an agile world, and discuss how to move from a handful of teams to many teams and many product lines.
Estimate Value to Deliver Value: Effectively Estimate the Value of Requiremen...Dave Sharrock
Agile organizations move work to dedicated teams, rather than move people to projects. In order to succeed, the Business Analyst needs to continually compare the value of different projects or work requirements to make sure that the teams are working on the most valuable items at any one time. But how can you compare new features that increase your profitability with platform migrations that increase your system stability or administrative features that reduce operational overhead? Where do BAs spend their time and how do stakeholders get their critical projects done?
The Experience Canvas provides a one-page requirement definition that allows stakeholders to effectively discuss and estimate the value of each requirement.
Using the Experience Canvas, we show how:
Stakeholders can compare and contrast the value of very different requirements with very different objectives,
Business Analysts can estimate return-on-investment using effort estimates from the team (investment) and value estimates from the stakeholders (return).
Out of Sight, Out of Mind: Survival tricks and tools for remote developersAlessio Bragadini
Presented at PycCon 8, Florence 7 April 2017 – Remote working and “smart working” is very much in fashion these days, but what does it entail for the daily routing of a distributed development team? We will talk about tools, the disputed use of email, Skype, Slack but more specifically about time management, what you can expect from yourself and from other members of the remote team. Is your company “remote-friendly” or rather “remote-first”? When it’s time to spend a few days in physical proximity with your colleagues? We will share some examples out of the experience of a distributed team actively working with Python and Django on a daily basis, and show how you can make it all work, if you work on it.
Giving Teams the Roots to Grow and Wings to FlyDave Sharrock
We introduce useful and proven practices that increase the sticking power of new agile teams, allowing them to stay agile long into the future. To create sustainable change, agile teams have to overcome organizational gravity that pulls them back into the old, comfortable ways of working. New agile teams are especially at risk of falling back after the coaches leave or the agile transition is declared ‘over’. By helping the team set expectations early, the +15 practices provide support just when the team is most vulnerable, and increases the chance of creating lasting change.
We introduce two concepts, the +15 Team and the +15 Flightplan, that support teams not just at the beginning of a transformation, when management attention and resources are focused on the effort, but much later on as the teams begin unlocking some of the more challenging engineering practices, such as continuous integration or continual refactoring which take time and repeated practice to achieve. You will learn how to work with a new team to apply these concepts, and how the team can use these to guide growth over time.
Successful Agile transformations are built on successful Agile teams; achieving sustainable success depends on helping those teams grow and evolve over time. But in order to be self-organized and self-directed, newly formed agile teams need an example to follow; they need to have a glimpse of where a team can get to after 3, 6 or 12 months of continual retrospection, learning and improvement. Unfortunately, in many cases, there are few examples of such success around them. In a large organization, the inertia of existing cultural norms is likely to weigh down on any visions of excellent execution, diluting the vision and ultimately limiting the success of the teams and the transition.
The +15 Team is a simple exercise to focus the team on developing good agile behaviors that provide the roots from which a team can grow. The +15 Flightplan is a workshop or game that delivers a long-term plan for agile maturity created by the team that allows the team to soar over time. Participants will be introduced to this technique as a way to better guide the team’s development over time as well as learn how and when to respond. Spending just minutes at every retrospective using these artifacts can make the difference between a team returning to old habits and performance levels or striding forward to become self-directed, high-performing agile teams.
What the presentation is not about:
- Explaining why self-organized teams
- Explaining what a self-organized team is
- Explaining what a team is
- Explaining the boundaries and conditions to make self-organization to happen
What the presentation is about:
- Show an structured way of supporting self-organization throw my personal experience.
For a long time, organizations were seen more as machines in which processes are repeatable and, once set in motion, remain always the same. At agile42 we instead compare a company to an organism which grows, changes, and becomes resilient against external influences.
An organisation’s Agile transformation changes the organizational culture itself. This requires embracing a different set of values and principles, and so establishing a mindset strongly focused on collaboration and delivering customer value.
ORGANIC Agility recognises all organisational dimensions and contexts in order to create alignment between culture and business. The goal is to reduce process overhead as much as possible and create an environment of continuous improvement.
Despite the Agile manifesto commitment to Individuals and interactions over processes and tools the reality too often degenerates into certification schemes focused on structured methods or even worse it degrades into tool implementation. Approaches assume a manufacturing model (the engineering metaphor) rather than a network of relationships between individuals (the biological metaphor). Requirements are fragmented, the bigger picture and wider opportunities are lost. Excessive focus on predetermined goals and KPIs fails to support continuous learning and adaptation through experimentation. In this presentation we will look at the next generation of organizational agility, creating real-time feedback loops, adaptive processes and fostering innovation - working out what is a minimal scaffolding or structure around which new and innovative applications can emerge.
Stop scaling... Start growing an Agile Organization!Andrea Tomasini
Strategic advantage lies in being yourself and doing the right things the right way. Those who copy what their competitors are doing, place themselves behind the pack — a sure way of losing. This is why “scaling” agility is misleading at best, and disastrous at worst. When you take an existing model and fit your organization to that, you lose much of what makes you unique and different.
Companies small and large must instead learn to grow their own agility for their own advantage. This sounds simple — and it is, when you know what to look for.
In this keynote, Andrea Tomasini presents guidelines and heuristics for growing an agile organization. You will understand why the first step in any transition must be learning how to change. Small inexpensive experiments and empirical metrics will lead you towards your strategic goal, iteratively and incrementally.
The agile transition never ends — but you know it’s working when transitioning becomes a way of life. This not only lets you adapt to new market conditions: it also allows you to create change in the market, on your own terms.
The complexity of scaling agile in a large organization
Fundamental principles on “growing”
Concrete examples (Siemens, Ericsson…) from companies of all sizes (60-6000 employees)
The principles are simple, but they must apply to the organization, not the product or the system architecture.
The heartbeat of a growing organization.
How shifting thinking about an organisation as a biological, natural systems, opens significant options about how to design a better organisation. Using Nassim Taleb Antifragility concept, combined with the Cynefin Framework from Dave Snowden, it is possible to identify principles which will allow to design a better and more Resilient, possibly Antifragile organisation. In this presentation I am sharing the 6 Design Principles for an agile organisation that are at the core of the agile42 Enterprise Transition Framework (ETF). There are concrete examples from some of the companies that allowed us to share pictures.
Agile teams form the building blocks for agility. Having strong agile teams allows an organization to overcome systemic issues and adapt the product development process to the needs of the business. Agile teams that are not self-organizing and continually learning can quickly become subsumed by the challenges around them. So what does it mean for a team to be agile? We look at the fundamental characteristics of high performing teams, and how to influence the team environment and selection in order to initiate a team for success.
The rise of the Lean Startup has led to a deeper understanding of the importance of validating business ideas, from new features to new business models. But many tools available to the Product Owner aren't adapted to rapid validation. Starting from the principles and practices of agile product management, from defining the product vision to creating story maps and refining the product backlog, you will learn about key practices that incorporate the lean startup principles, allowing a Product Owner to bring the build-measure-learn cycle alive and ultimately earn more value more quickly.
Out of the success of some pilot (experiments) more and more organizations are stumbling on how to scale those experiments throughout the rest of the company. What most organizations end up doing is to reuse over and over again the same structures and the same rules they have been using for years, missing entirely the point about Agile. If you want to make it work for your organization, start from looking within a Team and understand what makes them Agile... look deeper into principles and values, not so much in practices, as those will emerge out of experience from your teams. Also understand the major difference between becoming agile and adopting agile. The latter encourage the wrong behaviour of looking on the market at existing models to adopt, and roll-out within your organization. Look at those model as a confirmation that is possible to solve your problems - as someone else apparently already did - and as inspiration. Also be vary of models which are not stemming out of experience, but of a lot of thinking, as that doesn't fit well to the Agile and Lean paradigm. Finally there are many factor you can evaluate in your journey toward becoming more Agile, there are level of complexity growing at an organizational level which you might not find in teams. Finally look at identifying metrics for tracking your progress in a way that reflects the outcome your organization is delivering and not the "work" is doing. In fact learning to work in an Agile way means learning to deliver more, by doing less. In the presentation I use the metaphor of an organization being a "car" rather than an organism, because of pure esthetic reasons, it would get rather bloody with an organic metaphor. I am aware like all models, has its weaknesses, and one of those is that it is mechanic, and predictable, unless it is a transforming car :-)
Epic Budgeting - how agile teams meet deadinesDave Sharrock
According to this year's State of Agile survey, the most common success measure for agile initiatives, at 53%, is on-time delivery. But if agile teams can choose how much work they take into a sprint, how can teams be sure of delivering pre-committed scope on time and on budget? There is more to agile delivery than product owners ordering a backlog of work for teams to work on.
Epic budgeting is one tool that allows the product owner to steer a product across the line, delivering the expected scope on time by managing scope creep or an unsustainable focus on the perfect over the pragmatic. During this session learn about how product owners and their teams work towards a fixed date or budget by applying double loop learning to epic sizing and breakdown. Expect some tales from real companies and a few light hearted moments. And I'm at least 53% certain we will finish on time!
We all know the engineering practices we should be using, and many teams I meet say that they have plans to start unit testing or test automation, ‘in the next 6 months’. But for a variety of reasons familiar to all of us, like time pressure and ever increasing demands from the customer, these worthy plans rarely come to pass. Using experiences from starting agile teams, I’ll throw out some proven strategies for getting a toe hold in adopting great agile practices, as well as looking at real examples from the audience and how we might accelerate the adoption of good practices.
Valtech - Connecting Product Vision to Everyday Agile WorkValtech
Connecting Product Vision to Everyday Agile Work.
Kelly R. Looney, Principal Process Engineer, Valtech US
Kelly.Looney@valtech.com
Agile Day 2012
Valtech
Why practices are not as important as principles?Andrea Tomasini
You might wonder why is not that easy to adopt agile engineering practices and achieve technical excellence. When we think at practices we tend to think at simple things: pinning on the fridge with a magnet the list of shopping items to buy, having a clear prioritised list of things to do, and work that in order… why is then that with Agile practices is not working that easy? What is that Teams are not getting right? Is it that we don’t have the right Software tools? Or we are not collocated? The Agile dilemma is: “To effectively apply practices, you need to understand the principle, to understand the principles you need to practice!”, simply… complicated!
Why self-organization might not work, and what has that to do with the compan...Andrea Tomasini
On the way toward becoming more agile, we often stumble on issues which are sometimes simple in hindsight, but when we are at it, they seem impossible challenges. We might start with an agile team, probably following the Scrum framework and having quite some fun while learning and delivering more value with our colleagues. At a certain point though the expected “hyper productivity” that some folks in the agile world are talking about doesn’t seem to be something achievable at all, and we comfortably think, that must be just marketing, or even the effect of the Chinese Whispers. But if we reflect ourselves on it, and have the courage to look deep and understand why things aren’t going the way they should, we often come to learn a lot. Question such as: “By the way, why do we still have Team Leader in a self-organizing team?” or “What is the role of a Tech Lead in a Scrum team?” up to “Why are we still estimating and planning upfront if we are doing agile development?” inevitably pop up. Is it a trust issue? is it a cultural problem? or is it an organizational design issue? Maybe the answer, as many times happen in complex situation is a mixture or neither of those.
Explore together with me what implications these dimensions have on the way teams will develop further or not develop. Also how do other companies around the world relate to this challenges, and maybe you can learn something from that…
Improve the chances of success of your organization with Resilience and Antif...Andrea Tomasini
Explicitly measuring and designing culture is an enabler towards agility and can provide incredible advantages to an organization development. Understanding how to lead such change is the one thing that might save your company in the rough waters of todays market. Are you ready for the challenge?
From a Product Vision to a running software... and back again, and agile coac...Andrea Tomasini
Eliciting Requirements and breaking them down into actionable tasks is a challenge that requires both creativity and a systematic and analytical approach. Applying agility to Requirement Engineering, means much more than focusing on full bandwidth communication instead of documentation... Discovering a more empirical approach to Requirement Engineering - an approach that allows you to focus systematically on what needs to be done, as well as allowing creative tension to emerge and find the simplest and more concrete solutions for your Requirements engineering
Herding cats, or the art of scaling agile teamsDave Sharrock
Managing the evolution of a single product working with a small number of teams is somewhat straightforward. Working from a single backlog, the product roadmap becomes relatively easy to visualize, and planning and tracking is simple. As we increase the complexity of the product, things become harder. Different teams require different backlogs. Different products require work from different teams. Before you know it, there are lots of independent moving parts, and coordination costs increase and dependencies dominate. In this talk, we consider core principles and practices for scaling in an agile world, and discuss how to move from a handful of teams to many teams and many product lines.
Estimate Value to Deliver Value: Effectively Estimate the Value of Requiremen...Dave Sharrock
Agile organizations move work to dedicated teams, rather than move people to projects. In order to succeed, the Business Analyst needs to continually compare the value of different projects or work requirements to make sure that the teams are working on the most valuable items at any one time. But how can you compare new features that increase your profitability with platform migrations that increase your system stability or administrative features that reduce operational overhead? Where do BAs spend their time and how do stakeholders get their critical projects done?
The Experience Canvas provides a one-page requirement definition that allows stakeholders to effectively discuss and estimate the value of each requirement.
Using the Experience Canvas, we show how:
Stakeholders can compare and contrast the value of very different requirements with very different objectives,
Business Analysts can estimate return-on-investment using effort estimates from the team (investment) and value estimates from the stakeholders (return).
Out of Sight, Out of Mind: Survival tricks and tools for remote developersAlessio Bragadini
Presented at PycCon 8, Florence 7 April 2017 – Remote working and “smart working” is very much in fashion these days, but what does it entail for the daily routing of a distributed development team? We will talk about tools, the disputed use of email, Skype, Slack but more specifically about time management, what you can expect from yourself and from other members of the remote team. Is your company “remote-friendly” or rather “remote-first”? When it’s time to spend a few days in physical proximity with your colleagues? We will share some examples out of the experience of a distributed team actively working with Python and Django on a daily basis, and show how you can make it all work, if you work on it.
Giving Teams the Roots to Grow and Wings to FlyDave Sharrock
We introduce useful and proven practices that increase the sticking power of new agile teams, allowing them to stay agile long into the future. To create sustainable change, agile teams have to overcome organizational gravity that pulls them back into the old, comfortable ways of working. New agile teams are especially at risk of falling back after the coaches leave or the agile transition is declared ‘over’. By helping the team set expectations early, the +15 practices provide support just when the team is most vulnerable, and increases the chance of creating lasting change.
We introduce two concepts, the +15 Team and the +15 Flightplan, that support teams not just at the beginning of a transformation, when management attention and resources are focused on the effort, but much later on as the teams begin unlocking some of the more challenging engineering practices, such as continuous integration or continual refactoring which take time and repeated practice to achieve. You will learn how to work with a new team to apply these concepts, and how the team can use these to guide growth over time.
Successful Agile transformations are built on successful Agile teams; achieving sustainable success depends on helping those teams grow and evolve over time. But in order to be self-organized and self-directed, newly formed agile teams need an example to follow; they need to have a glimpse of where a team can get to after 3, 6 or 12 months of continual retrospection, learning and improvement. Unfortunately, in many cases, there are few examples of such success around them. In a large organization, the inertia of existing cultural norms is likely to weigh down on any visions of excellent execution, diluting the vision and ultimately limiting the success of the teams and the transition.
The +15 Team is a simple exercise to focus the team on developing good agile behaviors that provide the roots from which a team can grow. The +15 Flightplan is a workshop or game that delivers a long-term plan for agile maturity created by the team that allows the team to soar over time. Participants will be introduced to this technique as a way to better guide the team’s development over time as well as learn how and when to respond. Spending just minutes at every retrospective using these artifacts can make the difference between a team returning to old habits and performance levels or striding forward to become self-directed, high-performing agile teams.
What the presentation is not about:
- Explaining why self-organized teams
- Explaining what a self-organized team is
- Explaining what a team is
- Explaining the boundaries and conditions to make self-organization to happen
What the presentation is about:
- Show an structured way of supporting self-organization throw my personal experience.
For a long time, organizations were seen more as machines in which processes are repeatable and, once set in motion, remain always the same. At agile42 we instead compare a company to an organism which grows, changes, and becomes resilient against external influences.
An organisation’s Agile transformation changes the organizational culture itself. This requires embracing a different set of values and principles, and so establishing a mindset strongly focused on collaboration and delivering customer value.
ORGANIC Agility recognises all organisational dimensions and contexts in order to create alignment between culture and business. The goal is to reduce process overhead as much as possible and create an environment of continuous improvement.
Despite the Agile manifesto commitment to Individuals and interactions over processes and tools the reality too often degenerates into certification schemes focused on structured methods or even worse it degrades into tool implementation. Approaches assume a manufacturing model (the engineering metaphor) rather than a network of relationships between individuals (the biological metaphor). Requirements are fragmented, the bigger picture and wider opportunities are lost. Excessive focus on predetermined goals and KPIs fails to support continuous learning and adaptation through experimentation. In this presentation we will look at the next generation of organizational agility, creating real-time feedback loops, adaptive processes and fostering innovation - working out what is a minimal scaffolding or structure around which new and innovative applications can emerge.
Stop scaling... Start growing an Agile Organization!Andrea Tomasini
Strategic advantage lies in being yourself and doing the right things the right way. Those who copy what their competitors are doing, place themselves behind the pack — a sure way of losing. This is why “scaling” agility is misleading at best, and disastrous at worst. When you take an existing model and fit your organization to that, you lose much of what makes you unique and different.
Companies small and large must instead learn to grow their own agility for their own advantage. This sounds simple — and it is, when you know what to look for.
In this keynote, Andrea Tomasini presents guidelines and heuristics for growing an agile organization. You will understand why the first step in any transition must be learning how to change. Small inexpensive experiments and empirical metrics will lead you towards your strategic goal, iteratively and incrementally.
The agile transition never ends — but you know it’s working when transitioning becomes a way of life. This not only lets you adapt to new market conditions: it also allows you to create change in the market, on your own terms.
The complexity of scaling agile in a large organization
Fundamental principles on “growing”
Concrete examples (Siemens, Ericsson…) from companies of all sizes (60-6000 employees)
The principles are simple, but they must apply to the organization, not the product or the system architecture.
The heartbeat of a growing organization.
How shifting thinking about an organisation as a biological, natural systems, opens significant options about how to design a better organisation. Using Nassim Taleb Antifragility concept, combined with the Cynefin Framework from Dave Snowden, it is possible to identify principles which will allow to design a better and more Resilient, possibly Antifragile organisation. In this presentation I am sharing the 6 Design Principles for an agile organisation that are at the core of the agile42 Enterprise Transition Framework (ETF). There are concrete examples from some of the companies that allowed us to share pictures.
Agile teams form the building blocks for agility. Having strong agile teams allows an organization to overcome systemic issues and adapt the product development process to the needs of the business. Agile teams that are not self-organizing and continually learning can quickly become subsumed by the challenges around them. So what does it mean for a team to be agile? We look at the fundamental characteristics of high performing teams, and how to influence the team environment and selection in order to initiate a team for success.
The rise of the Lean Startup has led to a deeper understanding of the importance of validating business ideas, from new features to new business models. But many tools available to the Product Owner aren't adapted to rapid validation. Starting from the principles and practices of agile product management, from defining the product vision to creating story maps and refining the product backlog, you will learn about key practices that incorporate the lean startup principles, allowing a Product Owner to bring the build-measure-learn cycle alive and ultimately earn more value more quickly.
Out of the success of some pilot (experiments) more and more organizations are stumbling on how to scale those experiments throughout the rest of the company. What most organizations end up doing is to reuse over and over again the same structures and the same rules they have been using for years, missing entirely the point about Agile. If you want to make it work for your organization, start from looking within a Team and understand what makes them Agile... look deeper into principles and values, not so much in practices, as those will emerge out of experience from your teams. Also understand the major difference between becoming agile and adopting agile. The latter encourage the wrong behaviour of looking on the market at existing models to adopt, and roll-out within your organization. Look at those model as a confirmation that is possible to solve your problems - as someone else apparently already did - and as inspiration. Also be vary of models which are not stemming out of experience, but of a lot of thinking, as that doesn't fit well to the Agile and Lean paradigm. Finally there are many factor you can evaluate in your journey toward becoming more Agile, there are level of complexity growing at an organizational level which you might not find in teams. Finally look at identifying metrics for tracking your progress in a way that reflects the outcome your organization is delivering and not the "work" is doing. In fact learning to work in an Agile way means learning to deliver more, by doing less. In the presentation I use the metaphor of an organization being a "car" rather than an organism, because of pure esthetic reasons, it would get rather bloody with an organic metaphor. I am aware like all models, has its weaknesses, and one of those is that it is mechanic, and predictable, unless it is a transforming car :-)
Epic Budgeting - how agile teams meet deadinesDave Sharrock
According to this year's State of Agile survey, the most common success measure for agile initiatives, at 53%, is on-time delivery. But if agile teams can choose how much work they take into a sprint, how can teams be sure of delivering pre-committed scope on time and on budget? There is more to agile delivery than product owners ordering a backlog of work for teams to work on.
Epic budgeting is one tool that allows the product owner to steer a product across the line, delivering the expected scope on time by managing scope creep or an unsustainable focus on the perfect over the pragmatic. During this session learn about how product owners and their teams work towards a fixed date or budget by applying double loop learning to epic sizing and breakdown. Expect some tales from real companies and a few light hearted moments. And I'm at least 53% certain we will finish on time!
We all know the engineering practices we should be using, and many teams I meet say that they have plans to start unit testing or test automation, ‘in the next 6 months’. But for a variety of reasons familiar to all of us, like time pressure and ever increasing demands from the customer, these worthy plans rarely come to pass. Using experiences from starting agile teams, I’ll throw out some proven strategies for getting a toe hold in adopting great agile practices, as well as looking at real examples from the audience and how we might accelerate the adoption of good practices.
Valtech - Connecting Product Vision to Everyday Agile WorkValtech
Connecting Product Vision to Everyday Agile Work.
Kelly R. Looney, Principal Process Engineer, Valtech US
Kelly.Looney@valtech.com
Agile Day 2012
Valtech
K8 2014 - Product Vision and Client Success Kenshoo
Presentation from Kenshoo CRO, Ted Krantz, SVP of Product, Will Martin-Gill, and MD of Client Excellence, Susane Berger, shared at Kenshoo's K8 Summit on September 16th, 2014.
"SCRUM allows us to create better products, more suited to the users' needs. ...Anna Zarudzka
General approach and widely available knowledge make us think that Scrum allows us to create better products. We can make better ones than while using Waterfall approach. It's hard to argue with that.
The question is: Does the iterativeness itself guarantee products that are better for the users?
Is a good Scrum team, presence of the Product Owner and more intense contact with stakeholders enough to form a theoretically better path for the product?
Do we remember about Product Vision? Do we emphasise it enough?
Product Vision is not something additional, it’s not only one high-level sentence of one person. It’s the package of crucial knowledge and THE TOOL OF COMMUNICATION: Target User, Values, Competitors and more.
Mike acaba de completar un entrenamiento de Scrum y siente que ha entendido las bases de Scrum así que está convencido que será beneficioso aplicarlo en su próximo proyecto.
Semanas más tarde, le dan luz verde al proyecto y Mike, entusiasmado, convoca a la primer Sprint Planning. Dado que ha pasado un poco de tiempo desde que revisó por última vez los conceptos de Scrum, Mike revisas sus apuntes, y recuerda que tiene que tener un Product Backlog granulado, una visión compartida, un roadmap, etc.
Mike entra en pánico, puesto que no tiene estas cosas listas, y siente que le ha faltado hacer cosas antes del sprint 1.
La presente charla será una explicación para Mike, de qué cosas podría hacer (un workflow y unas prácticas) antes del primer sprint para iniciarlo de la mejor forma.
Agile Testing is nonsense, because Agile is about testing!Andrea Tomasini
Testing is an attitude which brings us to trust results based on the fact that we can validate them. Testing is an approach which allows us to think about how to verify we did the right thing even before starting. Testing is a practice which allows us to write effective tests that can be repeated indefinitely while systematically producing consistent results.
Agile is built around the idea of managing complex projects, recognizing the importance of emerging results and verifying in a very disciplined way the assumptions and hypothesis we make as often and as thoroughly as possible. This means testing everything we do, every day ... So if you are truly Agile, you are living testing in every second of your life!
From an Idea to a Vision you can implement - Vision workshopVasco Duarte
You've been there. You are tasked with implementing a product that someone else cooked up. What do do next? Follow the spec you say? Wrong!
Developing a product without this Vision is not just waste, it is bad business for you and for your customer.
Before we start implementing any product we must explore it's reason to exist, what customers it benefits and ultimately how it can help your customers (not you!) make money.
In this workshop we will take an example and go through a simple process that helps us explore a product idea to the point that a spec is just a reference, but the product comes alive in the minds of the team members.
[Trung Hoang] Creating a compelling product visionTrung Hoang Nhac
How well are you communicating your product strategy?
How to create a product vision that motivates and aligns people, acts as the product's true north, and facilities collaboration?
How to form agile teams talks about the fundamental characteristics of high performing teams, and how to influence the team environment and selection in order to initiate a team for success.
IBM Innovate2014 - Is Agile Compliance an Oxymoron? Dave Sharrock
Agile software development is a light framework that focusses more on early value delivery and incremental improvement than traditional tasks like detailed up-front planning, comprehensive specifications and technical documentation. But from the perspective of regulatory compliance, this planning and documentation serve a purpose. How can we reconcile agile approaches that value a working product over documentation with the need to meet regulatory requirements for, e.g. medical devices or telecommunications? I will discuss how to bring together the apparently conflicting needs of regulatory compliance and agile, and show by example how agile teams actually approach tough regulatory requirements in finance, healthcare and telecommunications.
Learning Objectives
- How to use agile in a highly-regulated environment
- How to incorporate strict regulatory requirements within an agile development approach
- The power of agile as a risk-limiting software development approach
Breakfast for agile champions workshop-sgsea2011Dave Sharrock
Breakfast - the most important meal of the day. Certainly, if you miss breakfast around mid-morning you can find yourself lacking the energy and motivation to keep on working; Missing out on a good breakfast can doom you to an ineffectual and frustrating day. The kick-off of a major transition has a similar impact on the success of the transition.
But how can we increase the chance of success on a large transition? What is a “good breakfast” when starting a large transition? What should be avoided? Drawing from our own experience of many successful transitions, and learning from the experiences of you, the audience, we will learn what works - and what does not work - when kicking-off large transitions
Thoughts on Lean Product Development at CAMUG, YYC Nov 2014Dave Sharrock
The rise of the Lean Startup has led to a deeper understanding of the importance of validating business ideas, from new features to new business models. But many tools available to the Product Owner aren't adapted to rapid validation. Starting from the principles and practices of agile product management, from defining the product vision to creating story maps and refining the product backlog, you will learn about key practices that incorporate the lean startup principles, allowing a Product Owner to bring the build-measure-learn cycle alive and ultimately earn more value more quickly.
How can we reconcile the light touch approach of agile development teams to the governance and information security requirements such as Data Privacy and Regulatory Compliance? I discuss how to bring together the apparently conflicting needs of information security and agile, and show by example how agile teams actually approach tough regulatory requirements and good governance.
big bang delivery to continual value deliveryDave Sharrock
Recent years has seen an emerging new standard in software delivery, with Gartner claiming that over 80% of software development uses some form of agile methodology. Starting by understanding the mega-trends underlying this shift, from the commoditization of software changes, to the proliferation of development frameworks, to the increasing influence the customers of software have on the development lifecycle, we’ll consider the fundamental differences between a long big bang delivery lifecycle and a short incremental value delivery lifecycle, and its impact on information systems, security and controls.
Leading Agile Change - AgileVancouver 2011Dave Sharrock
An often overlooked aspect of large agile transformations is how we lead that transformation. The elephant in the room, if you like, is that many coaches and transition consultants focus on helping teams become more agile, while not walking the walk themselves. It is extremely difficult to rely on many frameworks like Scrum or Kanban for managing the work of the transition team or leadership team in a large organization. We talk the talk with our teams, but don’t walk the walk.
For more than 25 years the Support HR solutions Group has been supporting companies and professionals in the realisation and development of their potential, offering a wide range of customized consulting services in the field of Human Resources.
In our Milan, Rome and Bergamo offices we have more than 60 specialists operating in 5 strategic Business Units, created with the aim of providing integrated and dedicated solutions: Search & Selection, Advertising & Communications, Student Communications, HR Consulting, HR Finance.
Support is able to identify the best way to satisfy clients’ and candidates’ needs through a methodology in which in-depth competencies in HR are highly valued via a results-oriented and innovative approach.
www.supporthr.com
Similar to How to get everything right... by doing everything wrong? (Andrea Tomasini, agile42) (20)
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
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.
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.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
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.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
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
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
Le nuove frontiere dell'AI nell'RPA con UiPath Autopilot™UiPathCommunity
In questo evento online gratuito, organizzato dalla Community Italiana di UiPath, potrai esplorare le nuove funzionalità di Autopilot, il tool che integra l'Intelligenza Artificiale nei processi di sviluppo e utilizzo delle Automazioni.
📕 Vedremo insieme alcuni esempi dell'utilizzo di Autopilot in diversi tool della Suite UiPath:
Autopilot per Studio Web
Autopilot per Studio
Autopilot per Apps
Clipboard AI
GenAI applicata alla Document Understanding
👨🏫👨💻 Speakers:
Stefano Negro, UiPath MVPx3, RPA Tech Lead @ BSP Consultant
Flavio Martinelli, UiPath MVP 2023, Technical Account Manager @UiPath
Andrei Tasca, RPA Solutions Team Lead @NTT Data
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...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.
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.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
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.