Presenter:
Dr. Gail Ferreira, Agile Practice Leader, MATRIX Resources, San Francisco Center of Excellence
Rapid scale directly impacts all levels of decision-making, planning, execution, culture, and communications for executives in hypergrowth companies. In this session, we will discuss how to organize, support, and tailor agile practices for teams and sub-teams in companies with a rapid growth cycle. We will share contemporary case studies of hypergrowth companies who have delivered agile at scale.
Topics will include:
• Basic agile and lean methods
• Scrum of Scrums
• SAFe
• Disciplined Agile Delivery (DAD)
• Agility at Scale (Ambler/Lines)
• Spotify model (Tribes, Squads, Chapters & Guilds, DSDM).
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
Exploring Agile Transformation and Scaling Patterns
The goal of any enterprise agile adoption strategy is NOT to adopt agile. Companies adopt agile to achieve better business outcomes. Large organizations have no time for dogma and one-size-fits-all thinking when it comes to introducing agile practices. These companies need pragmatic guidance for safely and incrementally introducing structure, principles, and ultimately practices that will result in greater long term, sustainable business results. This talk will introduce a framework for safely, pragmatically, and incrementally introducing agile to help you achieve your business goals.
This document discusses transforming organizations to agile practices. It begins by outlining common goals for going agile such as predictability, quality, and innovation. It then discusses considerations for transformation based on organization size and dependencies. The key aspects for transformation are identified as backlogs, teams, and working tested software. Governance structures, metrics, and teaming strategies are also discussed. Transformation is framed as a journey, and quadrants are used to illustrate where organizations are currently and where they aim to go.
Leading a large-scale agile transformation isn’t about adopting a new set of attitudes, processes, and behaviors at the team level… it’s about helping your company deliver faster to market, and developing the ability to respond to a rapidly-changing competitive landscape. First and foremost, it’s about achieving business agility. Business agility comes from people having clarity of purpose, a willingness to be held accountable, and the ability to achieve measurable outcomes. Unfortunately, almost everything in modern organizations gets in the way of teams acting with any sort of autonomy. In most companies, achieving business agility requires significant organizational change.
Agile transformation necessitates a fundamental rethinking of how your company organizes for delivery, how it delivers value to its customers, and how it plans and measures outcomes. Agile transformation is about building enabling structures, aligning the flow of work, and measuring for outcomes based progress. It's about breaking dependencies. The reality is that this kind of change can only be led from the top. This talk will explore how executives can define an idealized end-state for the transformation, build a fiscally responsible iterative and incremental plan to realize that end-state, as well as techniques for tracking progress and managing change.
Why transform to Agile? What are the impediments to Agile Transformation? How to plan the Agile transformation? How to accelerate and sustain the Agile Transformation.
Agile Transformation is a consulting firm that specializes in organizational transformation using Agile, Lean, and other methods. They help clients transform their processes, teams, and culture to improve performance. Their services include assessing needs, developing custom roadmaps, coaching teams in Agile practices, and training leaders in skills like servant leadership and collaboration. Clients praise how Agile Transformation helped them successfully transform their culture, empower teams, and bridge gaps between departments.
Presented by Mr Lee Chee Yong, Agile Practice Lead of NCS Agile Competency Centre at ISS Seminar - Agile Software Development: Swift and the Shift on 18 July 2014.
Scaled agile framework (SAFe) - adopting agile at enterprise scale
The Scaled Agile Framework (SAFe) is an agile framework for enterprise-scale organizations. It addresses challenges of architecture, integration, funding, and roles at scale. SAFe has three levels - portfolio, program, and team. At the portfolio level, investment themes drive budget allocations. The program level uses Agile Release Trains of 5-10 teams to deliver value in 10 week iterations. Teams use Scrum or Kanban with 2 week iterations. SAFe aims to apply lean-agile principles at an enterprise scale.
Agile Eastern Europe 2011 Large Scale Agile Transformation
The document describes a large scale agile transformation at a global retailer. It discusses why the transformation was undertaken due to issues like long development times and quality problems. It then details how the transformation was implemented over several phases, including piloting agile practices, establishing agile roles and processes, and ongoing improvements. The transformation was considered successful, leading to benefits like reduced time to market, increased innovation, and becoming an employer of choice. The lesson learned is that organizations should understand their reasons for transforming before embarking on the journey.
Rick Austin - Portfolio mangement in an agile world [Agile DC]
When organizations move to agile for software delivery, there is often tension with traditional portfolio management. This talk will illustrate how an organization can move from traditional portfolio management approaches to one that embraces agile software delivery. Doing so enables organizations to become predictable, improve the flow of value delivered, and pivot more quickly if necessary.
We will demonstrate the use of governance that allows a more adaptive portfolio management approach. We will cover topics that enable agile portfolio management including:
Lean techniques for managing flow
Effective prioritization techniques
Long range road-mapping
Demand management and planning
Progressively elaborated business cases
Validation of outcomes
Support for audit and compliance needs
These topics will be illustrated by real-world examples of portfolio management that have been proven over the last five years with a wide range of clients.
Presentation to OU Agile special interest group 25 January 2017. Agile basics, Agile myths, and stories of breakthroughs and breakdowns in Agile adoption in learning design and course production.
This document discusses the agile mindset and contrasts it with the traditional waterfall mindset. It defines mindset as a person's way of thinking and opinions. The agile mindset values individuals and interactions, customer collaboration, responding to change, and valuing working software over documentation. It also discusses agile principles, practices like Scrum and Kanban, and the differences between doing agile and having an agile mindset. The document contrasts fixed and growth mindsets and provides indicators of an agile mindset at both the team and organizational levels. It also discusses common agile pitfalls and provides resources for further reading.
The document provides an introduction to agile methods for executives. It discusses how agile approaches can help organizations adapt to increasingly volatile business environments. The key benefits of agile include shorter time to market, increased productivity, improved alignment with business needs, and greater predictability. The document outlines agile concepts like iterative development, minimal viable products, continuous delivery and focus on customer value. It also summarizes common agile frameworks like Scrum and how agility can be scaled in large organizations.
Scaled Agile Framework in 10 minutes (SAFe 3.0)
- Scaled: SAFe is designed for large-scale software development ecosystems of 50-125 people who need to resolve inter-dependencies
- Agile: SAFe is based on 9 Lean-Agile principles
- Framework: SAFe is a collection of a proven efficacy tools, and you only have to use what you need
https://www.youtube.com/watch?v=vysQQx7pQzg
El objetivo de la Lightning Talk es dar una visión "light" pero completa de lo que propone Scaled Agile Framework 3.0 como marco de referencia para el escalado de Agile.
Scaled Agile Framework es uno de los marcos de referencia para escalado de Agile que mayor aceptación está teniendo a día de hoy, sobre todo cuando hablamos de grandes organizaciones. El marco SAFe parte de las capas de abstracción clásicas de una organización para estructurar un cambio de perspectiva y de cultura basándose en los 4 valores y 9 principios Lean-Agile, apoyándose además en las prácticas Scrum-XP de desarrollo de productos. En la charla descubriremos de manera rápida los roles, artefactos y ceremonias que plantea el marco para conseguir un cambio de paradigma sostenible en las organizaciones.
Unai Roldán
UST Global
This document provides an overview of agile methodology for software development. It discusses how agile practices arose in response to the limitations of traditional waterfall approaches. The core principles of agile include valuing individuals and interactions, working software, customer collaboration, and responding to change. Agile methods embrace changing requirements, frequent delivery of working software, collaboration between business and technical teams, self-organizing teams, and continuous improvement.
To compete in today’s application economy, organizations have adopted agile execution techniques. But is that enough? Learn about SAFe and how to leverage this methodology to elevate your agile teams to deliver quality outcomes and align at the enterprise level.
For more information, please visit http://cainc.to/Nv2VOe
Management is dead, at least traditional management is. No need to tell you what’s wrong with traditional management, you’ve probably experienced it yourself. And the results are outrageous, be it at company level, team level, and individual level; downright from project failures to complete demotivation of the staff.
Managers need to evolve, or they simply won’t survive if they don’t bring solutions to the above problems. From traditional management to … Agile management and leadership. You, as an experienced manager or as a wannabe/junior manager, are in a key position to change this.
By attending this 60-minutes talk, you’ll (re-)discover proven and actionable techniques to improve your management skills, foster team productivity, and keep morale and motivation atop. Yes, success is that close ;-)
On October 13, 2016, Tom Haak of the HR Trend Institute gave a keynote at "HR on the Move 2016", organised by AOG School of Management. This is the pack of slides he used.
The agile manifesto introduced a new way of implementing software development projects which resulted in a dramatic improvement in these types of projects. Agile success at the project level has prompted IT leaders within organization to try to scale it to the enterprise level with less success rate. In this interactive session, we will review the various approaches to large-scale agile transformation, discuss the transformation road map and organizational change management required as well as key drivers/sponsors required for a successful agile transformation. We will discuss how to measure transformation progress, and outline possible challenges and corresponding solutions.
The PPT is about scaling agile across various non-cross-functional teams and the various experiments that were done before arriving at a methodology that worked for the teams.
AgileLIVE: Scaling Agile to the Program & Portfolio Levels - Part 1
Are you ready to maximize the impact of delivering in an agile framework across your organization, yet challenged by scaling agile beyond the team level to the program and portfolio levels? Transforming a larger organization to agile requires deliberate change and coordination. While there are frameworks developing, such as the Scaled Agile Framework® (SAFe™), the solutions to your specific organization challenges may look different. Attend this 2-part webinar series for insights into what you need to know to take agile to the next level!
Part 1: Join SD Times Editor-in-Chief David Rubinstein and Agile Coaches Dave Gunther and Mike McLaughlin, who will explore the five key questions organizations need to consider when scaling agile to the program and portfolio levels including:
• How should we organize?
• How will we communicate?
• How, what and where will we prioritize?
• How can we facilitate decisions & plan effectively?
• How can we deliver predictably at scale?
After we finally seem to have settled the agile wars, between XP, Scrum and Kanban, the market
now starts to flood with enterprise agile frameworks, such as SAFe, DAD and Agility Path.
However, many organizations are still struggling with how to implement agile, even in
straightforward projects. During this vivid talk Sander Hoogendoorn, independent agile mentor,
software architect and developer, will share his years of experiences in implementing agile
principles and techniques in organizations, from the ground up, one step at the time. Sander does
not shy away from criticizing agile – especially enterprise agile – and will go through a series of
anti-patterns, pitfalls and roadblocks organizations encounter when moving towards agile, Scrum
and Kanban. He also shows how to get around them, illustrated with many real-life and examples,
and how to implement agile in baby steps.
We are in the age where lot of traditional business are building software that are truly disruptive and they have started to embrace agile.
Many fail to realise the importance of scaling their analysis practices, to successfully plan and shape their portfolio.
Previously working as an Agile Transformation Consultant, and taking part in delivery of products for large enterprises, this talk is about practical techniques that enterprises can take away to increase their organization agilty
Présentation effectuée par Charles-André Bouchard, dans le cadre du cours LOG3000 conduit par Mathieu Lavallée, à Polytechnique, mardi le 22 novembre 2016.
The document discusses how to prioritize business capabilities and system development to maximize business value. It recommends establishing the business value of each work item, prioritizing based on return on investment, and measuring business value delivery over time. It also suggests mapping business capabilities to system capabilities and identifying minimum releasable features to structure development and releases around delivering business value.
Agile Everywhere!
Henrik Kniberg talks about how his journey implementing agile & lean methods at Spotify and Lego helped him apply agility in new & unexpected fields. Henrik will share his vision on how agility may evolve in the future and affect various areas of our lives.
About Henrik Kniberg
Henrik Kniberg is an Agile/Lean coach at Crisp in Stockholm, working primarily with Lego and Spotify. He enjoys helping companies succeed with both the technical and human sides of software development. During the past 15 years he has been CTO of 3 Swedish IT companies and helped many more get started with Agile and Lean software development.
Henrik is former board member of the Agile Alliance and works regularly with Mary Poppendieck, Jeff Sutherland, and other thought leaders. He is the author of “Scrum and XP from the Trenches” and “Kanban and Scrum, making the most of both” and “Lean from the Trenches“. These books are available in over 12 languages, have over 500,000 readers, and are used as primary guide to Agile and Lean software development by hundreds of companies worldwide. Henrik also created the viral animated videos “Agile Product Ownership in a Nutshell” and “Spotify Engineering Culture“.
Agile Scaling with Blueprints (Goto Berlin, 04-dec-2015)
When more than 10 people are needed to reach a goal multiple agile teams are needed. These teams have to coordinate - we have to scale agile. There are several blueprints for scaling agile. This session argues that using a blueprint is premature optimization.
When looking at successful agile companies one thing becomes clear: they didn't follow a blueprint but implemented unique structures and processes. Every company is unique and needs unique structures and processes matching its purpose.
In this talk Stefan presents the Agile Scaling Cycle, an organic approach to find and optimize scaling structures appropriate for the company.
As more organizations begin to adopt agile on multiple, interdependent teams, how do we ensure that the success within a team can translate to success at the enterprise level?
Presented by: Sanjiv Augustine, President of LitheSpeed
Asia Agile Forum'16 Dhaka - Leadership, the pivot for scaling Agile up beyon...
This document discusses how leadership is the pivotal factor for scaling agile practices within organizations. It argues that prioritizing agile practices over principles is a key hurdle to achieving agility at scale. True agility requires influencing organizational culture towards agile values through visionary leadership. Leaders must scale their approach from tactical to strategic and participatory to demonstrate cultural change, provide a safe environment, and align people towards a shared vision. The pivot for achieving agility beyond the team level and throughout an organization lies in developing adaptive leadership.
Discusses some of the issues involved in scaling agile methods for large systems engineering.
Accompanies YouTube video atL
https://www.youtube.com/watch?v=GuK46hw3CyI
Scaling Agile With SAFe (Scaled Agile Framework)Andreano Lanusse
This document provides an overview of the Scaled Agile Framework (SAFe) for applying Lean and Agile practices at an enterprise scale. It discusses the key aspects of SAFe including the three levels (Team, Program, Portfolio), roles and activities within a Program like Release Planning and the Agile Release Train, and how features flow from the Portfolio through Epics and Programs down to individual Teams. The goal is to show how 5-10 Agile Teams can deliver shared objectives using SAFe to scale Agile practices beyond a single team.
This document discusses agile transformations and provides guidance on successfully implementing agile practices within an organization. It addresses the differences between agile adoption and transformation, what it means to be "agile", managing expectations, and key success practices. Barriers to transformation are outlined, along with case studies of challenges experienced and recommendations provided. The presentation concludes by discussing the paradigm shift required and outlining phases of agile adoption.
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
Exploring Agile Transformation and Scaling PatternsMike Cottmeyer
The goal of any enterprise agile adoption strategy is NOT to adopt agile. Companies adopt agile to achieve better business outcomes. Large organizations have no time for dogma and one-size-fits-all thinking when it comes to introducing agile practices. These companies need pragmatic guidance for safely and incrementally introducing structure, principles, and ultimately practices that will result in greater long term, sustainable business results. This talk will introduce a framework for safely, pragmatically, and incrementally introducing agile to help you achieve your business goals.
This document discusses transforming organizations to agile practices. It begins by outlining common goals for going agile such as predictability, quality, and innovation. It then discusses considerations for transformation based on organization size and dependencies. The key aspects for transformation are identified as backlogs, teams, and working tested software. Governance structures, metrics, and teaming strategies are also discussed. Transformation is framed as a journey, and quadrants are used to illustrate where organizations are currently and where they aim to go.
Leading a large-scale agile transformation isn’t about adopting a new set of attitudes, processes, and behaviors at the team level… it’s about helping your company deliver faster to market, and developing the ability to respond to a rapidly-changing competitive landscape. First and foremost, it’s about achieving business agility. Business agility comes from people having clarity of purpose, a willingness to be held accountable, and the ability to achieve measurable outcomes. Unfortunately, almost everything in modern organizations gets in the way of teams acting with any sort of autonomy. In most companies, achieving business agility requires significant organizational change.
Agile transformation necessitates a fundamental rethinking of how your company organizes for delivery, how it delivers value to its customers, and how it plans and measures outcomes. Agile transformation is about building enabling structures, aligning the flow of work, and measuring for outcomes based progress. It's about breaking dependencies. The reality is that this kind of change can only be led from the top. This talk will explore how executives can define an idealized end-state for the transformation, build a fiscally responsible iterative and incremental plan to realize that end-state, as well as techniques for tracking progress and managing change.
Why transform to Agile? What are the impediments to Agile Transformation? How to plan the Agile transformation? How to accelerate and sustain the Agile Transformation.
Agile Transformation is a consulting firm that specializes in organizational transformation using Agile, Lean, and other methods. They help clients transform their processes, teams, and culture to improve performance. Their services include assessing needs, developing custom roadmaps, coaching teams in Agile practices, and training leaders in skills like servant leadership and collaboration. Clients praise how Agile Transformation helped them successfully transform their culture, empower teams, and bridge gaps between departments.
Successful Agile Transformation - The NCS StoryNUS-ISS
Presented by Mr Lee Chee Yong, Agile Practice Lead of NCS Agile Competency Centre at ISS Seminar - Agile Software Development: Swift and the Shift on 18 July 2014.
The Scaled Agile Framework (SAFe) is an agile framework for enterprise-scale organizations. It addresses challenges of architecture, integration, funding, and roles at scale. SAFe has three levels - portfolio, program, and team. At the portfolio level, investment themes drive budget allocations. The program level uses Agile Release Trains of 5-10 teams to deliver value in 10 week iterations. Teams use Scrum or Kanban with 2 week iterations. SAFe aims to apply lean-agile principles at an enterprise scale.
Agile Eastern Europe 2011 Large Scale Agile Transformationpskapa
The document describes a large scale agile transformation at a global retailer. It discusses why the transformation was undertaken due to issues like long development times and quality problems. It then details how the transformation was implemented over several phases, including piloting agile practices, establishing agile roles and processes, and ongoing improvements. The transformation was considered successful, leading to benefits like reduced time to market, increased innovation, and becoming an employer of choice. The lesson learned is that organizations should understand their reasons for transforming before embarking on the journey.
Rick Austin - Portfolio mangement in an agile world [Agile DC]LeadingAgile
When organizations move to agile for software delivery, there is often tension with traditional portfolio management. This talk will illustrate how an organization can move from traditional portfolio management approaches to one that embraces agile software delivery. Doing so enables organizations to become predictable, improve the flow of value delivered, and pivot more quickly if necessary.
We will demonstrate the use of governance that allows a more adaptive portfolio management approach. We will cover topics that enable agile portfolio management including:
Lean techniques for managing flow
Effective prioritization techniques
Long range road-mapping
Demand management and planning
Progressively elaborated business cases
Validation of outcomes
Support for audit and compliance needs
These topics will be illustrated by real-world examples of portfolio management that have been proven over the last five years with a wide range of clients.
Presentation to OU Agile special interest group 25 January 2017. Agile basics, Agile myths, and stories of breakthroughs and breakdowns in Agile adoption in learning design and course production.
This document discusses the agile mindset and contrasts it with the traditional waterfall mindset. It defines mindset as a person's way of thinking and opinions. The agile mindset values individuals and interactions, customer collaboration, responding to change, and valuing working software over documentation. It also discusses agile principles, practices like Scrum and Kanban, and the differences between doing agile and having an agile mindset. The document contrasts fixed and growth mindsets and provides indicators of an agile mindset at both the team and organizational levels. It also discusses common agile pitfalls and provides resources for further reading.
The document provides an introduction to agile methods for executives. It discusses how agile approaches can help organizations adapt to increasingly volatile business environments. The key benefits of agile include shorter time to market, increased productivity, improved alignment with business needs, and greater predictability. The document outlines agile concepts like iterative development, minimal viable products, continuous delivery and focus on customer value. It also summarizes common agile frameworks like Scrum and how agility can be scaled in large organizations.
Scaled Agile Framework in 10 minutes (CAS2015)Unai Roldán
Scaled Agile Framework in 10 minutes (SAFe 3.0)
- Scaled: SAFe is designed for large-scale software development ecosystems of 50-125 people who need to resolve inter-dependencies
- Agile: SAFe is based on 9 Lean-Agile principles
- Framework: SAFe is a collection of a proven efficacy tools, and you only have to use what you need
https://www.youtube.com/watch?v=vysQQx7pQzg
El objetivo de la Lightning Talk es dar una visión "light" pero completa de lo que propone Scaled Agile Framework 3.0 como marco de referencia para el escalado de Agile.
Scaled Agile Framework es uno de los marcos de referencia para escalado de Agile que mayor aceptación está teniendo a día de hoy, sobre todo cuando hablamos de grandes organizaciones. El marco SAFe parte de las capas de abstracción clásicas de una organización para estructurar un cambio de perspectiva y de cultura basándose en los 4 valores y 9 principios Lean-Agile, apoyándose además en las prácticas Scrum-XP de desarrollo de productos. En la charla descubriremos de manera rápida los roles, artefactos y ceremonias que plantea el marco para conseguir un cambio de paradigma sostenible en las organizaciones.
Unai Roldán
UST Global
This document provides an overview of agile methodology for software development. It discusses how agile practices arose in response to the limitations of traditional waterfall approaches. The core principles of agile include valuing individuals and interactions, working software, customer collaboration, and responding to change. Agile methods embrace changing requirements, frequent delivery of working software, collaboration between business and technical teams, self-organizing teams, and continuous improvement.
An Introduction to Scaled Agile Framework (SAFe)CA Technologies
To compete in today’s application economy, organizations have adopted agile execution techniques. But is that enough? Learn about SAFe and how to leverage this methodology to elevate your agile teams to deliver quality outcomes and align at the enterprise level.
For more information, please visit http://cainc.to/Nv2VOe
Management is dead, at least traditional management is. No need to tell you what’s wrong with traditional management, you’ve probably experienced it yourself. And the results are outrageous, be it at company level, team level, and individual level; downright from project failures to complete demotivation of the staff.
Managers need to evolve, or they simply won’t survive if they don’t bring solutions to the above problems. From traditional management to … Agile management and leadership. You, as an experienced manager or as a wannabe/junior manager, are in a key position to change this.
By attending this 60-minutes talk, you’ll (re-)discover proven and actionable techniques to improve your management skills, foster team productivity, and keep morale and motivation atop. Yes, success is that close ;-)
On October 13, 2016, Tom Haak of the HR Trend Institute gave a keynote at "HR on the Move 2016", organised by AOG School of Management. This is the pack of slides he used.
Large Scale Agile Transformation by Husni RoukbiAgile ME
The agile manifesto introduced a new way of implementing software development projects which resulted in a dramatic improvement in these types of projects. Agile success at the project level has prompted IT leaders within organization to try to scale it to the enterprise level with less success rate. In this interactive session, we will review the various approaches to large-scale agile transformation, discuss the transformation road map and organizational change management required as well as key drivers/sponsors required for a successful agile transformation. We will discuss how to measure transformation progress, and outline possible challenges and corresponding solutions.
The PPT is about scaling agile across various non-cross-functional teams and the various experiments that were done before arriving at a methodology that worked for the teams.
AgileLIVE: Scaling Agile to the Program & Portfolio Levels - Part 1VersionOne
Are you ready to maximize the impact of delivering in an agile framework across your organization, yet challenged by scaling agile beyond the team level to the program and portfolio levels? Transforming a larger organization to agile requires deliberate change and coordination. While there are frameworks developing, such as the Scaled Agile Framework® (SAFe™), the solutions to your specific organization challenges may look different. Attend this 2-part webinar series for insights into what you need to know to take agile to the next level!
Part 1: Join SD Times Editor-in-Chief David Rubinstein and Agile Coaches Dave Gunther and Mike McLaughlin, who will explore the five key questions organizations need to consider when scaling agile to the program and portfolio levels including:
• How should we organize?
• How will we communicate?
• How, what and where will we prioritize?
• How can we facilitate decisions & plan effectively?
• How can we deliver predictably at scale?
After we finally seem to have settled the agile wars, between XP, Scrum and Kanban, the market
now starts to flood with enterprise agile frameworks, such as SAFe, DAD and Agility Path.
However, many organizations are still struggling with how to implement agile, even in
straightforward projects. During this vivid talk Sander Hoogendoorn, independent agile mentor,
software architect and developer, will share his years of experiences in implementing agile
principles and techniques in organizations, from the ground up, one step at the time. Sander does
not shy away from criticizing agile – especially enterprise agile – and will go through a series of
anti-patterns, pitfalls and roadblocks organizations encounter when moving towards agile, Scrum
and Kanban. He also shows how to get around them, illustrated with many real-life and examples,
and how to implement agile in baby steps.
We are in the age where lot of traditional business are building software that are truly disruptive and they have started to embrace agile.
Many fail to realise the importance of scaling their analysis practices, to successfully plan and shape their portfolio.
Previously working as an Agile Transformation Consultant, and taking part in delivery of products for large enterprises, this talk is about practical techniques that enterprises can take away to increase their organization agilty
Présentation effectuée par Charles-André Bouchard, dans le cadre du cours LOG3000 conduit par Mathieu Lavallée, à Polytechnique, mardi le 22 novembre 2016.
The document discusses how to prioritize business capabilities and system development to maximize business value. It recommends establishing the business value of each work item, prioritizing based on return on investment, and measuring business value delivery over time. It also suggests mapping business capabilities to system capabilities and identifying minimum releasable features to structure development and releases around delivering business value.
Agile Everywhere!
Henrik Kniberg talks about how his journey implementing agile & lean methods at Spotify and Lego helped him apply agility in new & unexpected fields. Henrik will share his vision on how agility may evolve in the future and affect various areas of our lives.
About Henrik Kniberg
Henrik Kniberg is an Agile/Lean coach at Crisp in Stockholm, working primarily with Lego and Spotify. He enjoys helping companies succeed with both the technical and human sides of software development. During the past 15 years he has been CTO of 3 Swedish IT companies and helped many more get started with Agile and Lean software development.
Henrik is former board member of the Agile Alliance and works regularly with Mary Poppendieck, Jeff Sutherland, and other thought leaders. He is the author of “Scrum and XP from the Trenches” and “Kanban and Scrum, making the most of both” and “Lean from the Trenches“. These books are available in over 12 languages, have over 500,000 readers, and are used as primary guide to Agile and Lean software development by hundreds of companies worldwide. Henrik also created the viral animated videos “Agile Product Ownership in a Nutshell” and “Spotify Engineering Culture“.
Agile Scaling with Blueprints (Goto Berlin, 04-dec-2015)Stefan ROOCK
When more than 10 people are needed to reach a goal multiple agile teams are needed. These teams have to coordinate - we have to scale agile. There are several blueprints for scaling agile. This session argues that using a blueprint is premature optimization.
When looking at successful agile companies one thing becomes clear: they didn't follow a blueprint but implemented unique structures and processes. Every company is unique and needs unique structures and processes matching its purpose.
In this talk Stefan presents the Agile Scaling Cycle, an organic approach to find and optimize scaling structures appropriate for the company.
As more organizations begin to adopt agile on multiple, interdependent teams, how do we ensure that the success within a team can translate to success at the enterprise level?
Presented by: Sanjiv Augustine, President of LitheSpeed
This document discusses how leadership is the pivotal factor for scaling agile practices within organizations. It argues that prioritizing agile practices over principles is a key hurdle to achieving agility at scale. True agility requires influencing organizational culture towards agile values through visionary leadership. Leaders must scale their approach from tactical to strategic and participatory to demonstrate cultural change, provide a safe environment, and align people towards a shared vision. The pivot for achieving agility beyond the team level and throughout an organization lies in developing adaptive leadership.
Discusses some of the issues involved in scaling agile methods for large systems engineering.
Accompanies YouTube video atL
https://www.youtube.com/watch?v=GuK46hw3CyI
The Scaled Agile Framework (SAFe) has a special event that is held for every Program Increment (5 sprints-ish). This is a large scale, collaborative event including everyone from the Agile Release Train (50 people plus). This workshop will be a highly interactive event where all participants will be involved in one of many teams collaborating together to plan a single Program Increment for a single product.
The schedule will roughly contain:
Overview of SAFe Program Increment Planning
(Fictional) Business Context
Product / Solution Vision
Architecture Vision And Development Practices
Planning Session 1
Draft Plan Review
Planning Session 2
Final Plan Review
Risk ROAMing
Confidence Vote
Retrospective
L’agilité à l’échelle est l’une des dernières frontières à atteindre. Différents frameworks existent pour aider les entreprises à diffuser l’agilité à tous les niveaux de l’organisation. SAFe et Spotify sont surement les plus connus mais tout semble les opposer.
Là où Spotify est généralement vanté pour son respect du mindset agile, SAFe est lui diabolisé pour sa vision TopDown et les craintes que suscitent ce schéma presque trop parfait.
Mais alors, c’est qui le champion ? Y’a t-il vraiment un vainqueur ?
by Moitié Benjamin and Renaud CHEVALIER
Scaling Agile Projects to Programs: Networks of Autonomy, Collaboration and E...Johanna Rothman
Are you trying to scale your agile project to a program, a collection of projects with one strategic objective? If you do what you’ve done with one small project, you’ll get bloat. Instead of bloat or large frameworks, you can use agile and lean approaches to manage your program with small-world networks. Small world networks help each team to remain autonomous, and still collaborate and explore across the program.
The common risks for software programs are how to manage the interdependencies, how to nurture the architecture, how to see the status, and how to release an entire product. When we ask feature teams to collaborate and take responsibility across the organization, the teams can manage many of the interdependency and architecture challenges. With program management, we can see the status and release the entire product.
This document provides an introduction to Agile methodology. It discusses how Agile addresses problems in software development like lack of predictability, transparency, and responsiveness to change. It then defines what Agile is from a mindset, values, and principles perspective. It also outlines some popular Agile flavors like Scrum, Kanban, SAFe, and XP. Finally, it walks through what a day or sprint looks like for a Scrum team, including roles, artifacts, meetings, and how stories are planned and tracked on a Scrum board. The overall document serves to introduce the core concepts and promise of Agile software development.
This document discusses scaling agile across large organizations. It introduces agile mindset, values, principles and practices. It also covers several frameworks for scaling agile such as Large Scale Scrum (LeSS), Scaled Agile Framework (SAFe), and Disciplined Agile Delivery (DAD). Adopting agile requires changes to organizational culture and giving autonomy and mastery to self-organizing teams. Scaling agile is not just about processes but transforming the mindset and empowering people.
Scrum_Blr 11th meet up 13 dec-2014 - Introduction to SAFe - Nagesh_SharmaScrum Bangalore
The document provides an introduction to the Scaled Agile Framework (SAFe) for applying agile practices at an enterprise scale. It discusses challenges organizations face with scaling agile and how SAFe addresses these challenges through its three layers (Portfolio, Program, Team). SAFe draws from Scrum, Extreme Programming, Kanban, lean principles and flows to provide transparency, alignment and program execution capabilities. It emphasizes continuous delivery through Agile Release Trains, empowered self-organizing teams, and roles like the Product Owner and Release Train Engineer. An example case study shows how a financial services company rapidly adopted SAFe to deliver more value faster by aligning their portfolio and programs.
The document discusses various frameworks for scaling agile development in large organizations. It introduces Disciplined Agile Delivery (DAD), the Scaling Agile Framework (SAFe), Agility Path, Continuous Improvement Framework (CIF), and Large Scale Scrum. DAD is described as a decision-oriented framework, while SAFe is presented as more prescriptive. The document emphasizes that principles are more important than practices and that adopting an agile mindset is key to successful scaling.
Антон Семенченко, опыт в IT более 10 лет, работает в компании ISSoft, специализируется в разработке и автоматизированном тестировании ПО плюс менеджмент\продажи. C++ Architect, Automation Practice Lead, PM, Group Manager
«Agile ValueTeam, учимся понимать Scrum». IT секция. Agile отделение. Для всех уровней подготовки.
«Как эффективно продавать Automation Service». IT секция. Продажи.
«Как эффективно организовать Автоматизацию, если у вас недостаточно времени, ресурсов и денег». Development секция. Отделение тестирования.
NetCom Learning : How to Improve Business Processes using AgileSwati Chhabra
Organizations intend to improve their business processes quickly and cost-effectively in today’s dynamic world. Agile Business Process Management (BPM) contributes to transform the business landscape in several aspects and organizations are also embracing it.
Scrum Bangalore 14th MeetUp 05 September 2015 - Scaling Agile - Saikat Das - ...Scrum Bangalore
This document summarizes an approach to scaling Agile in a mid-size enterprise eCommerce company. It discusses the motivation to scale Agile, provides an overview of common scaling frameworks, and describes the company's journey to scaling Agile across multiple teams and locations. Key aspects of the scaling model include establishing a cadence of sprints and releases, implementing feature-driven teams, adopting Scrum of Scrums, and establishing communities of practice. Outcomes of scaling included improved team performance, increased customer satisfaction, reduced delivery cycle times, and lower costs. Challenges included coordinating distributed teams and maintaining synchronization across teams.
Introduction to Enterprise Agile FrameworksMehul Kapadia
The document provides an overview of several enterprise agile frameworks: SAFe (Scaled Agile Framework), DAD (Disciplined Agile Delivery), and LeSS (Large Scale Scrum). It describes the foundations, roles, events, and distinctive features of each framework at a high level. Additionally, it provides references and resources for further exploration of these frameworks.
This document provides a five step approach to adopting agility across an entire organization. The first step is to build agile skills in people by establishing an agile role progression and providing training tailored to different roles. The second step is to make the adoption agile itself by educating stakeholders, establishing accountable adoption teams, and launching pilot projects. The third step is to focus agility at different levels including focusing the product portfolio, releasing more frequently, and letting teams flow work independently. The fourth step is to not forget principles of innovation like using scrum patterns, the lean startup approach, and flexible budgeting frameworks. The final step is that frameworks are just tools and the core is to create a simple but reliable agile process.
The Agile Method and AGILE ISD; how to use each to improve your training programChristopher King
The document discusses how Agile development methods and AGILE instructional design can be used together to improve training programs. It describes how Agile was created to make software development more flexible and rapid, and how AGILE was created for the same reasons for instructional design. While they have different focuses, Agile on software tactics and AGILE on comprehensive learning, they are complementary. The document advocates using Agile values, Scrum framework, and iterative development with AGILE instructional design and the ADDIE model to create both formal training and structured performance support. This holistic approach aims to better link learning to job performance.
How to become a great DevOps Leader, an ITSM Academy WebinarITSM Academy, Inc.
Presenter: Mustafa Kapadia, Service Line Leader, IBM
The ideal DevOps Leader is a tactical or strategic individual who helps design, influence, implement or motivate the cultural transformation proven to be a critical success factor in DevOps adoption. The most successful DevOps leaders understand the human dynamics of cultural change and are equipped with practices, methods, and tools to engage people across the DevOps spectrum. We will explore the role of the DevOps Leader in more detail.
The document discusses agile frameworks like Scrum and scaled agile frameworks. It defines Scrum and its components like sprints, artifacts, roles. It notes that Scrum is difficult to master. It discusses how agile scales to multiple teams through roles like the Program/Release Train Engineer who coordinate flow across teams.
The document outlines an agenda for a training on Agile concepts for executives. It includes introducing Agile concepts, characteristics of Agile teams, roles and responsibilities of Agile leaders, how Lean and Agile work together, and Lean/Agile leadership models. It also describes exercises used in the training, such as the Penny Game, and covers topics like Scrum framework, product backlogs, planning in Agile, and governance with dynamic budgeting.
Principle 11 needs to go! by Ken France at #AgileIndia2019Agile India
The Principles in the Agile Manifesto provide us guidance on how to have an Agile mindset in our organizations. Principle 11 within the Manifesto states "The best architectures, requirements, and designs emerge from self-organizing teams". While this works well for autonomous teams, it proves to be challenging for large organizations with dozens or even hundreds of teams who need to share common architectures and design patterns.
This talk will present a case study of a large retail organization and explore their journey from a highly centralized/governance-based technology organization to a more distributed/collaborative one and explore their lessons learned and success/failure patterns along the way. In the end, we'll answer the question about whether or not Principle 11 scales!
More details:
https://confengine.com/agile-india-2019/proposal/9281/principle-11-needs-to-go
Conference link: https://2019.agileindia.org
The Five Phases of Agile Maturity (Part 3): Phase 5Cprime
The journey to agile maturity is neither fast nor straightforward. What do you need to know? What challenges might you face? Which tools will best meet your organization where it's at?
Learn:
- Common maturity elements of Phase 5 of agile maturity (The Scaling Agile Enterprise)
- Challenges you may face in the last phase of your agile maturity journey and how to overcome them
- How Jira Align’s features and functionality can support your Agile enterprise
- How to utilize custom-tailored solutions to meet your specific needs
The document provides an overview of agile software development principles and practices. It discusses benefits of agility such as faster time to market and better responsiveness. Common agile frameworks like Scrum and Kanban are summarized. Extreme programming practices for engineering are outlined. The document also discusses scaling agile through frameworks like SAFe and applying lean principles to software development. Overall it serves as a high-level introduction to agile concepts, methods and roles.
Agile Transformation is a Journey, a continuous Learning Process. As part of Transformation capability Improvement, Cultural change should happen naturally by the change in habit and behavior of the people and help customer achieve their Business Goals.
Contact 98408 60639 for Agile Mentorship and Career guidance with SAFe RTE and other SAFe guidance. SAFe RTe, SAFe POPM, SAFe SA, SAFe SSM. To contact directly contact in
Aspiring Agile Coached/RTE/Scrum Masters
https://www.linkedin.com/safety/go?url=https%3A%2F%2Fchat.whatsapp.com%2FFCWEtJJJ0YyKWKXXExRR5x
WhatsApp /click from mobile https://wa.me/+919840860639
SRE Roundtable with 4 DevOps Ambassadors
A roundtable conversation about Site Reliability Engineering (SRE).
Please join us as four of the DevOps Institute's Ambassadors discuss SRE.
DevOps and SRE (and a little history of Google and SRE) - Helen Beal
SRE and ITIL - Donna Knapp
Benefits of SRE - Craig Pearson
SRE and Security - Niladri Choudhuri
And then the team will answer questions for 30+ minutes. We are very interested in hearing your questions. You can tweet them to @ITSMAcademy, add to the registration form, or bring them with you and chat in during the session.
How to improve Customer and Employee Experience with IT Service ManagementITSM Academy, Inc.
This document provides a summary of a presentation on improving customer and employee experience with IT service management. It introduces the presenter, Chris Gallacher, and his background in IT service delivery and consulting. It then defines customer experience and employee experience, explaining that both are based on perceptions of interactions with an organization. The presentation discusses why digital customer experience is important for IT organizations and outlines a framework for measuring CX and EX maturity. It also provides tips on adopting an outside-in perspective, developing a clear vision and strategy, and getting started with initiatives like journey mapping and defining moments that matter.
Donna Knapp, Curriculum Development Manager, ITSM Academy
How to Create a Great Customer Experience
A key activity in the ITIL 4 service value chain is 'engage'. One reason why this activity is particularly important is that it represents the start of the customer journey. The most successful organizations understand and master the customer journey; often by walking in their customers’ shoes and experiencing the end-to-end journey for themselves.
In this session, Donna Knapp introduces concepts from the new ITIL® 4: Drive Stakeholder Value publication including ways to optimize the customer journey and create a great customer experience.
Donna Knapp, Curriculum Development Manager, ITSM Academy
Digital has changed everything! It has enabled organizations to introduce new business models and to significantly change how they do business. Most importantly, it has changed expectations regarding the development, delivery, and use of digital technologies. Speed is crucial, but not at the expense of quality and resilience. In this session, Donna Knapp introduces concepts from the new ITIL® 4 High Velocity IT publication including new ways of thinking and working when speed (across the organization, not just in IT) is key.
The document provides an agenda for an ITIL4 and ServiceNow overview presentation. It includes introductions of the presenter, Mario Vivas. It then provides overviews of ITIL4, focusing on its practices and dimensions of service management. It discusses the ServiceNow platform and its key product lines and applications for incident management, problem management, change management, service catalog, knowledge management and demonstrations. The presentation aims to highlight ITIL4 guiding principles and how ServiceNow supports various ITSM processes and practices through its applications and integrations.
Vicki Rogers, Senior Manager of Change, Georgia Tech
Learn how Georgia Tech adopted the IT change management process (AKA change enablement practice in ITIL v4), designed to help control the life cycle of strategic, tactical, and operational changes to IT services through standardized procedures.
In this webinar, host Vicki Rogers will briefly describe and define change management and how it fits into the ITSM model, touching on changes with ITIL v4.
Please join us as Vick
Is this the End of ITIL? NO, it is the end-to-end of ITIL!ITSM Academy, Inc.
Paul Wilkinson, GamingWorks
Is this the End of ITIL? NO, it is the end-to-end of ITIL!
As we celebrate the first year anniversary of ITIL 4, enterprises are working their way to understand and clarify the full impact and value of the update. Do these questions sound familiar to you (or have you asked them yourself?):
"ITIL 4 is theoretical, how do we translate theory into practice?"
"How do you demonstrate the relevance of ITIL 4?"
"How do we get buy-in from the other stakeholders in the value chain?"
"How do we get the business to buy-in to apply effective IT governance to prioritize scarce resources against exploding demands?"
"Do we need to shift from SLAs to XLAs?"
In this session we will explore how the MarsLander Experiential Learning Workshop has been effectively used to address these challenges and show concrete, pragmatic takeaways.
And yes, Paul will be talking about their simulation, but will also unveil lots of pragmatic advice you can use to better understand the value proposition of ITIL 4.
Artificial Intelligence (AI) & The Future of Employee ServiceITSM Academy, Inc.
Dan Turchin, Astound
he bots are coming… but not to take your job. Learn how and why AI and machine learning are making humans better and how organizations like McDonald’s and adidas are delivering better service today.
Astound co-founder Dan Turchin will discuss the future of AI in IT and provide actionable tips that will guarantee your AI initiatives succeed.
Key takeaways:
How artificial intelligence is impacting IT
Why machine learning accelerates shift left strategies
How AI and natural language processing (NLP) are used to improve KPIs like MTTR, FCR, cost per ticket, and customer satisfaction
How AI-driven automation benefits the entire service lifecycle from provisioning and monitoring to incident, problem, and change management
Greg Sanker, CIO, Author, speaker and practitioner with over 30 years of global IT experience
Every organization makes changes on a daily basis, and every change has the potential to go wrong and potentially do great harm to the business. How do you balance the need to manage risk, without slowing everything to a grinding halt to go to CAB?
Thankfully, ITIL 4 has some great news, and this webinar will get you up to speed on Change Control.
What’s in it for you?
Join if you:
Want to know what’s new in ITIL4 Change Control
Have an unpopular CAB
Need help doing change management in a DevOps world
Far more than a new name for the same old thing, Change Control helps you manage changes at the speed of business.
Introducing “The V*A*L*U*E Formula: Do more with less and reduce stress"ITSM Academy, Inc.
Ken Wendle, Author, speaker, consultant and instructor
A common thread shared by almost every best practice or methodology – from ITIL to Lean to DevOps - is VALUE. Understanding, focusing on and improving our value ultimately is the most important thing any organization can do.
The V*A*L*U*E Formula - an exciting new book by Ken Wendle - explains and explores the “five essential elements of value” which work together to help individuals and organizations define, focus, augment, differentiate and deliver their full value potential.
This webinar will introduce and discuss “The V*A*L*U*E Formula” and model.
Topics and Key Takeaways:
It comes down to VALUE
Crafting a compelling Value Vision
Aspects of Alignment
Facets of Leverage and Uniqueness
Unleashing value through effective Execution
Alan Nance, FISM, Managing Partner CitrusCollab LLLP ... thought leader, innovator, creative disruptor
Service Management exists to guarantee a valuable experience to customers and colleagues. Despite years of implementing best practices, the reputation of most technology departments is below par in the eyes of business leaders.
90% of CEOs feel they aren’t meeting their customer needs.
85% of CEOs don’t think technology is performing critical functions.
One of the core reasons is that technology teams are often trapped into measuring output rather than outcome, and KPIs on activities rather than XPIs that guarantee experience.
Luckily, ITIL 4 now connects to the world of design thinking and experience management with its focus on co-creation and outcomes. But how can we include eXperience Level Agreements (XLA) effectively and quickly?
In this presentation Alan will explain all-things XLA.
DJ Schleen, DevSecOps Evangelist
You wouldn’t make changes in a production environment without testing first, so why make changes to a production pipeline and risk breaking the CI/CD process? This talk will introduce the concept of Blue/Green *pipelines* to optimize flow and continuously experiment with security toolsets without interrupting critical DevSecOps infrastructure. If you are a Continuous Delivery Architect, or are interested in minimizing interruption while integrating security toolsets this talk will resonate with you.
Mark Blanke, OwlPoint
Whether you are new to ITIL, Captains of ITIL 3 - or somewhere in between, this webinar is for you. Join us as Mark Blanke, President of OwlPoint, shares with us 5 practical steps to map where your organization is today and how to plan for your journey.
Donna Knapp, ITSM Academy's Curriculum Development Manager / Author
ITSM Academy was so excited to introduce ITIL 4 in our January webinar. We can tell our 300+ audience members were excited as well by the number of questions we did get to answer. Join us in February for an extended Q&A session and the latest ITIL 4 news.
Donna Knapp
Join us for an introduction to ITIL 4. We’ll share – at a high level – key ITIL 4 concepts and how those concepts support the management of modern IT services. If your organization is leveraging agile, lean and DevOps practices, you will like what you see in this current evolution of the ITIL framework.
Mike Orzen, Lean Technologist / Author, Donna Knapp, Curriculum Development Manager / Author
It’s been said that where there is demand there is a value stream. It seems you can’t visit an IT website these days without reading about the importance of value stream management. As Agile, Lean and DevOps practices accelerate our ability to satisfy customer demand, it’s important that ITSM professionals understand the relationship between value streams and processes.
Join Mike Orzen, author of Lean IT and The Lean IT Field Guide and Donna Knapp, author of The ITSM Process Design Guide, for a conversation about value streams and the benefits of incorporating Lean thinking into our continuous improvement efforts. Mike and Donna will set the stage and then ‘open up the mics’ for your questions about anything related to value streams and value stream mapping.
Sean Mack, CEO, xOps
There is a prevalent myth that DevOps and IT Service Management (ITSM) and the IT Infrastructure Library (ITIL) are incompatible. However this supposition has very little basis. ITIL is a framework from which you can take or leave portions you like and, in fact, this framework provides many useful paradigms for DevOps help implementations.
There’s actually wide synergy between ITIL and DevOps. If we understand ITIL as a process framework and see DevOps as, primarily, a culture of collaboration, there is no reason we cannot have a process framework integrate very well with a culture of collaboration.
This talk looks at the overlap of ITIL and DevOps and outlines some practical ways in which the DevOps philosophy can be applied to ITIL and operations process management.
Modernizing Service Management Processes with Self-Service AccessITSM Academy, Inc.
Webinar - Nick Schneider - Driven by a range of initiatives: DevOps, Digital Transformation, Modern Operations, etc - today Infrastructure and Operations organizations are experiencing growing pressure to modernize established ITSM processes and practices. The impetus is help streamline and accelerate software and service delivery to safely improve their organization’s speed, agility and responsiveness to the market. This presentation will provide real world experiences and practical guidance on how to modernize key processes with Self Service Access to safely empower software developers with autonomy, feedback loops and visibility across the end to end SDLC (Software Development Lifecycle).
Service Portfolio - Preparing for the Future of your OrganizationITSM Academy, Inc.
This document discusses the importance of service portfolio management for organizations. It defines a service portfolio as the complete set of services managed by a service provider. An effective service portfolio articulates business needs, services offered to meet those needs, and how resources will be allocated. It represents all current and planned commitments to customers. Implementing a service portfolio ensures the right mix of services to balance IT investment with business outcomes. The presentation reviews how to define services, implement a service portfolio, structure the portfolio, manage it through the service lifecycle, and consider portfolio design. Effective service portfolio management provides strategic direction and financial discipline for an organization.
Status Quo or Status Whoa? with Brad Utterback, an ITSM Academy WebinarITSM Academy, Inc.
Presenter: Brad Utterback, ITSM Consultant and Trainer
Whoa is often used to "stop" motion. But it is also an idiom for something that causes us to pay attention. For example, something that's new, creative and a game changer for the business. Continual Service Improvement is a set of best practices that can help you move off the " status quo" and on to the "status WHOA" by ensuring the service organization grows and changes with the business and ensuring your people are enabled to innovate and create new ways of being effective and efficient.
Please join us as we explore in more detail the benefits of Continual Service Improvement.
論文紹介:A Systematic Survey of Prompt Engineering on Vision-Language Foundation ...Toru Tamaki
Jindong Gu, Zhen Han, Shuo Chen, Ahmad Beirami, Bailan He, Gengyuan Zhang, Ruotong Liao, Yao Qin, Volker Tresp, Philip Torr "A Systematic Survey of Prompt Engineering on Vision-Language Foundation Models" arXiv2023
https://arxiv.org/abs/2307.12980
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data.
The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs.
Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution!
Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.
Blockchain technology is transforming industries and reshaping the way we conduct business, manage data, and secure transactions. Whether you're new to blockchain or looking to deepen your knowledge, our guidebook, "Blockchain for Dummies", is your ultimate resource.
UiPath Community Day Kraków: Devs4Devs ConferenceUiPathCommunity
We are honored to launch and host this event for our UiPath Polish Community, with the help of our partners - Proservartner!
We certainly hope we have managed to spike your interest in the subjects to be presented and the incredible networking opportunities at hand, too!
Check out our proposed agenda below 👇👇
08:30 ☕ Welcome coffee (30')
09:00 Opening note/ Intro to UiPath Community (10')
Cristina Vidu, Global Manager, Marketing Community @UiPath
Dawid Kot, Digital Transformation Lead @Proservartner
09:10 Cloud migration - Proservartner & DOVISTA case study (30')
Marcin Drozdowski, Automation CoE Manager @DOVISTA
Pawel Kamiński, RPA developer @DOVISTA
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
09:40 From bottlenecks to breakthroughs: Citizen Development in action (25')
Pawel Poplawski, Director, Improvement and Automation @McCormick & Company
Michał Cieślak, Senior Manager, Automation Programs @McCormick & Company
10:05 Next-level bots: API integration in UiPath Studio (30')
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
10:35 ☕ Coffee Break (15')
10:50 Document Understanding with my RPA Companion (45')
Ewa Gruszka, Enterprise Sales Specialist, AI & ML @UiPath
11:35 Power up your Robots: GenAI and GPT in REFramework (45')
Krzysztof Karaszewski, Global RPA Product Manager
12:20 🍕 Lunch Break (1hr)
13:20 From Concept to Quality: UiPath Test Suite for AI-powered Knowledge Bots (30')
Kamil Miśko, UiPath MVP, Senior RPA Developer @Zurich Insurance
13:50 Communications Mining - focus on AI capabilities (30')
Thomasz Wierzbicki, Business Analyst @Office Samurai
14:20 Polish MVP panel: Insights on MVP award achievements and career profiling
TrustArc Webinar - 2024 Data Privacy Trends: A Mid-Year Check-InTrustArc
Six months into 2024, and it is clear the privacy ecosystem takes no days off!! Regulators continue to implement and enforce new regulations, businesses strive to meet requirements, and technology advances like AI have privacy professionals scratching their heads about managing risk.
What can we learn about the first six months of data privacy trends and events in 2024? How should this inform your privacy program management for the rest of the year?
Join TrustArc, Goodwin, and Snyk privacy experts as they discuss the changes we’ve seen in the first half of 2024 and gain insight into the concrete, actionable steps you can take to up-level your privacy program in the second half of the year.
This webinar will review:
- Key changes to privacy regulations in 2024
- Key themes in privacy and data governance in 2024
- How to maximize your privacy program in the second half of 2024
Fluttercon 2024: Showing that you care about security - OpenSSF Scorecards fo...Chris Swan
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge.
You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter.
The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
Transcript: Details of description part II: Describing images in practice - T...BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and slides: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
BT & Neo4j: Knowledge Graphs for Critical Enterprise Systems.pptx.pdfNeo4j
Presented at Gartner Data & Analytics, London Maty 2024. BT Group has used the Neo4j Graph Database to enable impressive digital transformation programs over the last 6 years. By re-imagining their operational support systems to adopt self-serve and data lead principles they have substantially reduced the number of applications and complexity of their operations. The result has been a substantial reduction in risk and costs while improving time to value, innovation, and process automation. Join this session to hear their story, the lessons they learned along the way and how their future innovation plans include the exploration of uses of EKG + Generative AI.
Details of description part II: Describing images in practice - Tech Forum 2024BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
Coordinate Systems in FME 101 - Webinar SlidesSafe Software
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights.
During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to:
- Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value
- Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems
- Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors
- Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported
- Look Ahead: Gain insights into where FME is headed with coordinate systems in the future
Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
The DealBook is our annual overview of the Ukrainian tech investment industry. This edition comprehensively covers the full year 2023 and the first deals of 2024.
Best Programming Language for Civil EngineersAwais Yaseen
The integration of programming into civil engineering is transforming the industry. We can design complex infrastructure projects and analyse large datasets. Imagine revolutionizing the way we build our cities and infrastructure, all by the power of coding. Programming skills are no longer just a bonus—they’re a game changer in this era.
Technology is revolutionizing civil engineering by integrating advanced tools and techniques. Programming allows for the automation of repetitive tasks, enhancing the accuracy of designs, simulations, and analyses. With the advent of artificial intelligence and machine learning, engineers can now predict structural behaviors under various conditions, optimize material usage, and improve project planning.
4. 5
“…the ability to both create and
respond to change in order to profit in
a turbulent business environment.”
- Jim Highsmith
5
Definition of Agile
5. 66
The Culture of Change
1. Organizational structure is about how you
create teams and organize them
2. Agile practice is about the methods and
tools you choose to introduce
3. People and culture is about changing the
hearts and minds of the organization
- All three aspects are essential to sustain agility
of any kind within the organization.
6. 99
The Culture of Transformational Change
Agile
Adoption is
about the
‘Agile Doing’
side of the
equation.
Transformation
is about
changing the
‘Agile Being’
side of the
equation.
Long term results require both adoption and
transformation to be successful.
Culture is the #1 Challenge with Agile
Transformation.
8. 11
Three main challenges in scaling
teams:
Coordinating work across teams
Integrating work across teams
Maintaining technical integrity of the system
9. 12
• Scrum of Scrums (SoS)
• Large Scale Scrum (LeSS) - Larman/Vodde
• Scaled Agile Framework (SAFe) - Leffingwell
• Spotify “model” (Tribes, Squads, Chapters & Guilds) –
Kniberg
• Scrum at Scale – Sutherland/Brown
• Disciplined Agile Delivery (DAD) + Agility at Scale
Ambler/Lines
Scaling Approaches
Each of the popular scaling approaches offers a certain
value proposition, focus, options for implementation,
cost implications and other attributes
10. 13
Scrum of Scrums
Scrum of scrums is a technique
used to scale Scrum up to large
groups (over a dozen people),
consisting of dividing the groups into
Agile teams of 5-10. Each daily scrum
within a sub-team ends by designating
one member as "ambassador" to
participate in a daily meeting with
ambassadors from other teams, called
the Scrum of Scrums.
11. 14
Craig Larman characterizes LeSS as:
an organizational design based on ten LeSS Principles:
1. Large Scale Scrum is Scrum
2. Transparency
3. More with Less
4. Whole Product Focus
5. Customer Centric
6. Continuous Improvement
7. Lean Thinking
8. Systems Thinking
9. Empirical Process Control
10. Queueing Theory
Insights – LeSS (Large Scale Scrum)
15. 18
Insights – SAFE
… Scaled Agile Framework
• Is applicable whenever at
least a few hundred software
practitioners are working
cooperatively on related
products and solutions
• Has generated great
amounts of interest from
enterprises
• Is becoming supported by a
large number of Agile Tools
• The SAFe “big picture” has 3 levels:
portfolio, program, team
• Relatively more prescriptive,
pragmatic
• More controversial
• Evolving, growing, doing more
types of training
• Release Trains
17. 20
Insights – Spotify
… Spotify offers a culture-centric approach to Scaling
Agile
• Squads have end-to-end
autonomy over their products
• Loosely coupled, tightly
aligned
• Infrastructure
• Client Applications
• Features
• Squads = Scrum Teams
• Chapters = Competency Areas
• Tribes = Lightweight matrix of squads
and chapters
• Guilds = Communities of Practice
• Self-service, Open source model
• Focus on enabling each other
• Release Train
18. 21
Insights – Scrum at Scale
Reproducible Patterns
1.Modularity allows versatility.
2.Scrum is modular.
3.Deploying incrementally is modular.
4.Modularity supports a pattern library.
20. 23
Insights – DAD
DAD seeks to extend Scrum for enterprise
scale challenges
• People-first, learning-oriented hybrid agile
approach
• Risk-value delivery lifecycle and goal
driven
• Agility at scale is about explicitly
addressing the challenges teams face in
the real world
• Promotes Enterprise Awareness
• Key Differentiator – explicitly recognizes
that Agile teams are governed
21. 24
DAD supports a robust set of roles
• Team Lead
• Product Owner
• Architecture Owner
• Team Member
• Stakeholder
22. 25
Concept: the Agile 3C rhythm
The coordinate-collaborate-conclude rhythm occurs at several levels
on a disciplined agile delivery (DAD) project:
Construction
Construction
Construction
Release rhythm
Iteration rhythm
Daily rhythm
Inception Transition
Coordinate - Collaborate - Conclude
Inception
Inception
Transition
Transition
23. 26
DAD Teams Are Enterprise Aware
Disciplined Agilists:
Work closely with
enterprise groups
Follow existing
roadmaps where
appropriate
Leverage existing
assets
Enhance existing
assets
24. 27
Transformation at Scale
A Step by Step approach towards Enterprise
Agile Adoption
Projects should be evaluated to determine
their suitability for Agile.
Define Basic Agile
Model for the
organization.
Agree on a high
level adoption
roadmap
Identify Agile
practices and
prioritize
Identify Pilots and
assess for risks
Initial pilots Kick-off
Introduce Agile best
practices to the
teams
Train and Mentor
for several sprints
Refine Agile model
based on the
learning/feedback
Identify Additional
pilots
Create roadmap
Group training
Evangelize success
Mentor pilot project
Setup COE
Establish enterprise
architecture for
tools
Build mapping to
Enterprise processes
Establish Support
model for Agile
projects
Align to
organizational toll
gates
Audit processes
Calendar zed
training
Tailoring and
refactoring
Multiple LOB for
entire Enterprise
25. 28
• Ensure Executive buy-in
• Implement Scrum as a program / product
management framework
• Introduce Continuous Engineering practices
• Small, incremental rollout is proposed
• Identify pilot product to implement the agile
principles and practices
28
Proposed steps for Rollout – Principles and
Practices
26. 29
Agile and Scrum trainings for the entire team
Developers
Testers
Product Owner / Product Manager
Scrum Master(s)
Requirements writing (Stories, Use Cases)
Estimation Techniques
Relative Estimation
Story points
Planning Poker
29
Pilot Rollout & Trainings
27. 30
Integrated & Collaborative Governance
Line of
Business
Needs
Compliance
Needs
Customer
Needs
ValueStream
Product
Definition
Product Owner,
Customer, Human
Factors & Design,
Training, Business
Stakeholders, BAs
STEERING
DELIVERY
Product
Backlog
Sprint
Backlog
Program
Management
Office
Scrum Master,
Project Manager,
Architect,
Deployment,
Maintenance,
Support, Infra
Enterprise
Backlog
GOVERNANCE
Agile Center of
Excellence
Scrum of Scrums
Product Owners Scrum Masters
RESULTS&IMPEDIMENTS
VISION&RESOURCES
28. 31
Alignment
ValueStream Chief Product Owner
Product
Owner
Business
Stakeholder
Enterprise
Backlog
Agile
Teams
Agile
Teams
Agile
Teams
Agile
Teams
Executive Steering
• Enable Customer
Participation
• Provide Vision
• Resolve
Organizational
Impediments & Risks
• Provide Resources
• Resolve Priority
disputes
• Product Owner able
to represent
decisions made with
Stakeholders
• Stakeholders voice is
heard, differences
resolved, vision
clarified, priorities
and value
established
• Represent the
Customer and
Business needs
• Use Change
Management
Executive
Backlog
Product
Backlog
Sprint
Backlog
Business
Stakeholder
• Deliver Value
• Partner w/Business
Change
Management
Chief
BA
Chief
UX
Dev/Q
A Lead
Deploy
Lead
PMO
Rep
POs
Product Definition Office
Support Functions
• Architect
• Business
Analyst
• Development
• QA
• Deployment
Business
Stakeholder
Product
Owner
Business
Stakeholder
Business
Stakeholder
Business
Stakeholder
Product
Backlog
29. 32
Establish Communication & Collaboration Mechanisms
Keys to Effective Distributed Delivery
• Onshore & Offshore Tech Leads
• Offshore Customer Representatives
• Periodic travel rotation for offshore
resources
• Good Agile PM tools
• Automated Build/Continuous Integration
• Overlapping hours and daily standups
• Leveraging technology maximally
• Leverage Coaching & Common Training
• Whole teams offshore
• Common Planning
OFFSITE
TEAM
ORG
ONSITE
Shared Assets
(Req, Code, Tests, etc)
Agile PM Tools
90
DAYS
Planning
30. 33
Leverage Continuous Integration & Automation
Continuous Integration
Write Test
Run
Test
See Failure
Write Code
Run Test
See Success
Test First Development
Automation
Regression Tests
Functional Tests
System/Performance Tests
Automated Builds
32. 41
How do we measure success of Agile teams?
Process Measure Formula
Process Metric
Agile Maturity Index
Agile Maturity Index at the end of every
Sprint
Customer Satisfaction Customer rating at the end of every Sprint
Team Satisfaction
Team satisfaction rating at the end of
every Sprint
Retrospective Action
Items completed
% of Retrospective items completed
Automation capability % of Automation scripts / test scripts
Requirement Change
on Sprint – Discipline
% of Requirement change within the
Sprints
33. 4242
Key Agile Metrics – Using IT Balanced Scorecard
Balanced Scorecard Strategic Objectives Performance Measures
Financial Compliance Improve Budget Performance 1. Time to Value
2. Cost of Value
3. Earned value / release
Customer Value Increase Customer Satisfaction 1. Cycle time.
2. Customer Satisfaction
ratings.
Processes Project Delivery 1. Velocity
2. Avg project cycle time
3. Schedule performance
index
Decrease Defects 1. Defects
2. Unit Test Coverage
3. System Test Coverage
4. UAT Defects Found
5. Running tested features
Learning and Growth Enable Agile Transformation 1. Increase Agile Utilization.
2. Build community of
practice.
34. 43
Better Decisions through Frequent Feedback
Sample Metrics
Process Measure Formula
Velocity Actual Number of story points achieved in an iteration
Drag factor Actual Effort (unplanned) / Capacity
Iteration Defects No. of defects at the Iteration end / LOC
Story de-scoping index Stories descoped / Stories planned
Effort deviation (Actual effort – Planned effort) *100 / Planned effort
Build success rate Builds passed / Total # of builds
Automation & Test
Coverage
Unit test coverage, test case execution, etc
Burn Down & Burn Up Charts
Balanced Scorecard
Financial
Compliance
Customer
Value
Automated
Test Results
Code
Quality
Customer
Satisfaction
Learning &
Growth
35. 44
• Financial Compliance
• Customer Satisfaction
• Automated Test Results
• User Scenarios
• Code Quality
Measurement
Data
Logic
Integration
Interface
User
Scenario
User
Scenario
User
Scenario
User
Scenario
MUST SHOULD WANT
ProjectedActual
= Ship it!
Outcome based
status as slices of
user functionality.
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
UserStoriesDelivered
Time (Iterations)
Code Quality
• Extent of duplication
• Cyclomatic complexity
• Presence of large methods
• Code encapsulation
Qualification via Automation
• Unit Testing
• Integration Testing
• Functional Testing
• Automated regression
• Maximum Coverage
• Non-auto Exploratory
Agile PMO Distinctions
1. Define progress in terms of business value.
Focus on results instead of effort.
2. Burn up charts providing actual progress, cost
incurred, and value achieved.
3. Meaningful measurement of the code assets
4. Automation for reduced burden and increased
accuracy
5. Conduit for clearing impediments, ensuring
collaboration, getting resources
6. Ensure alignment to strategic goals and value.
ContinuousIntegration
IntegratedMeasurement
AutomationBalanced Scorecard
Actual Progress
(Value Delivered)
1
2
3
4
1
2
3
4
37. 46
• Started with team level practices
• Lots of attention early to team culture
• Began engaging leaders on strategy and portfolio
management
• Currently integrating marketing, sales, and
support
Methods:
Scrum of Scrums, Spotify
Single Team / Single Product
Sub 25 person product company and a start-up
38. 47
• Program level first …established a PO team
• Three tightly integrated Scrum teams
• Defined the portfolio governance layer
• Established the relationship between strategy
and support
• Modeled the overall value stream and wrapped
up the Scrum process in a two-tiered Kanban
Multi-Team / Single Product
Sub 100 person product company.
10 years old and privately owned.
Methods:
LeSS, Scrum of Scrums, Spotify
39. 48
• Started with a basic view of the portfolio layer
• Portfolio level value stream mapping, RACI
• Built out the program management layer with PO
teams to develop a requirements management
capability
• Program level value stream mapping, RACI, introduced
agile tooling
• Introduced Scrum at the team level
Multi-Team / Multi-Product
Large multi-national organization. Scope is a 500
person development organization with 55 Scrum
teams.
Methods:
SAFe, Scrum at Scale, LeSS, DAD
40. 49
• Scrum teams by product / component.
• Product owner teams established.
• Portfolio level governance model.
• Lean/TOC planning model.
• Integration with a traditional PMO for metrics
and monitoring.
Product of Products
Large multi-national company. Geographically
dispersed. Products of products.
Methods:
SAFe, Scrum at Scale, LeSS, DAD
43. 52
Links
Disciplined Agile Delivery (DAD) + Agility at Scale – Ambler/Lines
http://disciplinedagiledelivery.com
Large Scale Scrum (LeSS) – Larman / Vodde
http://www.craiglarman.com/wiki/index.php?title=Large-Scale_Scrum
Scaled Agile Framework (SAFe) – Leffingwell
http://scaledagileframework.com
Scrum at Scale
http://www.scruminc.com
Spotify Model
https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/
44. 53
Links
HyperGrowth Done Right - Lessons from the Man who Scaled
Dropbox and Facebook
http://firstround.com/review/Hyper-Growth-Done-Right-Lessons-From-the-
Man-Who-Scaled-Engineering-at-Dropbox-and-Facebook/
Wisdom from Hypergrowth Companies
http://www.startuplessonslearned.com/2013/10/wisdom-from-hyper-
growth-companies.html
45. 54
IT Balanced Scorecard – Agile Focus
Strategy Map Strategic
Objectives
Performance Measures Targets Initiatives
Financial
Compliance
Improve Project
Budget
Performance
1. Margin Contribution (or Revenue, or Cost, etc)
2. Earned Value/Release
3. Avg CPI – Cost Performance Index
4. Time to Value
1. TBD
2. TBD
3. 1 Month
• Measure IT contribution to Revenue
• Enable operations to release value every month to
production
• Reduce cycle time
• Use business measures
Customer Value Increase External
CSAT
1. Customer Satisfaction –CSAT >6/qtr • Implement CSAT for all branches and end users of
software
Internal Process Increase accuracy
of Estimates
1. E0/E1 Estimate Variance Delta <20%/spr • Measure and monitor estimates every sprint, take active
role in reducing variance
On Time Project
Delivery
1. Velocity & Std. Deviation
2. Drag factor
3. Avg Project Request Cycle Time - Requested
4. Avg Project Request Cycle Time - Scheduled
5. Sprint & Release Burndown performance trend
deviation
6. Customer Satisfaction –CSAT
7. Avg SPI – Schedule Performance Index
1. Varies/spr
2. <5%/spr
3. #prr/days
4. #prs/spr
5. <10%
6. >6/qtr
7. TBD
• Ensure operational measures are collected and collated
every sprint, by every sprint team.
• Ensure sprint and release burndowns are posted daily
(hours for teams, story points for everyone)
• Ensure CSAT surveys are created and part of goals
• PM to help teams track SPI during the release
Decrease Defect
RFCs in
Production
1. Defects/Story Point
2. Unit Test Coverage
3. System Test Coverage
4. UAT Defects Found
5. Running Tested Features
1. 0
2. >90%
3. >90%
4. 0
5. >90%
• Ensure consistent defect management across CRP and
INC test teams.
• Measure coverage every sprint
• Measure running tested features
Increase Audit
Compliance %
1. PQA Compliance 1. >90% • Educate teams about compliance, SM to help ensure
compliance
Increase % of
agreed scope
1. Story de-scoping index
2. User Story Volatility
1. <10%
2. <5%
• IT and Business measure needed. Indication of
partnership. Ensure collection and review.
Learning and
Growth
Enable Agile
Transformation
1. Increase Agile Utilization 1. >25%/qtr • Transformation team proactively working the roadmap
to work toward 100% (of goal) participation.
Enable People &
Culture
1. Increase Ace Participation
((people/events)/month)
1. >33% • Define and formalize the ACE program and participation
opportunities and guidelines.
46. 55
Key Agile Metrics
Measurement Frequency Target Notes
E0/E1 EV Delta Sprint <20% (E1 – E0/E1)*100
Velocity & Std. Deviation Sprint, Release varies varies by team
Drag factor Sprint, Release <5% (Actual Effort in story pts unplanned / velocity )
Avg Project Request Cycle Time - Requested Sprint, Release varies
days, measure end to end time from the time the request was submitted by the business to
the time it goes live in production. Alternatively, can measure the "request to scheduled"
cycle time and that can be added to the "scheduled to production" cycle time (below).
Value range will vary by request type (maint, s/m/l project), but also want average of all.
Avg Project Request Cycle Time - Scheduled Sprint, Release varies
days, measure end to end time from the time the request was scheduled by the business to
the time it goes live in production. Value range will vary by request type (maint, s/m/l
project), but also want average of all.
Sprint & Release Burndown Daily varies varies by team
Customer Satisfaction -CSAT Sprint >6
Implement for all groups (dev, support, biz functions, etc). Low CSAT indicate less
collaboration and potential increase in cycle time and/or duration. Also apps to Scope
Defects/Story Point Sprint varies
Unit Test Coverage Sprint >90%
System Test Coverage Sprint >90%
UAT Defects Found Sprint 0
Harder target due to Agile structure and PO involvement. New code going through UAT
should have 0 defects.
Running Tested Features Sprint 100%
Running Tested Features. Cumulative number of tests that are running for tested (non-
broken) features. Drives performance to ensure running code and tested code. Should
increase steadily on from the first sprint w/tests.
Story de-scoping index Sprint >10% (stories descoped / stories planned )
User Story Volatility <5%
((Story pts Descoped + Story pts Added + Story pts Modified)/ Story pts Originally Planned) *
100). This is important for helping track business activities in relation to changing scope.
Scope can slip due to development issues, but it also can slip do to a lack of focus and
prioritization and changing mindsets on the part of the business. Creates accountability on
both sides of the house.
Total Earned Value Sprint varies
Sum Total of earned value of stories completed. The pre-requisite of this approach is to
have story values assigned as part of the demand and prioritization process. Should be
tracked by the business.
Agile Utilization Month
as per
roadmap
Deliver competitive business value, cost optimization, improved compliance, and strategic
business alignment. (% Agile hrs/% total hrs)
Get Involved - ACE Participation Sprint >30% (% of people involved in some initiative)