Agile works. We get it. You don’t have to sell people on the underlying principles anymore. Even so, many large-scale agile transformations are struggling. Some have failed. Others can’t figure out why things aren't working after multiple attempts. It’s easy to blame the people, the process, and the culture. And it’s especially easy to blame management. However, the underlying problem is that most large organizations weren’t built to be agile. You need a way to safely and pragmatically refactor your company into an organization that can adopt agile and sustain the transformation. Mike Cottmeyer introduces a framework for understanding the type of company in which you work, its delivery constraints, and likely challenges you’ll face in your agile transformation. Mike shares a strategy for establishing an end-state vision and operational model to guide your transformation. Finally, he defines an approach for incrementally introducing change, measuring outcomes, and sustaining those changes.
This slide deck addresses the importance of proper functional design for creating resilient distributed systems (not only, but also microservice-based systems).
It starts by explaining the pitfall that many developers fall into when getting started with resilience: Quite often the effects of the fundamentals, i.e., creating bulkheads and choosing the communication paradigm, on system robustness at runtime are heavily underrated. Instead, the pure technical measures like circuit breakers, backpressure, etc. are often overestimated.
Unfortunately, all technical measures will not help to create a robust system if the functional design leads to highly coupled services where the availability of one service functionally totally depends on the availability of another service. The same is true if you need to call many services that all need to be available to answer a client request.
To make it worse, most of the wide-spread design approaches like functional decomposition, DRY (don't repeat yourself), design for re-use or layered architecture exactly lead to those problems, i.e., they are not suitable for designing distributed systems.
This slide deck does not offer any silver bullets to solve the problem (and actually I believe there is no silver bullet), but at least a few guiding principles. Additionally, it shows how the choice of the communication paradigm influences the bulkhead design and this way creates more options to create a good service design that also supports resiliency on a functional level.
As always this slide deck is without the voice track, i.e., most of the information is missing. But I hope that the slides on their own also provide some helpful hints.
Remark: As the "dismiss reusability" slide tends to get quite some attention, one more remark about that slide: On the voice track I usually add "If you find something that is worth being made reusable, i.e., that it satisfies the commercial constraints of Fred Brooks 'Rule of 9' (see https://blog.codecentric.de/en/2015/10/the-broken-promise-of-re-use/ for details), do not put it in a service. Instead create a library and put the functionality in there. And make sure that changes to the library do not mean that all users have to upgrade at the same time, but that any library user can update whenever it fits the user's schedule. Otherwise, you would have introduced tight coupling through the back door again."
Treating Your Pipeline as a Product - Full Day WorkshopManuel Pais
On completion of the workshop, you should have practical experience of techniques to treat your delivery chain as a first class citizen in your value stream, including testing, monitoring and recovering your delivery system.
MHA2018 - Agile Transformation Explained - Mike CottmeyerAgileDenver
"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."
Modern Change Management - 5 Universales del CambioJason Little
5 Universals of Change designed to help you be more agile in change management by focusing on what matters. PResented at Transformation LATAM 2020 (slides in EN and ES)
Modern Change Management - 5 Universals for ChangeJason Little
We’ve run over 450 workshops in 30 countries for over 5000 people and visited countless organizations of all sizes. We’ve discovered 5 Universals for Change that help you apply the right approach for change, at the right time.
Understanding the function of an Agile Coach is much more feasible once we acknowledge the set of “why’s” described in the previous section. An Agile Coach is a professional who will assist the organisation in solving the types of problems listed above. It’s possible to do it in different ways; however, let’s explore a few details regarding what is the gist of the activity of Agile Coaching.
We can summarise the essence of the work of an Agile Coach using a model called “The Agile Coaching DNA”. This DNA works as a compass to guide the decisions about which practices and approaches we can use to help clients achieve better results.
This slide deck addresses the importance of proper functional design for creating resilient distributed systems (not only, but also microservice-based systems).
It starts by explaining the pitfall that many developers fall into when getting started with resilience: Quite often the effects of the fundamentals, i.e., creating bulkheads and choosing the communication paradigm, on system robustness at runtime are heavily underrated. Instead, the pure technical measures like circuit breakers, backpressure, etc. are often overestimated.
Unfortunately, all technical measures will not help to create a robust system if the functional design leads to highly coupled services where the availability of one service functionally totally depends on the availability of another service. The same is true if you need to call many services that all need to be available to answer a client request.
To make it worse, most of the wide-spread design approaches like functional decomposition, DRY (don't repeat yourself), design for re-use or layered architecture exactly lead to those problems, i.e., they are not suitable for designing distributed systems.
This slide deck does not offer any silver bullets to solve the problem (and actually I believe there is no silver bullet), but at least a few guiding principles. Additionally, it shows how the choice of the communication paradigm influences the bulkhead design and this way creates more options to create a good service design that also supports resiliency on a functional level.
As always this slide deck is without the voice track, i.e., most of the information is missing. But I hope that the slides on their own also provide some helpful hints.
Remark: As the "dismiss reusability" slide tends to get quite some attention, one more remark about that slide: On the voice track I usually add "If you find something that is worth being made reusable, i.e., that it satisfies the commercial constraints of Fred Brooks 'Rule of 9' (see https://blog.codecentric.de/en/2015/10/the-broken-promise-of-re-use/ for details), do not put it in a service. Instead create a library and put the functionality in there. And make sure that changes to the library do not mean that all users have to upgrade at the same time, but that any library user can update whenever it fits the user's schedule. Otherwise, you would have introduced tight coupling through the back door again."
Treating Your Pipeline as a Product - Full Day WorkshopManuel Pais
On completion of the workshop, you should have practical experience of techniques to treat your delivery chain as a first class citizen in your value stream, including testing, monitoring and recovering your delivery system.
MHA2018 - Agile Transformation Explained - Mike CottmeyerAgileDenver
"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."
Modern Change Management - 5 Universales del CambioJason Little
5 Universals of Change designed to help you be more agile in change management by focusing on what matters. PResented at Transformation LATAM 2020 (slides in EN and ES)
Modern Change Management - 5 Universals for ChangeJason Little
We’ve run over 450 workshops in 30 countries for over 5000 people and visited countless organizations of all sizes. We’ve discovered 5 Universals for Change that help you apply the right approach for change, at the right time.
Understanding the function of an Agile Coach is much more feasible once we acknowledge the set of “why’s” described in the previous section. An Agile Coach is a professional who will assist the organisation in solving the types of problems listed above. It’s possible to do it in different ways; however, let’s explore a few details regarding what is the gist of the activity of Agile Coaching.
We can summarise the essence of the work of an Agile Coach using a model called “The Agile Coaching DNA”. This DNA works as a compass to guide the decisions about which practices and approaches we can use to help clients achieve better results.
Team Topologies - how and why to design your teams - AllDayDevOps 2017Matthew Skelton
From the AllDayDevOps 2017 live stream https://www.youtube.com/watch?v=XqowSG2Jxqc
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Takeaways:
- The implications of Conway’s Law for software teams
- Cognitive Load for teams
- Effective team topologies
- Team evolution
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.
Growing up with agile - how the Spotify 'model' has evolved Peter Antman
Spotify is known for its agile organization. But how did we end up with it, what are the founding principles and how has it evolved? Speech held at the Bay Area Agile Leadership Network 3/15 2016.
YouTube Link: https://youtu.be/3s2S-SNFCo4
** Edureka Certification Training: https://www.edureka.co **
This Edureka PPT on "Scaled Agile Framework" will help you understand how the scaled agile framework is used to scale agile practices and principles for large, complex and mission-critical projects. The topics discussed in this course are listed below:
Challenges of scaling agile
What is the Scaled Agile Framework (SAFe)?
Levels of Scaled Agile Framework
Configurations of SAFe
Advantages and Disadvantages of SAFe
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
The Secret, Yet Obvious, Ingredient to Sustainable AgilityAhmed Sidky
This was a presentation I gave at Ciklum in Kiev, Ukraine and at ScrumTrek in Moscow, Russia. The presentation discuss the notion of Agile and agility and then talks about what people should do to have sustainable agile. They key to sustainable agile is education. By educated, and changing the mindset of everyone in the company, then you will have sustainable agility. However, if you just focus on strategy, structure, and processes, but don't change the mindset and culture and habits of people it will not be sustainable. The presentation introduces the learning roadmap developed by the International Consortium for Agile (ICAgile) as a path organizations should pursue to engage their people in a common educational journey about agile and agility not Scrum or any particular process.
The International Consortium for Agile (ICAgile) accredits training organizations, corporations, academic institutes and government entities, thereby providing their members with over 20 knowledge-based and competency-based certifications to pursue, based on the ICAgile Learning Roadmap created by experts from around the world.
ICAgile is the only certification and accreditation body to offer knowledge-based and competency-based certifications in every discipline needed to sustain agility in an organization. ICAgile has engaged over 40 International Agile gurus and experts to create the most comprehensive agile learning roadmap.
ICAgile's Learning Roadmap is intentionally designed to focus on the education of agile not on any particular flavor or methodology of agile to ensure that every organization, can utilize the educational roadmap as it matures and customizes it agile processes and practices. ICAgile’s Learning Roadmap includes over 20 different certifications covering the disciplines of Agile Executive Leadership, Agile Coaching and Facilitation, Agile Enterprise Coaching, Agile Project Management and Governance, Agile Value Management and Business Analysis, Agile Software Design and Programming, and Agile Testing.
Driving on from Agile, organisations are looking to
dramatically increase the rate at which they deliver
new software updates to their customers / business
users by embracing DevOps. This presentation will
explain the Micro Focus approach to DevOps and
how we can help organisations like yours as they
move to Continuous Delivery.
eCloudChain's mission is to enable
enterprises to transform their
businesses by providing cuttingedge cloud-computing services including premier Consulting &
Business advisories,
Cloud monitoring & Cloud Migration services.
Agile Alliance maintains a guide on the practice areas of Agile software development. They include: extreme programming, teams, lean, scrum, product management, devops, design, testing and fundamentals. Each practice area is know as an Agile Tribe with its own definitions and best practices. Many of these practices overlap or are complementary. This file is an overview of the Agile Tribes displayed as a subway map.
When scaling Agile, an effective Scrum of Scrums is fundamental to success. This presentation covers common patterns for Scrum of Scrums, with varied purpose and format. Successful practices, learned experience, potential anti-patterns, and alternatives to Scrum of Scrums are included.
Presented at Agile New England as an ANE 101 session on 4 February 2021.
How agile coaches help us win the agile coach role @ SpotifyBrendan Marsh
In this talk, we cover:
- What is an Agile Coach at Spotify?
- What do they do?
- Why do we believe they help us win?
We also talk about:
- How do we scale or Organisation?
- High Performing Teams (What is a high performing team?)
- How are we measuring High Performance right now?
- How do we help teams reach High Performance?
Appendix:
- Chapter = Competency group
- Chapter Lead = Hiring Manager for Developer (or other) competency
Business and Technical Agility with Team Topologies @ CAS 2022Manuel Pais
Las organizaciones que no se adaptan rápidamente al entorno empresarial moderno y altamente cambiante están fracasando en gran número. El aumento de la regulación, las presiones del cambio climático, la digitalización y (recientemente) la pandemia de COVID-19 están impulsando la necesidad de agilidad empresarial en organizaciones de todos los tamaños.
En esta charla, explicaremos cómo los patrones y principios de Team Topologies promueven una verdadera agilidad del negocio a través de un flujo rápido de cambio de software (soportado por prácticas modernas de ingeniería), feedback rápido desde los sistemas en vivo, bajo acoplamiento sistémico y una visión de la arquitectura sociotécnica.
Team Topologies está ayudando a las organizaciones de todo el mundo a adaptarse a la "nueva normalidad" y lograr una verdadera agilidad empresarial. Miraremos ejemplos concretos de cómo han evolucionado algunas empresas bajo estos patrones y principios.
Uma conversa sobre os princípios e valores da agilidade, conectando a aplicação desses conceitos às práticas de pequenos passos bem medidos, validações de hipóteses e a descompressão do ambiente organizacional para que a Inovação possa aflorar. Uma construção da agilidade sobre a ótica da "desprojetização".
Implement an Enterprise Performance Test ProcessTechWell
Suddenly, application performance is important to your business, and you have been given the budget to improve it. You’re in a hurry because customers are complaining or because you expect jumps in transaction volume and your application needs to scale quickly. Do you know where to start? Join Ryan Riehle as he shares his experiences developing enterprise performance testing programs. Ryan covers the key techniques and heuristics that lead to an effective performance improvement effort. He discusses patterns teams use to effectively collaborate to achieve performance requirements, how to configure and organize test environments, considerations for application deployment and release cycles, appropriate metrics to use and how to report them, and strategies and techniques for data movement that support reproducible test results. But measuring alone does not solve the performance problem. So Ryan discusses how teams can act on testing results to improve and verify the impact of application and infrastructure changes.
Successful Test Automation: A Manager’s ViewTechWell
Many organizations invest substantial time and effort in test automation but do not achieve the significant returns they expected. Some blame the tool they used; others conclude test automation just doesn't work in their situation. The truth, however, is often very different. These organizations are typically doing many of the right things but they are not addressing key issues that are vital to long term test automation success. Describing the most important issues that you must address, Mark Fewster helps you understand and choose the best approaches for your organization—no matter which automation tools you use. We’ll discuss both management issues—responsibilities, automation objectives, and return on investment—and technical issues—testware architecture, pre- and post-processing, and automated comparison techniques. If you are involved with managing test automation and need to understand the key issues in making test automation successful, join Mark for this enlightening tutorial.
Team Topologies - how and why to design your teams - AllDayDevOps 2017Matthew Skelton
From the AllDayDevOps 2017 live stream https://www.youtube.com/watch?v=XqowSG2Jxqc
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Takeaways:
- The implications of Conway’s Law for software teams
- Cognitive Load for teams
- Effective team topologies
- Team evolution
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.
Growing up with agile - how the Spotify 'model' has evolved Peter Antman
Spotify is known for its agile organization. But how did we end up with it, what are the founding principles and how has it evolved? Speech held at the Bay Area Agile Leadership Network 3/15 2016.
YouTube Link: https://youtu.be/3s2S-SNFCo4
** Edureka Certification Training: https://www.edureka.co **
This Edureka PPT on "Scaled Agile Framework" will help you understand how the scaled agile framework is used to scale agile practices and principles for large, complex and mission-critical projects. The topics discussed in this course are listed below:
Challenges of scaling agile
What is the Scaled Agile Framework (SAFe)?
Levels of Scaled Agile Framework
Configurations of SAFe
Advantages and Disadvantages of SAFe
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
The Secret, Yet Obvious, Ingredient to Sustainable AgilityAhmed Sidky
This was a presentation I gave at Ciklum in Kiev, Ukraine and at ScrumTrek in Moscow, Russia. The presentation discuss the notion of Agile and agility and then talks about what people should do to have sustainable agile. They key to sustainable agile is education. By educated, and changing the mindset of everyone in the company, then you will have sustainable agility. However, if you just focus on strategy, structure, and processes, but don't change the mindset and culture and habits of people it will not be sustainable. The presentation introduces the learning roadmap developed by the International Consortium for Agile (ICAgile) as a path organizations should pursue to engage their people in a common educational journey about agile and agility not Scrum or any particular process.
The International Consortium for Agile (ICAgile) accredits training organizations, corporations, academic institutes and government entities, thereby providing their members with over 20 knowledge-based and competency-based certifications to pursue, based on the ICAgile Learning Roadmap created by experts from around the world.
ICAgile is the only certification and accreditation body to offer knowledge-based and competency-based certifications in every discipline needed to sustain agility in an organization. ICAgile has engaged over 40 International Agile gurus and experts to create the most comprehensive agile learning roadmap.
ICAgile's Learning Roadmap is intentionally designed to focus on the education of agile not on any particular flavor or methodology of agile to ensure that every organization, can utilize the educational roadmap as it matures and customizes it agile processes and practices. ICAgile’s Learning Roadmap includes over 20 different certifications covering the disciplines of Agile Executive Leadership, Agile Coaching and Facilitation, Agile Enterprise Coaching, Agile Project Management and Governance, Agile Value Management and Business Analysis, Agile Software Design and Programming, and Agile Testing.
Driving on from Agile, organisations are looking to
dramatically increase the rate at which they deliver
new software updates to their customers / business
users by embracing DevOps. This presentation will
explain the Micro Focus approach to DevOps and
how we can help organisations like yours as they
move to Continuous Delivery.
eCloudChain's mission is to enable
enterprises to transform their
businesses by providing cuttingedge cloud-computing services including premier Consulting &
Business advisories,
Cloud monitoring & Cloud Migration services.
Agile Alliance maintains a guide on the practice areas of Agile software development. They include: extreme programming, teams, lean, scrum, product management, devops, design, testing and fundamentals. Each practice area is know as an Agile Tribe with its own definitions and best practices. Many of these practices overlap or are complementary. This file is an overview of the Agile Tribes displayed as a subway map.
When scaling Agile, an effective Scrum of Scrums is fundamental to success. This presentation covers common patterns for Scrum of Scrums, with varied purpose and format. Successful practices, learned experience, potential anti-patterns, and alternatives to Scrum of Scrums are included.
Presented at Agile New England as an ANE 101 session on 4 February 2021.
How agile coaches help us win the agile coach role @ SpotifyBrendan Marsh
In this talk, we cover:
- What is an Agile Coach at Spotify?
- What do they do?
- Why do we believe they help us win?
We also talk about:
- How do we scale or Organisation?
- High Performing Teams (What is a high performing team?)
- How are we measuring High Performance right now?
- How do we help teams reach High Performance?
Appendix:
- Chapter = Competency group
- Chapter Lead = Hiring Manager for Developer (or other) competency
Business and Technical Agility with Team Topologies @ CAS 2022Manuel Pais
Las organizaciones que no se adaptan rápidamente al entorno empresarial moderno y altamente cambiante están fracasando en gran número. El aumento de la regulación, las presiones del cambio climático, la digitalización y (recientemente) la pandemia de COVID-19 están impulsando la necesidad de agilidad empresarial en organizaciones de todos los tamaños.
En esta charla, explicaremos cómo los patrones y principios de Team Topologies promueven una verdadera agilidad del negocio a través de un flujo rápido de cambio de software (soportado por prácticas modernas de ingeniería), feedback rápido desde los sistemas en vivo, bajo acoplamiento sistémico y una visión de la arquitectura sociotécnica.
Team Topologies está ayudando a las organizaciones de todo el mundo a adaptarse a la "nueva normalidad" y lograr una verdadera agilidad empresarial. Miraremos ejemplos concretos de cómo han evolucionado algunas empresas bajo estos patrones y principios.
Uma conversa sobre os princípios e valores da agilidade, conectando a aplicação desses conceitos às práticas de pequenos passos bem medidos, validações de hipóteses e a descompressão do ambiente organizacional para que a Inovação possa aflorar. Uma construção da agilidade sobre a ótica da "desprojetização".
Implement an Enterprise Performance Test ProcessTechWell
Suddenly, application performance is important to your business, and you have been given the budget to improve it. You’re in a hurry because customers are complaining or because you expect jumps in transaction volume and your application needs to scale quickly. Do you know where to start? Join Ryan Riehle as he shares his experiences developing enterprise performance testing programs. Ryan covers the key techniques and heuristics that lead to an effective performance improvement effort. He discusses patterns teams use to effectively collaborate to achieve performance requirements, how to configure and organize test environments, considerations for application deployment and release cycles, appropriate metrics to use and how to report them, and strategies and techniques for data movement that support reproducible test results. But measuring alone does not solve the performance problem. So Ryan discusses how teams can act on testing results to improve and verify the impact of application and infrastructure changes.
Successful Test Automation: A Manager’s ViewTechWell
Many organizations invest substantial time and effort in test automation but do not achieve the significant returns they expected. Some blame the tool they used; others conclude test automation just doesn't work in their situation. The truth, however, is often very different. These organizations are typically doing many of the right things but they are not addressing key issues that are vital to long term test automation success. Describing the most important issues that you must address, Mark Fewster helps you understand and choose the best approaches for your organization—no matter which automation tools you use. We’ll discuss both management issues—responsibilities, automation objectives, and return on investment—and technical issues—testware architecture, pre- and post-processing, and automated comparison techniques. If you are involved with managing test automation and need to understand the key issues in making test automation successful, join Mark for this enlightening tutorial.
Crafting Smaller User Stories: Examples and ExercisesTechWell
Agile development techniques generally emphasize frequent iterations. But even after adopting agile values, methods, and ceremonies, many organizations struggle to make such iterations work in practice. These organizations inevitably wrestle with agile rhythms until they learn to break up their work into small user stories that will fit within short iterations and allow for fast feedback. Stephen Frein discusses the importance of small user stories and how crucial they are to finishing the stories within the iteration and avoiding a mini-waterfall inside an iteration. After reviewing the characteristics of a good user story, Stephen introduces various techniques for identifying stories that could be decomposed into several other stories, along with accompanying practice exercises to help you get a good feel for the practical aspects of breaking up large stories. Join Stephen if you are having trouble finishing stories within their planned iterations or if your work seems to double in the last days of an iteration.
Many projects implicitly use some kind of risk-based approach for prioritizing testing activities. However, critical testing decisions should be based on a product risk assessment process using key business drivers as its foundation. For agile projects, this assessment should be both thorough and lightweight. Erik van Veenendaal discusses PRISMA (PRoduct RISk MAnagement), a highly practical method for performing systematic product risk assessments. Learn how to employ PRISMA techniques in agile projects using Risk Poker. Carry out risk identification and analysis, see how to use the outcome to select the best test approach, and learn how to transform the result into an agile one-page sprint test plan. Erik shares practical experiences and results achieved by employing product risk assessments. Learn how to optimize your test effort by including product risk assessment in your agile testing practices.
The Power of an Individual Tester: The HealthCare.gov ExperienceTechWell
Like millions of other Americans, Ben Simo visited HealthCare.gov in search of health insurance and found a frustratingly buggy website that was failing to fulfill its purpose―to educate people on the new health insurance law and help them purchase health insurance. After failing to create an account, Ben put on his tester hat and turned on his web developer tools. In addition to many functional and performance issues, Ben soon discovered a chain of security vulnerabilities that exposed users to unnecessary risk. Finding HealthCare.gov customer service unequipped to receive reports of security vulnerabilities, he blogged his discoveries, spawning a storm of public attention which hailed Ben as a “web expert,” “methodical IT guru," “folk hero”—and “not too bright.” His reports even came up in congressional hearings, where the Secretary of Health and Human Services referred to Ben as “a sort of skilled hacker.” Ben’s reports helped bring attention to problems that suggested a systematic lack of care and understanding of system design and information security. Join Ben as he shares his experience, the issues he found, and lessons testers can learn from HealthCare.gov.
The key to successful testing is effective and timely planning. Rick Craig introduces proven test planning methods and techniques, including the Master Test Plan and level-specific test plans for acceptance, system, integration, and unit testing. Rick explains how to customize an IEEE-829-style test plan and test summary report to fit your organization’s needs. Learn how to manage test activities, estimate test efforts, and achieve buy-in. Discover a practical risk analysis technique to prioritize your testing and become more effective with limited resources. Rick offers test measurement and reporting recommendations for monitoring the testing process. Discover new methods and develop renewed energy for taking your organization’s test management to the next level.
Mindmaps: Lightweight Documentation for TestingTechWell
Quality starts with requirements. In small to mid-size companies, it is not uncommon for the communication chain to be broken. Florin Ursu shares ways to avoid miscommunication through a streamlined process in which requirements are communicated to both developers and testers simultaneously; then developers write code while testers document what will be tested. Florin explores what mindmaps are; what they can be used for, both in general and applied to software development; and then dives deeper into how mindmaps can be used for testing. He describes how his teams use mindmaps to brainstorm, organize testing scenarios, prioritize work, review test scenarios, present results to stakeholders highlighting what was tested and (just as important) what was not tested, issues found, and risks. Using example mindmaps, Florin highlights important details captured in day to day work, including tips regarding format, communication style, and how to “sell” the idea of mindmaps to your stakeholders.
Survival Guide: Taming the Data Quality BeastTechWell
As companies scramble to adjust to the demands of an increasingly data-driven world, testers are told “go test data quality” without any guidance as to what that entails or how to go about it. The fact that the data is often a living, flowing ecosystem, rather than just a single object, requires the use of different strategies to gain meaningful insights. Shauna Ayers and Catherine Cruz Agosto guide you through the challenges of data quality and apply a structured approach to analyze, measure, test, and monitor living data sets, and gauge the business impact of data quality issues. Shauna and Catherine define data quality, describe the five goals of data quality management, provide the four pillars of data quality assurance, and show how data flow, scale, and properties interact to build the data quality landscape. Learn how to tame the data quality beast, determine what and how to test, overcome technical obstacles—and emerge with a usable plan of attack.
Innovation for Existing Software Product: An R&D ApproachTechWell
In the world of software, innovating an existing product often makes the difference between continued success and rapid irrelevance and failure. Although innovation can come from many different sources, it can be difficult to develop breakthrough innovations while simultaneously trying to maintain an existing piece of software. Aaron Barrett says that a stand-alone R&D team, freed from the constraints of production software, is a great answer to this dilemma. Join Aaron as he shares some simple guidelines to facilitate the process of integrating R&D efforts into an existing software product while avoiding R&D that does not lead to production-ready systems. Learn how and when to get company buy-in, actively engage your developers, and develop with your go-to-market strategy in mind to reap the innovation benefits of a dedicated R&D team.
What is the Internet of Things (IoT)? What are the technologies that make it happen? Where do we see it today? Where will we see it tomorrow? What capabilities will it provide, and what do we need to know to take part in it? Jim McKeeth considers where IoT is taking us and discusses the hurdles we face today and in the future. With a focus on applications, Jim offers examples of IoT technology from the perspective of developers. Join Jim to learn about cross-platform development, cloud synchronization, app-to-app communication, Bluetooth, WiFi, security concerns, privacy issues, and more. Look at specific IoT devices now available that are changing the landscape for businesses and the consumer. Is the Internet of Things the dawn of a new age or just another way for “Big Brother” to watch our every move? Come find the answers to this and other thought-provoking questions.
Building on Existing Infrastructure for Mobile ApplicationsTechWell
In 2013 Farm Credit Services of America (FCSAmerica) wanted to enter the mobile application arena so their customers could manage their FCSAmerica lending accounts. Anthony Carlson explains that in the previous thirteen years, FCSAmerica had built an SOA infrastructure for internal applications, including services for customer authentication, lending accounts, and remote check depositing. However, mobility had not been considered when the services were created, and these services were internally protected by a firewall inside their DMZ. If your company has concerns of exposing services to a mobile app, yet wants to reuse what already exists in the enterprise, then the concept of designing services through an API Gateway may be your answer. API Gateways are part of an API Management solution to deal with issues of integration and security. Anthony shares the benefits, challenges, and results of designing a system with an API Management solution to expose services to a mobile application.
At Walt Disney Parks and Resorts Technology, we provide the applications and infrastructure our online guests use to plan, book, explore, and enjoy their stay at our parks and resorts. With millions of page views per day and a multi-billion dollar ecommerce booking engine, we face a unique set of challenges. Join Les Honniball for insights into how they work with Product Owners and development teams to design tests, both manual and automated for these challenges. Les explains the testing processes that support a global set of brands on one web platform, including successful QA strategies, analytics, and user experience design―all while working within an agile development process. Discover how Les and his team of QA engineers work with various development teams in Orlando FL, Glendale CA, and Argentina to support many areas of Walt Disney Parks and Resorts Technology Business.
Mobile App Testing: The Good, the Bad, and the UglyTechWell
Mobile app testing has lots of good practices, some not so useful (bad) concepts, and some really ugly, don’t-ever-do ones. In the tradition of James Whittaker’s How to Break Software books, Jon Hagar applies the testing “attack” concept to mobile app software. Jon starts by defining the big problems and challenges of testing mobile app software and examines the patterns of product failures that you must attack. He then shares a set of good, bad, and ugly test techniques, which testers and developers can direct against their software to find important bugs quickly. Looking at native, web-based, and hybrid apps, Jon explains the pros and cons of each technique with examples to further your understanding. Finally, he gives you takeaway information on tools, automation, and test attacks your can begin using immediately. Go beyond basic functionality verification and learn how to attack your mobile apps with the best techniques while avoiding the ugly ones.
Metrics Program Implementation: Pitfalls and SuccessesTechWell
When we talk about product quality, test team efficiency, and productivity, we always talk numbers. However, very few companies implement metrics programs in a way that supports solid decision making. Many have tried and failed, leaving a negative impression of metrics. Kris Kosyk explains what metrics like Defect Removal Efficiency tell us and how it is impacted by Test Coverage and Defect Backlog Change Rate. Moving up a level, Kris explains how to use operational testing metrics to understand the development lifecycle process. Though it’s a common belief that a successful metrics program depends on the metrics selected, that is really only half the battle. The other half is a well-designed implementation of the metrics program and effective ongoing governance. Kris addresses these issues and other related questions, and shares a case study on her successes and mistakes while implementing a company-wide test metrics program for more than 200 projects.
Quality Index: A Composite Metric for the Voice of TestingTechWell
It is quite possible that you are spending a considerable amount of your time as a QA manager making sense of the multitude of metrics reported by your teams, connecting the facts, understanding the underlying reality, and articulating it to your peers and leadership. Still, others in the organization may not interpret the message correctly, rendering most of your efforts futile. Nirav Patel and Sutharson Veeravalli share insights to help you resolve this challenge through a composite measure called Quality Index. By aligning metrics to business outcomes and using Quality Index as a tool of articulation, disparate interpretation of data can be eliminated and a cohesive message delivered to stakeholders. Learn how QA can acquire a voice across the senior forums by articulating succinct, contextual, and actionable information to speed up executive decisions in the course of programs and projects.
Step-by-Step Guide to Leading a Large-Scale Agile TransformationTechWell
A few years ago everyone wanted to know how to convince their executives to go agile. Today, executives are asking their teams how they'll make the transformation. We have made significant progress changing the hearts and minds of senior leadership, but executives now demand a greater level of assurance that the plan is actually going to work. Executives are tired of being told to trust the team and that everything will be okay. Executives want to know how agile is going to help make things better. Mike Cottmeyer begins by discussing the elements of an agile transformation business case and how to identify a meaningful value proposition for change. Next, he considers how to assess the organization and build an agile transformation strategy and roadmap that encourage an iterative and incremental approach to change. Finally, Mike explores the metrics and controls that help you know if you're on the right track. Explore the change management and engagement techniques necessary to make sure you are building meaningful organizational support as you engage the enterprise.
Next Level Agile - David Hawks - Dallas Agile Leadership Network February 2019Agile Velocity
Today, most Agile leaders are trying to achieve predictable, fast delivery. While that’s good, it’s no longer good enough—not if we want to keep up in this highly competitive, rapidly changing world. Next Level Agility is about the ability of an entire organization to quickly adapt to market
changes.
In this session at Dallas Agile Leadership Network, David Hawks shared principles and practices that are the future of Agile organizations.
LEARNING OBJECTIVES
- Learn 3 key reasons for creating the urgency to improve
- Understand the mindset that is holding us back
- Discover 5 practices for evolving Agile to the next level
Why 76% of Organizations are Failing at Agile - Agile Cincinnati April 2019Agile Velocity
Traditional leadership paradigms, organization structures, and culture all get in the way of agility, as too many enterprises focus on team level change and framework implementation (Scrum and SAFe). Explore how leaders can guide their organizations past these barriers and accelerate the momentum towards true organizational agility.
'My Case for Agile Methods & Tranformation' : Presented by Saikat Das oGuild .
This paper describes Saikat's experiences with Agile values, tranforamtion and my implementation of them. He describes the circumstances that have led him to believe passionately that Agile Frameworks will best assure the success of his projects.
Competency models for the team and how to choose specific practices against the model.
He describes what has worked for him and why, and he describes what hasn’t worked and why.
Highlights:
A different Approach to look into Agile practices and Transformation.
The difference between Agile Adoption and Agile Transformation.
The real goal of Agile change initiatives.
Adapting Practices in Agile.
http://ow.ly/EHSHz
In this complimentary, hour-long webinar, you will learn how many organizations approach change management as compared to how best practices dictate that change management should work. Global Knowledge instructor and ITIL Expert Michael Scarborough will fill you in on the purpose of change management and the difference between change management and change tickets. He will provide a high-level guide for establishing a change management process that uses real-world examples as its basis.
How to Build Organizational Change Capabilities - Prosci WebinarTim Creasey
Prosci Webinar - How to Build Organizational Change Capabilities. Agenda: 1) What is Project ECM? 2) The case for Project ECM; 3) The status of Project ECM; 4) Current state, Future state, Transition state; 5) Prosci ECM Suite. Visit www.prosci.com/ecm to learn more about the Prosci ECM Suite.
The current definition of Business Agility is as nebulous as DevOps was only a few years ago. Some schools of thought focus on different parts of the business employing agile techniques. While an important step, it proves insufficient to allow the overall business to achieve true agility.
In this session, we will explore the emerging thinking on what is Business Agility and provide concrete examples of organizations who have taken steps to successfully achieve it.
Learning Objectives:
*Define Enterprise Business Agility in a holistic fashion
*Articulate real-world examples of Business Agility
*Begin to implement aspects of Business Agility within your organization
Scaling Agile Up to the Enterprise and Staying LeanTechWell
Scaling agile from the team to the program to the portfolio level of the enterprise requires the inclusion of additional roles—product manager and system architect; activities—release planning and program retrospectives; and artifacts—portfolio and program visions and backlogs. Practitioners must constantly increase scale and scope, while keeping both the system and the process lean and agile. Dean Leffingwell describes how to accomplish this with the Scaled Agile Framework™, a knowledge-base of proven lean and agile practices for enterprise-class software development. Dean approaches the scaling problem from the perspective of lean thinking and principle of product development flow, illustrating how their core principles help deliver business results at scale, while keeping the system—and the enterprise—responsive. Learn some key principles of lean thinking and product development flow, participate in lightweight exercises designed to reinforce these principles, and leave with an understanding of how to apply them in your organization.
Mary Thorn has had the opportunity in the past twenty years to work at many startups, creating several QA/test departments from scratch. For the past ten years, she has done this in agile software companies. Recently Mary moved from leading small agile test organizations to leading a large agile test organization where she has learned how to lead agile testers and agile testing in large contexts. Mary takes you through what she has learned, identifies the keys to transitioning your test organization as it grows, and discusses the techniques required to lead it through the changes. Agile testing is difficult; training your testers to be consistent and interchangeable across large scale agile teams is even more difficult; and still more difficult is test automation at scale. Join Mary as she shares her experience in creating an automation strategy that works in a large scale context and lessons learned from leading a large agile test organization.
Abstract: Many organizations are struggling with the speed and diversity of technology change. In this presentation we will discuss how to use concepts of patterns to make configurable and repeatable infrastructure topologies, improve speed and environmental consistency. By leveraging elasticity and auto scaling capacities of IBM PureApplications show how to increase application capacity. Demonstrate how the use of patterns improves testing, deployment and lowers risk. Finally we will show how the use of these concepts can be a catalyst for change, letting us challenge established barriers so we can embrace continuous improvement and DevOps.
Organizational Agility: Take Agile Beyond the Team - Webinar w/ David HawksAgile Velocity
The benefits of total organizational agility can be seen in many of the world’s largest companies--think Google, Apple, and Amazon. While they may not explicitly call themselves capital-“A” Agile, they work with a heavy emphasis on Agile principles like a focus on delivering value, shortened feedback loops, quick time-to-market, and an opposition to traditional top-down management techniques. These principles go beyond teams. Instead, they are ingrained throughout the whole organization and its culture.
As a result, these companies have the ability to change and adapt to their markets and have now grown into industry leaders. How did they do it? What can you learn from the changes they’ve made?
In this webinar, David Hawks discusses 7 ways your organization can begin operating more like some of the top companies in the world.
Key discussion points include:
- What is organizational agility and what are the benefits?
- 7 ways to bring organizational agility to your business
- Why is it imperative to apply Agile principles across the whole organization?
- Q&A with the audience
Looking for guidance during your Agile transformation? Contact info@agilevelocity.com for more information on how we can help.
User Stories Suck - David Hawks, Agile 2018Agile Velocity
Enjoy the full slide deck from David Hawks' presentation, User Stories Suck, from Agile 2018.
The current Epic and User Story process is stale and needs to go. David Hawks presented a new discovery centered model driven by Objectives, Hypothesis, and Experiments.
User Stories Suck by David Hawks at North Dallas Product Owners MeetupAgile Velocity
The User Story concept was invented almost 20 years ago, it’s time for an update. This outdated process supports an old way of working focused on predictable requirements delivery instead of product discovery. Wouldn’t you like to know much earlier which features are not going to be valued by your market? We need techniques that shorten the feedback loop with customers, not stakeholders. We need to prioritize based on riskiest assumptions and iterate quickly through small experiments in order to (in)validate our ideas as fast as possible.
Similar to Why Agile Fails in Large Enterprises—and What to Do about It (20)
Do you ever feel you have lost confidence in your own abilities? Why does this happen? Isabel Evans spends a lot of time painting. Someone once commented, “Why are you doing this, when you are not very good at it?” And gradually she stopped drawing and painting, after being intimidated by a conventional vision of what good art should look like. At the same time, she experienced a parallel loss of confidence in her professional abilities. Attempting creative pursuits like drawing and painting is essential to cognitive, emotional, creative abilities and she began to understand the correlation between her creative activities and her confidence. Making errors, being wrong, failing – that is a generous gift we receive when we practice outside our skill level. By staying in a comfort zone and repeating successes, we stagnate. As Isabel started to create again she thought “I don’t feel good at it, I do feel good doing it” The difference was that she was learning, having ideas and the act of re-engaging with failure, together with the comradeship of friends and colleagues, including at Women Who Test, Isabel has regained her confidence in her professional abilities, and been able to reboot her career and joy. Join Isabel to share a journey from self-perceived failure, to recovery and renewed learning.
Instill a DevOps Testing Culture in Your Team and Organization TechWell
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build ArchitectureTechWell
Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test design principles—applicable to organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage. Take back ideas about which test areas could benefit from being combined into a single suite and which areas could benefit most from being broken out altogether.
System-Level Test Automation: Ensuring a Good StartTechWell
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test StrategyTechWell
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for SuccessTechWell
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your SanityTechWell
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps StrategyTechWell
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOpsTechWell
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—LeadershipTechWell
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile TeamsTechWell
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile GameTechWell
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile TeamsTechWell
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery ProcessTechWell
DevOps is transforming software development with many organizations adopting lean development practices, implementing continuous integration (CI), and performing regular continuous deployment (CD) to their production environments. However, the database is largely ignored and often seen as a bottleneck in the DevOps process. Steve Jones discusses the challenges of database development and why many developers find the database to be an impediment to the CD process. Steve shares the techniques you can use to fit a database into the DevOps process. Learn how to store database code in a version control system, and the differences between that and application code. Steve demonstrates a CI process with SQL code and uses automated testing frameworks to check the code. Steve then shows how automated releases with manual gates can reduce the stress and risk of database deployments while ensuring consistent, reliable, repeatable releases to QA, UAT, and production.
Mobile Testing: What—and What Not—to AutomateTechWell
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for SuccessTechWell
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile TransformationTechWell
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
How Recreation Management Software Can Streamline Your Operations.pptxwottaspaceseo
Recreation management software streamlines operations by automating key tasks such as scheduling, registration, and payment processing, reducing manual workload and errors. It provides centralized management of facilities, classes, and events, ensuring efficient resource allocation and facility usage. The software offers user-friendly online portals for easy access to bookings and program information, enhancing customer experience. Real-time reporting and data analytics deliver insights into attendance and preferences, aiding in strategic decision-making. Additionally, effective communication tools keep participants and staff informed with timely updates. Overall, recreation management software enhances efficiency, improves service delivery, and boosts customer satisfaction.
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Top 7 Unique WhatsApp API Benefits | Saudi ArabiaYara Milbes
Discover the transformative power of the WhatsApp API in our latest SlideShare presentation, "Top 7 Unique WhatsApp API Benefits." In today's fast-paced digital era, effective communication is crucial for both personal and professional success. Whether you're a small business looking to enhance customer interactions or an individual seeking seamless communication with loved ones, the WhatsApp API offers robust capabilities that can significantly elevate your experience.
In this presentation, we delve into the top 7 distinctive benefits of the WhatsApp API, provided by the leading WhatsApp API service provider in Saudi Arabia. Learn how to streamline customer support, automate notifications, leverage rich media messaging, run scalable marketing campaigns, integrate secure payments, synchronize with CRM systems, and ensure enhanced security and privacy.
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns
Unlocking Business Potential: Tailored Technology Solutions by Prosigns
Discover how Prosigns, a leading technology solutions provider, partners with businesses to drive innovation and success. Our presentation showcases our comprehensive range of services, including custom software development, web and mobile app development, AI & ML solutions, blockchain integration, DevOps services, and Microsoft Dynamics 365 support.
Custom Software Development: Prosigns specializes in creating bespoke software solutions that cater to your unique business needs. Our team of experts works closely with you to understand your requirements and deliver tailor-made software that enhances efficiency and drives growth.
Web and Mobile App Development: From responsive websites to intuitive mobile applications, Prosigns develops cutting-edge solutions that engage users and deliver seamless experiences across devices.
AI & ML Solutions: Harnessing the power of Artificial Intelligence and Machine Learning, Prosigns provides smart solutions that automate processes, provide valuable insights, and drive informed decision-making.
Blockchain Integration: Prosigns offers comprehensive blockchain solutions, including development, integration, and consulting services, enabling businesses to leverage blockchain technology for enhanced security, transparency, and efficiency.
DevOps Services: Prosigns' DevOps services streamline development and operations processes, ensuring faster and more reliable software delivery through automation and continuous integration.
Microsoft Dynamics 365 Support: Prosigns provides comprehensive support and maintenance services for Microsoft Dynamics 365, ensuring your system is always up-to-date, secure, and running smoothly.
Learn how our collaborative approach and dedication to excellence help businesses achieve their goals and stay ahead in today's digital landscape. From concept to deployment, Prosigns is your trusted partner for transforming ideas into reality and unlocking the full potential of your business.
Join us on a journey of innovation and growth. Let's partner for success with Prosigns.
Navigating the Metaverse: A Journey into Virtual Evolution"Donna Lenk
Join us for an exploration of the Metaverse's evolution, where innovation meets imagination. Discover new dimensions of virtual events, engage with thought-provoking discussions, and witness the transformative power of digital realms."
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
In the ever-evolving landscape of technology, enterprise software development is undergoing a significant transformation. Traditional coding methods are being challenged by innovative no-code solutions, which promise to streamline and democratize the software development process.
This shift is particularly impactful for enterprises, which require robust, scalable, and efficient software to manage their operations. In this article, we will explore the various facets of enterprise software development with no-code solutions, examining their benefits, challenges, and the future potential they hold.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
May Marketo Masterclass, London MUG May 22 2024.pdf
Why Agile Fails in Large Enterprises—and What to Do about It
1. AW5
Agile Development Concurrent Session
11/12/2014 1:30 PM
"Why Agile Fails in Large
Enterprises—and What to Do
about It"
Presented by:
Mike Cottmeyer
LeadingAgile, LLC
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
2. LeadingAgile cofounder and president Mike Cottmeyer is
passionate about solving the challenges associated with agile in
larger, more complex enterprises. To that end, his company is
dedicated to providing large-scale agile transformation services to
help pragmatically, incrementally, and safely introduce agile
methods. Mike spends most of his time leading and growing
LeadingAgile, and providing strategic coaching for clients. He was
on the steering committee that created the PMI-ACP certification and
co-led the creation of the DSDM Agile Project Leader certification. A
fellow of the Lean Systems Society, Mike served on the boards of
the APLN and the Lean Software and Systems Consortium.
3. 11/4/2014
1
WHY AGILE IS FAILING
IN LARGE ENTERPRISES
WHY AGILE IS FAILING
IN LARGE ENTERPRISES
…and what you can do about it
5. 11/4/2014
3
Hirotaka Takeuchi
& Ikujiro Nonaka
The New New
Product
Development Game
DSDN Consortium
Dynamic System
Development
Method Jeff de Luca
Feature
Driven
Robert Charette
Lean
Development
Taiichi Ohno
Toyota Production
System
Kanban
1943
1950-
1960s
1985
1990
1995
1996
1997
1998
2000
2001
USAF & NASA
Development
Kanban
Hardware Software
USAF & NASA
X‐15 hypersonic jet
Iterative
Incremental Delivery
1990 - Sutherland &
Schwaber
Scrum Framework
1996 - Beck,
Cunningham,
Jeffries
Extreme
Programming
Alistair Cockburn
Crystal
Methodologies
THE
AGILE
MANIFEST
O
We are uncovering better ways of developing software by doing it
and helping others do it. Through this work we have come to value:
MANIFESTO VALUES
Individuals &
interactions
Processes & toolsover
Working software
Comprehensive
documentation
over
Customer collaboration Contract negotiationover
Responding to change Following a planover
That is, while there is value in the items on the
right, we value the items on the left more.
Source: www.agilemanifesto.org
6. 11/4/2014
4
Satisfy the Welcome Deliver Collaborate
MANIFESTO PRINCIPLES
Satisfy the
Customer
Welcome
Change
Deliver
Frequently
Collaborate
Daily
Support & Trust
Motivated
Teams
Promote
Face-to-Face
Conversations
Deliver
Working
Software
Promote
Sustainable
Pace
Promote
Technical
Excellence
Maximize
Through
Simplicity
Have
Self-Organized
Teams
Reflect &
Adjust
Regularly
Source: www.agilemanifesto.org
BELIEFS ABOUT AGILE &
TRANSFORMATION
7. 11/4/2014
5
Culture
BELIEFS…
PracticesStructure
• Focused on changing
hearts and minds
CULTURE DRIVEN
Culture
PracticesStructure
hearts and minds
• Focused on being agile
rather than doing agile
• Focused on values and
principles
PracticesStructure
8. 11/4/2014
6
• Focused on changing
hearts and minds
CULTURE DRIVEN
Culture
PracticesStructure
hearts and minds
• Focused on being agile
rather than doing agile
• Focused on values and
principles
• Belief that delivery
systems will emergePracticesStructure systems will emerge
based on new thinking
• Focused on the things
that you do
PRACTICES DRIVEN
Practices
StructureCulture
that you do
• Focused on roles,
ceremonies, and artifacts
• Can be management
driven or technically
driven
StructureCulture
9. 11/4/2014
7
• Focused on the things
that you do
PRACTICES DRIVEN
Practices
StructureCulture
that you do
• Focused on roles,
ceremonies, and artifacts
• Can be management
driven or technically
driven
B li f th t il iStructureCulture • Belief that agile is a
process or way to work
• Focused on forming
teams and governing the
STRUCTURE DRIVEN
Structure
CulturePractices
teams and governing the
flow of value
• Focused on aligning the
organization first
CulturePractices
10. 11/4/2014
8
• Focused on forming
teams and governing the
STRUCTURE DRIVEN
Structure
CulturePractices
teams and governing the
flow of value
• Focused on aligning the
organization first
• Belief that culture and
practices only emerge
within a rational structuralCulturePractices within a rational structural
and planning framework
Culture
... all three are essential,
but where you start
WHERE TO START?
PracticesStructure
is also essential…
12. 11/4/2014
10
Theory of Transformation
Tr e agilit comes bTrue agility comes by
breaking dependencies
between teams across the
organization
Theory of Transformation
Health c lt re and solidHealthy culture and solid
practices emerge within a
rational delivery framework
17. 11/4/2014
15
WHY AGILE WORKS
AT SCALE
Screen
User Story
User Story
Team
Database
Report
User Story
User Story
User Story
User Story
User Story
M blClarity Accountability
Measureable
Progress
23. 11/4/2014
21
WHY AGILE FAILS
AT SCALE
Screen
User Story
User Story
Team
Database
Report
User Story
User Story
User Story
User Story
User Story
L k fLack of
Clarity
Lack of
Accountability
Lack of
Measureable
Progress
29. 11/4/2014
27
Matrixed
Organizations
Non-instantly
Available
Resources
Too Much Work
In Process
Limited Access
to Subject Matter
Expertise
Team
Shared
Requirements
Between Teams
Matrixed
Organizations
Non-instantly
Available
Resources
Too Much Work
In Process
Limited Access
to Subject Matter
Expertise
Large Products
with Diverse
Technology
Team
Shared
Requirements
Between Teams
30. 11/4/2014
28
Matrixed
Organizations
Non-instantly
Available
Resources
Too Much Work
In Process
Limited Access
to Subject Matter
Expertise
Large Products
with Diverse
Technology
Team
Shared
Requirements
Between Teams
Technical Debt &
Defects
Matrixed
Organizations
Non-instantly
Available
Resources
Too Much Work
In Process
Limited Access
to Subject Matter
Expertise
Large Products
with Diverse
Technology
Team
Low Cohesion &
Tight Coupling
Shared
Requirements
Between Teams
Technical Debt &
Defects
31. 11/4/2014
29
Corollary One:
Sol ing for the iss es that getSolving for the issues that get
in the way of effectively
practicing agile is what should
guide your agile
transformation initiative
MAPPING YOUR AGILE
TRANSFORMATION
37. 11/4/2014
35
Emergence
Ad-Hoc Lean Startup
Project Pilot
Predictability
Adaptability
AEPE
PC AC
Convergence
Traditional Agile
Emergence
Ad-Hoc Lean Startup
Project Pilot
Predictability
Adaptability
AEPE
PC AC
Convergence
Traditional Agile
38. 11/4/2014
36
Emergence
Ad-Hoc Lean Startup
Adopt Pilot
Predictability
Adaptability
AEPE
PC AC
Convergence
Traditional Agile
Emergence
Ad-Hoc Lean Startup
LOB
Predictability
Adaptability
AEPE
PC AC
Convergence
Traditional Agile
39. 11/4/2014
37
Emergence
Ad-Hoc Lean Startup
LOB
Low Trust
Predictability
Adaptability
AEPE
PC AC
Convergence
Traditional Agile
Emergence
Ad-Hoc Lean Startup
LOB
Low Trust
Predictability
Adaptability
AEPE
PC AC
Convergence
Traditional Agile
LOB
Become Predictable
40. 11/4/2014
38
Emergence
Ad-Hoc Lean Startup
LOB
Low Trust
Predictability
Adaptability
AEPE
PC AC
Convergence
Traditional Agile
LOB
Become Predictable
Emergence
Ad-Hoc Lean Startup
LOB
Low Trust
Predictability
Adaptability
AEPE
PC AC
Convergence
Lean/Agile Agile
LOB
Become Predictable
41. 11/4/2014
39
Emergence
Ad-Hoc Lean Startup
LOB
Low Trust
Predictability
Adaptability
AEPE
PC AC
Convergence
Lean/Agile Agile
LOB
Become Predictable
LOB
Reduce Batch Size
Emergence
Ad-Hoc Lean Startup
LOB LOB
Low Trust Fully Decouple
Predictability
Adaptability
AEPE
PC AC
Convergence
Lean/Agile Agile
LOB LOB
Become Predictable Reduce Batch Size
42. 11/4/2014
40
Corollary Two:
Agile can mean differentAgile can mean different
things to different companies
and not all agile approaches
will work well for every
organization
INCREMENTAL AND
ITERATIVE IMPROVEMENT
43. 11/4/2014
41
Emergence
Ad-Hoc Lean Startup
Org
Slice
Low Trust Fully Decouple
Predictability
Adaptability
AEPE
PC AC
Slice
Convergence
Lean/Agile Agile
Become Predictable Reduce Batch Size
Emergence
Ad-Hoc Lean Startup
Org
Slice
Low Trust Fully Decouple
Predictability
Adaptability
AEPE
PC AC
Slice
Convergence
Lean/Agile Agile
Become Predictable Reduce Batch Size
Phase
One
44. 11/4/2014
42
Emergence
Ad-Hoc Lean Startup
Org
Slice
Low Trust Fully Decouple
Predictability
Adaptability
AEPE
PC AC
Slice
Convergence
Lean/Agile Agile
Become Predictable Reduce Batch Size
Phase
One
Phase
Two
Emergence
Ad-Hoc Lean Startup
Org
Slice
Low Trust Fully Decouple
Predictability
Adaptability
AEPE
PC AC
Slice
Phase
Three
Convergence
Lean/Agile Agile
Become Predictable Reduce Batch Size
Phase
One
Phase
Two
45. 11/4/2014
43
Emergence
Ad-Hoc Lean Startup
Org
Slice
Low Trust Fully Decouple
Predictability
Adaptability
AEPE
PC AC
Slice
Phase
Three
Phase
Four
Convergence
Lean/Agile Agile
Become Predictable Reduce Batch Size
Phase
One
Phase
Two
Emergence
Ad-Hoc Lean Startup
Org
Slice
Low Trust Fully Decouple
Phase
Five
Predictability
Adaptability
AEPE
PC AC
Slice
Phase
Three
Phase
Four
Convergence
Lean/Agile Agile
Become Predictable Reduce Batch Size
Phase
One
Phase
Two
46. 11/4/2014
44
Corollary Three:
Organi ational change can beOrganizational change can be
mapped out in such a way
that outcomes are
measureable and predictable
and economically justified
DEVELOPING YOUR
ROADMAP
50. 11/4/2014
48
Product Teams – These teams
integrate services and write customer
facing features. This is the proto-
typical Scrum team.
Team
Services Teams – These teams
support common services across
product lines. These teams support the
needs of the product teams.
Team
Programs Teams – These teams
define requirements, set technical
direction, and provide context and
coordination.
Product Teams – These teams
integrate services and write customer
facing features. This is the proto-
typical Scrum team.
Team
Team
Services Teams – These teams
support common services across
product lines. These teams support the
needs of the product teams.
Team
51. 11/4/2014
49
Portfolio Teams – These teams
govern the portfolio and make sure that
work is moving through the system.
Programs Teams – These teams
Team
define requirements, set technical
direction, and provide context and
coordination.
Product Teams – These teams
integrate services and write customer
facing features. This is the proto-
typical Scrum team.
Team
Team
Services Teams – These teams
support common services across
product lines. These teams support the
needs of the product teams.
Team
TeamTeamTeam
Product &
Services
Teams
Team Team Team Team
57. 11/4/2014
55
Program
Portfolio
Teams
Kanban
Kanban
Team
• Cycle Time
Product &
Services
Teams
Program
Teams
Scrum
Kanbany
• Features Blocked
• Rework/Defects
• Backlog Size
• Velocity
• Burndown
• Escaped Defectsp
• Commit % Rate
• Acceptance % Ratio
• Scope Change
Program
Portfolio
Teams
Kanban
Kanban
• Cycle Time
• Takt Time/Cycle Time
• Time/Cost/Scope/Value
• RIO/Capitalization
Product &
Services
Teams
Program
Teams
Scrum
Kanban
• Backlog Size
• Velocity
• Burndown
• Escaped Defects
y
• Features Blocked
• Rework/Defects
p
• Commit % Ratio
• Acceptance % Ratio
• Scope Change
58. 11/4/2014
56
Corollary Four:
Organi ational constr ctsOrganizational constructs,
governance models, metrics
and controls can be
established without violating
the principles of agile
INCREMENTAL
TRANSFORMATION
65. 11/4/2014
63
Program
Portfolio
Teams
Kanban
Kanban
Agile Pilot Agile Rollout
Team
Product &
Services
Teams
Program
Teams
Scrum
Kanban
Team Team
TeamTeamTeam
Team
Iteration Three Iteration One
Team Team TeamTeam
Program
Portfolio
Teams
Kanban
Kanban
Agile Pilot Agile Rollout
Team
Product &
Services
Teams
Program
Teams
Scrum
Kanban
Team Team
TeamTeamTeam
Team
Iteration Four Iteration Two
Team Team TeamTeam
66. 11/4/2014
64
Program
Portfolio
Teams
Kanban
Kanban
Agile Pilot Agile Rollout
Team
Product &
Services
Teams
Program
Teams
Scrum
Kanban
Team Team
TeamTeamTeam
Team
Iteration Five Iteration Three
Team Team TeamTeam
Corollary Five:
Organi ations can adopt agileOrganizations can adopt agile
safely and pragmatically by
iteratively and incrementally
introducing structure,
governance, and metrics and
maturing practices and culture
over time
68. 11/4/2014
66
Theory of Transformation
Tr e agilit comes bTrue agility comes by
breaking dependencies
between teams across the
organization
Theory of Transformation
Health c lt re and solidHealthy culture and solid
practices emerge within a
rational delivery framework
69. 11/4/2014
67
Corollary One:
Sol ing for the iss es that getSolving for the issues that get
in the way of effectively
practicing agile is what should
guide your agile
transformation initiative
Corollary Two:
Agile can mean differentAgile can mean different
things to different companies
and not all agile approaches
will work well for every
organization
70. 11/4/2014
68
Corollary Three:
Organi ational change can beOrganizational change can be
mapped out in such a way
that outcomes are
measureable and predictable
and economically justified
Corollary Four:
Organi ational constr ctsOrganizational constructs,
governance models, metrics
and controls can be
established without violating
the principles of agile
71. 11/4/2014
69
Corollary Five:
Organi ations can adopt agileOrganizations can adopt agile
safely and pragmatically by
iteratively and incrementally
introducing structure,
governance, and metrics and
maturing practices and culture
over time
Summary
B foc sing on the f ndamentalsBy focusing on the fundamentals
of agile delivery, while
systematically and methodically
breaking dependencies, we can
achieve true enterprise agility