The document discusses why agile approaches often fail in large enterprises and provides recommendations for successful agile transformation. It notes that agile fails at scale due to lack of clarity, accountability, measurable progress, structure, governance and tools. It recommends starting the transformation by defining a rational delivery system for the enterprise to improve predictability. True agility comes from breaking dependencies between teams. An incremental approach using pilots, phases and iterations is suggested. Structure, governance, and metrics are also important to support the transformation.
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.
Having the Correct Context for an Agile TransformationDerek Huether
3 years, 5 business units, 20 lines of business, and over 100 teams. With so many interactions, having the correct context for Agile was (and still is) key to an ongoing transformation. Remember, we're not all Spotify!
The Executives Step-by-Step Guide to Leading a Large-Scale Agile TransformationLeadingAgile
This talk explores a safe, pragmatic, and repeatable formula for leading change in large organizations. The Holy Grail for an executive is to tie dollars spent and activities performed, to internal improvement metrics and ultimately improved business performance. We’ll start by discussing the elements of an agile transformation business case and how to identify a meaningful value proposition for change. Next we’ll consider how to assess the organization and build an agile transformation strategy and roadmap that encourages an iterative and incremental approach to change. Finally we’ll explore the metrics and controls that help you know if you’re on the right track. Throughout the presentation, we’ll explore the change management and engagement techniques necessary to make sure you are building meaningful organizational support as you engage the enterprise. We’ll discuss how to build and execute a change management strategy to keep everyone safe and informed throughout the transformation. We’ll show how to sustain and improve the changes over time, ultimately creating an organizational ecosystem where business agility is part of the fundamental DNA of the company. The goal of this talk is to take the magic out of agile transformation and show you how to systematically and planfully introduce agile into your organization.
Why agile is failing in large enterprisesLeadingAgile
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.
Check out Mike giving this talk live https://www.leadingagile.com/why-agile-fails
This is the talk I am doing at the 2010 SQE Better Software/Agile Development Practices Conference in Vegas this week. Not much new, but this is a combination of several ideas from many of my existing presentations.
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.
Having the Correct Context for an Agile TransformationDerek Huether
3 years, 5 business units, 20 lines of business, and over 100 teams. With so many interactions, having the correct context for Agile was (and still is) key to an ongoing transformation. Remember, we're not all Spotify!
The Executives Step-by-Step Guide to Leading a Large-Scale Agile TransformationLeadingAgile
This talk explores a safe, pragmatic, and repeatable formula for leading change in large organizations. The Holy Grail for an executive is to tie dollars spent and activities performed, to internal improvement metrics and ultimately improved business performance. We’ll start by discussing the elements of an agile transformation business case and how to identify a meaningful value proposition for change. Next we’ll consider how to assess the organization and build an agile transformation strategy and roadmap that encourages an iterative and incremental approach to change. Finally we’ll explore the metrics and controls that help you know if you’re on the right track. Throughout the presentation, we’ll explore the change management and engagement techniques necessary to make sure you are building meaningful organizational support as you engage the enterprise. We’ll discuss how to build and execute a change management strategy to keep everyone safe and informed throughout the transformation. We’ll show how to sustain and improve the changes over time, ultimately creating an organizational ecosystem where business agility is part of the fundamental DNA of the company. The goal of this talk is to take the magic out of agile transformation and show you how to systematically and planfully introduce agile into your organization.
Why agile is failing in large enterprisesLeadingAgile
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.
Check out Mike giving this talk live https://www.leadingagile.com/why-agile-fails
This is the talk I am doing at the 2010 SQE Better Software/Agile Development Practices Conference in Vegas this week. Not much new, but this is a combination of several ideas from many of my existing presentations.
Agile Product Management: Getting from Backlog to ValueLeadingAgile
What does it take to create a backlog, build software, release features, and finally deliver value to your customers? From estimation to prioritization, to understanding an end-state vision of an organization, this deck helps you understand the value you're delivering to your users. Learn more about the principles of Agile Product Management in this slide deck from LeadingAgile, Senior Vice President and Executive Consultant, Adam Asch.
So you are considering going agile, huh? Your biggest question is probably "where do I start"? This session will help you answer that question and get you started down the road to agility . Mike will explore how to choose your first project and ensure that the pilot team is setup for success. He will talk through common organizational challenges and show you how to overcome them. You'll leave this talk with the knowledge necessary to get your first team going while laying the foundation to build on that success.
Why Agile is Failing in Large EnterprisesLeadingAgile
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.
Agile IT Operatinos - Getting to Daily ReleasesLeadingAgile
Getting to Daily Releases with Agile IT Operations. Devin Hedge, Enterprise Transformation Consultant talks to a group at Triagile about the Six Key Areas to focus on when attempting to transform IT Operations with Lean and Agile principles. The talk covers Service Engineering, IT Operations, and the Tier 1 Support/NOC organizations. Kanban, Service Management (ITSM), and what it means to have a DevOps orientation.
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. Join @Mike Cottmeyer live from #Agile2017 during this workshop.
Why Agile Is Failing in Large Enterprises, And What You Can Do About ItMike Cottmeyer
Large companies often struggle to adopt agile practices in a meaningful way. This presentation will help you understand why you are struggling to adopt agile, and more importantly, what you can do about it.
Gaining agility is different than "doing agile", particularly at scale. This session will start with how agility makes a difference for the business and for the teams adopting it. We will look at the business structures that are needed for agility to thrive, how teams are organized and the new measures that will redefine success. With agility, one size does not fit all, but there are proven solutions, and this session will look at success stories as well as the dead-ends every organization wants to avoid.
Showcase Webinar: Mapping Business Outcomes to SAFe with Mike HallAgile Velocity
Are you considering SAFe (Scaled Agile Framework)? Have you begun your SAFe implementation but are not seeing the promised business results? This webinar discusses how to ensure your desired business outcomes are achieved using SAFe. It explains the missing “connective tissue” that ties your business objectives to the underlying framework.
Mike Hall is an experienced Agile Coach specializing in scaling Agile and lean economics. He has led several large SAFe transformations and is an experienced SAFe trainer.
This guide summaries a successful Agile transformation in Telco with a related case study.
Do not take the described steps of this guide as the only way to be successful, there can be many other alternatives for sure. However, this guide explains a way thats experienced to be successful in many companies and under different circumstances.
Looking forward to hear your comments & suggestions
Thanks
Successful Agile Transformation - The NCS StoryNUS-ISS
Presented by Mr Lee Chee Yong, Agile Practice Lead of NCS Agile Competency Centre at ISS Seminar - Agile Software Development: Swift and the Shift on 18 July 2014.
Webinar: 3 Lessons Learned Guiding SAFe® Implementations with Mike Hall | Agi...Agile Velocity
Planning and executing an Agile scaling strategy is difficult. During my time as an Agile Coach, I’ve guided enterprises through successful Scaled Agile Framework® (SAFe®) implementation--but it wasn’t all daffodils and roses.
View the webinar recording here: https://agilevelocity.com/webinar/upcoming-webinar-3-lessons-learned-guiding-safe-implementations/
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."
Agile Product Management: Getting from Backlog to ValueLeadingAgile
What does it take to create a backlog, build software, release features, and finally deliver value to your customers? From estimation to prioritization, to understanding an end-state vision of an organization, this deck helps you understand the value you're delivering to your users. Learn more about the principles of Agile Product Management in this slide deck from LeadingAgile, Senior Vice President and Executive Consultant, Adam Asch.
So you are considering going agile, huh? Your biggest question is probably "where do I start"? This session will help you answer that question and get you started down the road to agility . Mike will explore how to choose your first project and ensure that the pilot team is setup for success. He will talk through common organizational challenges and show you how to overcome them. You'll leave this talk with the knowledge necessary to get your first team going while laying the foundation to build on that success.
Why Agile is Failing in Large EnterprisesLeadingAgile
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.
Agile IT Operatinos - Getting to Daily ReleasesLeadingAgile
Getting to Daily Releases with Agile IT Operations. Devin Hedge, Enterprise Transformation Consultant talks to a group at Triagile about the Six Key Areas to focus on when attempting to transform IT Operations with Lean and Agile principles. The talk covers Service Engineering, IT Operations, and the Tier 1 Support/NOC organizations. Kanban, Service Management (ITSM), and what it means to have a DevOps orientation.
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. Join @Mike Cottmeyer live from #Agile2017 during this workshop.
Why Agile Is Failing in Large Enterprises, And What You Can Do About ItMike Cottmeyer
Large companies often struggle to adopt agile practices in a meaningful way. This presentation will help you understand why you are struggling to adopt agile, and more importantly, what you can do about it.
Gaining agility is different than "doing agile", particularly at scale. This session will start with how agility makes a difference for the business and for the teams adopting it. We will look at the business structures that are needed for agility to thrive, how teams are organized and the new measures that will redefine success. With agility, one size does not fit all, but there are proven solutions, and this session will look at success stories as well as the dead-ends every organization wants to avoid.
Showcase Webinar: Mapping Business Outcomes to SAFe with Mike HallAgile Velocity
Are you considering SAFe (Scaled Agile Framework)? Have you begun your SAFe implementation but are not seeing the promised business results? This webinar discusses how to ensure your desired business outcomes are achieved using SAFe. It explains the missing “connective tissue” that ties your business objectives to the underlying framework.
Mike Hall is an experienced Agile Coach specializing in scaling Agile and lean economics. He has led several large SAFe transformations and is an experienced SAFe trainer.
This guide summaries a successful Agile transformation in Telco with a related case study.
Do not take the described steps of this guide as the only way to be successful, there can be many other alternatives for sure. However, this guide explains a way thats experienced to be successful in many companies and under different circumstances.
Looking forward to hear your comments & suggestions
Thanks
Successful Agile Transformation - The NCS StoryNUS-ISS
Presented by Mr Lee Chee Yong, Agile Practice Lead of NCS Agile Competency Centre at ISS Seminar - Agile Software Development: Swift and the Shift on 18 July 2014.
Webinar: 3 Lessons Learned Guiding SAFe® Implementations with Mike Hall | Agi...Agile Velocity
Planning and executing an Agile scaling strategy is difficult. During my time as an Agile Coach, I’ve guided enterprises through successful Scaled Agile Framework® (SAFe®) implementation--but it wasn’t all daffodils and roses.
View the webinar recording here: https://agilevelocity.com/webinar/upcoming-webinar-3-lessons-learned-guiding-safe-implementations/
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."
Collaboration Through Conflict - SFAA 2013Mark Kilby
Session at South FL's first agile conference where we talked about the 5 sources of conflict and various tools to help your team navigate it for better collaboration
European University Barcelona Campus: Beyond Budgeting – A (Secret) Performan...Fabiola Eyholzer
Barcelona, Spain | Mar-12-2015
Forbes Magazine calls Agile “The Best Kept Secret in Management” and industry leaders and key players across all industries are already embracing lean | agile – a leadership philosophy with a set of tools and techniques based on specific values and principles – with the goal of making their organizations more responsive, innovative, and engaging.
Besides applying a toolset instrumental for driving innovation, reducing time-to-market, and improving customer satisfaction, companies are revising and realigning their leadership approach in order to ensure not only precise, but also fast and flexible decisions, swift accomplishments, and valuable interactions. This will alter their approach towards providing, managing, and monitoring their initiatives and resources and help them meet the demands of a constantly and rapidly changing business environment. Lean | agile provides them with an unparalleled competitive advantage that will impact their bottom line in a positive and sustainable manner.
This presentation focuses on the characteristics of Lean | Agile enterprises and how they approach financial planning and investment approaches in a more flexible way. We talk about “Beyond Budgeting” (also known as “Beta-Complex”) that eliminate traditional budget and budget reporting and discuss their validity and impact.
Agile HR: Transforming a Human Resources Team Using ScrumSeedbox
At Seedbox Technologies, we use agile development and scrum in all our engineering teams and have the vision of becoming a fully agile company one day. To support this vision, some of our non-engineering teams are starting to adopt and adapt agile principles that will help them deliver more value for our customers, partners, and team members. Here is a kickoff presentation we created to start this transformation with one of our HR teams, responsible for driving our company culture projects. We hope this can inspire other technology (and non-tech) companies to make a similar change in their organizations.
How much does one story point cost? Is Sprint 0 an expense or an asset? Can you run Scrum with a fixed-cost contract? Agile challenges the existing approach to financial aspects of running projects: i.e. budgeting, forecasting, financial planning and vendor contracts.
Applying new financial models becomes increasingly important for larger organizations adopting Agile. While they are going through an Agile transformation, they also need to maintain transparent financial governance and reporting. Shareholders would not be too excited about messy Annual Financial Statements.
Building the Agile Enterprise: A New Model for HRJosh Bersin
Josh Bersin's IMPACT 2012 Keynote Speech ... "The Agile Enterprise" - how HR must rapidly evolve through changes in strategy, learning, leadership, and technology to adapt to today's agile management model. Detailed notes available from Bersin & Associates.
3 Things Every Sales Team Needs to Be Thinking About in 2017Drift
Thinking about your sales team's goals for 2017? Drift's VP of Sales shares 3 things you can do to improve conversion rates and drive more revenue.
Read the full story on the Drift blog here: http://blog.drift.com/sales-team-tips
How to Become a Thought Leader in Your NicheLeslie Samuel
Are bloggers thought leaders? Here are some tips on how you can become one. Provide great value, put awesome content out there on a regular basis, and help others.
Why Agile Fails in Large Enterprises—and What to Do about ItTechWell
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.
How to Successfully Scale Agile in Your EnterpriseIsaac Hogue
In an enterprise environment that is not structured to adopt out-of-the-box Agile, it’s critical to adopt Agile to your enterprises business drivers, value structure and governance. While Agile methodologies can improve the predictability, quality, and time to market of your software delivery, they are not a silver bullet.
Creating a pull for DevOps in an Agile TransformationTimothy Wise
This presentation was used to start a conversation with the Atlanta DevOps community around patterns for introducing DevOps in large organizations. During the session, I presented findings from coaches around the US.
This presentation gives you an introduction on practices and habits associated with DevOps while sharing personal experience on starting a DevOps journey inside a large project team.
Why Agile Fails in Large Enterprises—and What to Do about ItTechWell
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.
Performance through agility generic v2.2 seminarRobert Twiddy
Agility Way provides training and coaching services in Performance Through Agility. This presentation fro a seminar that took place in Bangkok in September 2018
How to scale agility in your enterpriseTimothy Wise
Presentation for Southern Fried Agile conference 10/23/2014 that outlines how to scale agility in an enterprise.
The conference is a one day'er in Raleigh NC.
Great Crowd :)
'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.
[DEISER Day Conferences] "DevOps & Teams" - Vlad Cavalcanti (Atlassian)Deiser
"DevOps & Teams: The secret sauce of successful teams."
La misma Atlassian envió un representante al DEISER Enterprise Day Madrid 2017, quien se tomó el tiempo de explicarle a los asistentes cómo trabajan los equipos funcionales, con el ejemplo de la firma de sofware australiana.
Asiste al DEISER Enterprise Madrid 2018, el próximo 14 y 15 de noviembre; suscríbete al newsletter oficial para obtener toda la información que buscas - https://deiser-enterprise-day.deiser.com/
-------------------------------------------------------------------------------------
Twitter.com/deiser
Facebook.com/deiserteam
LinkedIn.com/company/deiserteam
Instagram.com/deiserteam
blog.deiser.com
www.deiser.com
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.
Building on the Shoulders of Giants: the Story of Bitbucket PipelinesAtlassian
When the Atlassian Dev Tools team looked to innovate on continuous integration and delivery, we explored many ways to bring the build and deployment pipeline closer to developers and Bitbucket. This led us to think outside the existing product boundaries of Bamboo and build on top of the Bitbucket Connect platform.
James Bryant, a senior designer on the Software Team, will take you through how his team decided to build on top of a platform instead of building out new products. It involves defining a vision, guiding a team with an experience, and testing with customers early and often to build the new Bitbucket Pipelines feature.
You’ll come away from this session with a framework for adopting an experience-driven strategy, and tips to help give your agile teams a vision to build on top of a platform.
Products covered:
Bitbucket, Bamboo
How (can) Scrum and DevOps Walk Together to Build a High-Quality Product Deli...Scrum Day Bandung
Discussion in fishbowl format to find out how Scrum and DevOps should more power-full if we use it together and properly, then validating with data and convergence of CEO Scrum.org and CEO DevOps Institute.
Maximize IT Operations Observability With IBM i In SplunkPrecisely
Splunk’s powerful IT operations analytics platform helps you optimize the performance and availability of IT systems and applications, while controlling IT costs and resources. However, IBM i systems have been left out of most Splunk environments because the machine data they generate is unique and requires specialized skills to work with.
Ironstream collects and feeds IBM i log data to Splunk, ensuring a true 360-degree view of your IT landscape. Having this view into all your systems in one tool allows you to predict, prevent, and fix problems fast, all while optimizing your investment in these large systems.
Join this on-demand webinar to learn how customers turn IBM i log data into real-time insights with Ironstream for Splunk.
During this session you will see:
- Key customer use cases in IT Operations Analytics
- Challenges of integrating IBM i log data in Splunk and how to overcome them
- Demo of Ironstream for Splunk leveraging IBM i data sources
[Atlassian meets dev ops and itsm] itsm in an agile world atlassian scottOpen Source Consulting
[Atlassian meets dev ops and itsm] ITSM in an Agile World by atlassian
오픈소스컨설팅이 개최한 Atlassian meets DevOps and ITSM 세미나 발표자료를 공유합니다. Atlassian 본사의 솔루션 엔지니어인 'Scott'이 전하는 신속하게 변하는 IT팀을 위한 인력, 프로세스, 제품 전반에 걸친 Atlassian의 전략을 확인해 보세요.
Similar to Why Agile Is Failing in Large Enterprises, And What You Can Do About I... (20)
Aligning Your DevOps Strategy to Your Agile TransformationLeadingAgile
This is the deck used by our Chief Technology Officer, Matt Van Vleet, at 2021's Agile + DevOps West conference. This deck provides you with a visual to help you understand our Basecamp model, the Transformation Journey, and the DevOps practices you should apply at the different stages of Transformation.
The 10 Steps to Becoming a Great Agile CoachLeadingAgile
Recently, at TriAgile 2020, Mike Cottmeyer presented his talk on how to become a great Agile coach. In it, he goes into the four primary areas that make up a great coach, the hard skills you'll need to develop, and how those apply to particular coaching roles.
You can check out the talk here: https://hubs.ly/H0pGFRH0
So you want to become a great Agile coach?
Join us for the premier of Mike Cottmeyer's remote talk that he delivered at TriAgile 2020 and learn the 10 steps you can take to do exactly that.
Watch as Mike explores the four primary skill areas that make a great coach and the hard skills you'll need to develop, and learn how those translate to specific types of coaching roles.
The Journey to Transformation | Tech Company Case StudyLeadingAgile
Does any of this sound familiar?
Ad hoc delivery within a low trust environment.
Failing technical practices that lead to integration nightmares.
Multiple teams making things up as they go.
Shared common code with no communication amongst teams.
If so, you might want to check out this case study.
Learn how one company was able to leverage Agile to make and meet their commitments and begin expanding into new markets.
First check out the abbreviated version in this deck, then download the real thing here: https://hubs.ly/H0nhQHl0
Markets are changing faster than typical strategic planning cycles can support. Additionally, digital strategies are increasing interdependencies and exacerbating the strain on execution. Strategic planning often falls short because it’s not as fluid as it needs to be.
One thing we must consider is that there are—typically— a lot of assumptions being made about markets as well as the organization’s capacity to execute. Those assumptions often miss the mark when attempting to meet the ever-changing needs and expectations of shareholders and customers. Agile provides the opportunity to create the requisite adaptability to validate and adapt to as we understand our ability to deliver and the realizable value of our strategies.
This talk is targeted at senior managers seeking to understand how to leverage Agile to improve Strategic Execution. This talk will show how to build market sensing into strategic planning, how to design the execution model to provide valuable feedback, and how to prioritize learning to maximize return. The model has been developing over the years and has successfully responded to the assumptions and ambiguity facing firms. The reality is that it’s not that simple, but we have a model that can help.
Learning Outcomes:
• Understand how agile can enable strategy execution in rapidly evolving markets
• Quantify opportunities to accelerate learning to maximize business return
• Determine when and how to prioritize for learning over earning
Product-Driven Organizations: The Evolution of AgileLeadingAgile
Agile has been great. Revolutionary, even. Organizations are producing software faster, creating more cross-functional and collaborative teams than ever before. However, a lot of Agilists are experiencing diminishing returns on their investment to go Agile. Why is that?
The reality is that you've likely tapped the potential of your Agile practices and you've reaped all the benefits of the Agile culture that you've instilled already. The good news is that your journey doesn't have to end here.
The next evolution of Agile is to restructure the business, create a product-driven organization, and build a system of delivery that's conducive to getting more mileage out of your investment in Agile.
System of Delivery: An Intro to Our Governance ModelLeadingAgile
Our governance model and team design may look a little complicated at first glance. However, there's a lot of intentionality within our system of delivery to ensure that you're solving the right problems, at the right time, to maximize throughput and the value delivered to your customers.
In this video, our Chief Methodologist, Dennis Stevens will remove the noise and walk you through our governance model and team design to help you better understand the LeadingAgile system of delivery.
For more information on our approach to Transformation, check out our latest white paper:
www.leadingagile.com/whitepaper
If you're interested in helping other organizations achieve their Agility goals within a system such as this, check out our careers page:
www.leadingagile.com/careers
Rick Austin - Portfolio mangement in an agile world [Agile DC]LeadingAgile
When organizations move to agile for software delivery, there is often tension with traditional portfolio management. This talk will illustrate how an organization can move from traditional portfolio management approaches to one that embraces agile software delivery. Doing so enables organizations to become predictable, improve the flow of value delivered, and pivot more quickly if necessary.
We will demonstrate the use of governance that allows a more adaptive portfolio management approach. We will cover topics that enable agile portfolio management including:
Lean techniques for managing flow
Effective prioritization techniques
Long range road-mapping
Demand management and planning
Progressively elaborated business cases
Validation of outcomes
Support for audit and compliance needs
These topics will be illustrated by real-world examples of portfolio management that have been proven over the last five years with a wide range of clients.
Faster Food and a Better Place to Sleep: Exploring Agile in Non-IT DomainsLeadingAgile
Agile methods aren’t just for software anymore. Actually, they haven’t been just for software for quite a while now. That said, the types of companies, and the types of industries, that are exploring team-based, collaborative, iterative, and incremental approaches to do their work is rather breathtaking. Agile is truly going mainstream. The question at hand is can we apply team-based Agile straight out of the box in a non-software context? Can we take our scaled Agile approaches and apply them without modification? Mike Cottmeyer’s experience is that most of the principles and patterns apply, but sometimes the practices and frameworks need modification for a particular context.
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.
Information Radiators and Information VaultsLeadingAgile
Dave Nicolette discusses the tendency for novice teams to feel that maintaining information radiators in their team area represents duplicate effort on top of keeping their project management tool up to date. In reality, the two types of tools have quite different purposes. Let’s clarify the purpose of each and the differences between them.
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.
Enterprise Agile Metrics: A GQM ApproachLeadingAgile
Ever feel like you're doing metrics wrong? Well, you probably are! Join us and up your game by learning the GQM approach to Agile metrics.
In Agile, there is a need to collect data to demonstrate progress and show improvement, but where does one even start? Common Agile metrics approaches do well at measuring team velocity and throughput, but can sometimes overlook the requirements of executive sponsors, product management, and other key stakeholders. This problem is often rooted in a lack of understanding about what business goals are driving decision-making throughout the organization and what questions we should be answering with the metrics we collect.
The “Goal-Question-Metric” (GQM) approach is a proven method for driving goal-oriented measures throughout a software organization. With GQM, we start by defining the goals we are trying to achieve, then ask clarifying questions around those goals, and finally answer our questions through objective metrics. By mapping business outcomes and goals to specific measures, we can form a better picture of the Agile environment and clearly demonstrate how we are doing across the span of the enterprise.
During this session, we will explore the GQM approach and show its effectiveness in identifying the key information your enterprise needs to know at the Executive, Portfolio, Program, and Delivery tiers. We will provide sample metric sets for each tier and explain the goals and questions that drove us to them. At the end of this talk, the audience will understand not only how to ask the right questions, but specifically what metrics can be used to answer them.
Portfolio Management in an Agile World - Rick AustinLeadingAgile
When organizations move to agile for software delivery, there is often tension with traditional portfolio management. Rick Austin illustrates how an organization can move from traditional portfolio management approaches to one that embraces agile software delivery. Doing so enables organizations to become predictable, improve the flow of value delivered, and pivot more quickly if necessary.
Avoiding the Pitfalls of Capitalizing Software in an Agile WorldLeadingAgile
With the increased speed that CIOs and CTOs are moving their teams into agile environments, their financial brethren are running to catch up. Having been grounded in the days of waterfall methodologies, the financial side of the house is dealing with great uncertainty on how to account for software development costs. Questions include: Are all development costs now expensed because of the continual planning, developing and pivoting of software projects that occurs within agile? If development costs can be capitalized, what is the appropriate way to track these costs – through hours or something new altogether like story points?
We will explore how the historic accounting guidance that was developed specifically through the lens of waterfall methodologies remains applicable within agile methodologies. We will look at the alternative ways to amortize these capitalized development costs and evaluate the pros and cons of doing so. In addition to the financial reporting aspects of this presentation, we will also explore the benefits gained by moving from project-based funding to overall product–based funding and what key requirements must be in place to have that successful.
The goal of this presentation is to increase awareness among the audience that while making the decision to become agile is a business decision, this decision cannot be done in isolation. The business will eventually need the approval by their finance colleagues and if these financially grounded colleagues are not educated on the financial and accounting implications of moving to agile methodologies they may block such a move based on their misunderstandings alone. Getting everyone on the same page is a key success factor when moving to agile.
Faster Food and a Better Place to Sleep: Applying Agile Outside of SoftwareLeadingAgile
Agile methods aren’t just for software anymore. Actually they haven’t been just for software for quite a while now. That said, the types of companies, and the types of industries, that are exploring team-based, collaborative, iterative and incremental approaches to do their work is rather breath-taking. Agile is truly going mainstream. The question at hand is can we apply team-based agile straight out of the box in a non-software context? Can we take our scaled agile approaches and apply them without modification? Mike Cottmeyer will talk about his specific experiences with two companies, in different industries, both trying to use agile to solve their problems.
Agile Analytics: A GQM Approach to Enterprise MetricsLeadingAgile
When undertaking an Agile transformation, there is a need to collect data to demonstrate progress and show improvement, but where does one even start? Common Agile metrics approaches do well at measuring team velocity and throughput, but can sometimes overlook the requirements of executive sponsors, product management, and other key stakeholders. This problem is often rooted in a lack of understanding about what business goals are driving decision making throughout the organization and what questions we should be answering with the metrics we collect.
The “Goal-Question-Metric” (GQM) approach is a proven method for driving goal-oriented measures throughout a software organization. With GQM, we start by defining the goals we are trying to achieve, then clarifying the questions we are trying to answer with the data we collect. By mapping business outcomes and goals to data-driven metrics, we can form a holistic picture of the Agile environment and clearly articulate how we are doing across the span of the enterprise.
During this session, we will explore the GQM approach and show its effectiveness in identifying the key information your enterprise needs to know at the Executive, Portfolio, Program, and Delivery tiers. We will provide example metric sets for each tier and explain the goals and questions that drove us to them. At the end of this talk, the audience will understand not only how to ask the right questions, but specifically what metrics can be used to answer them.
Project Management to Enterprise Agile Product DeliveryLeadingAgile
This deck explores how Project Managers, Program Managers and Portfolio Managers fit into an Enterprise Agile setting. The slide deck was used during a presentation by VP & Principal Consultant, Greg King at a meetup with the Atlanta Scrum Users Group.
Product Owner Team: Leading Agile Program Management from Agile2015 by Dean S...LeadingAgile
This deck was used at the Agile Alliance Conference of the year Agile2015 in Washington, DC. The content was presented to a group of around 200 attendees by Enterprise Transformation Consultant, Dean Stevens.
AI Genie Review: World’s First Open AI WordPress Website CreatorGoogle
AI Genie Review: World’s First Open AI WordPress Website Creator
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-genie-review
AI Genie Review: Key Features
✅Creates Limitless Real-Time Unique Content, auto-publishing Posts, Pages & Images directly from Chat GPT & Open AI on WordPress in any Niche
✅First & Only Google Bard Approved Software That Publishes 100% Original, SEO Friendly Content using Open AI
✅Publish Automated Posts and Pages using AI Genie directly on Your website
✅50 DFY Websites Included Without Adding Any Images, Content Or Doing Anything Yourself
✅Integrated Chat GPT Bot gives Instant Answers on Your Website to Visitors
✅Just Enter the title, and your Content for Pages and Posts will be ready on your website
✅Automatically insert visually appealing images into posts based on keywords and titles.
✅Choose the temperature of the content and control its randomness.
✅Control the length of the content to be generated.
✅Never Worry About Paying Huge Money Monthly To Top Content Creation Platforms
✅100% Easy-to-Use, Newbie-Friendly Technology
✅30-Days Money-Back Guarantee
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIGenieApp #AIGenieBonus #AIGenieBonuses #AIGenieDemo #AIGenieDownload #AIGenieLegit #AIGenieLiveDemo #AIGenieOTO #AIGeniePreview #AIGenieReview #AIGenieReviewandBonus #AIGenieScamorLegit #AIGenieSoftware #AIGenieUpgrades #AIGenieUpsells #HowDoesAlGenie #HowtoBuyAIGenie #HowtoMakeMoneywithAIGenie #MakeMoneyOnline #MakeMoneywithAIGenie
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
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.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
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.
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...Mind IT Systems
Healthcare providers often struggle with the complexities of chronic conditions and remote patient monitoring, as each patient requires personalized care and ongoing monitoring. Off-the-shelf solutions may not meet these diverse needs, leading to inefficiencies and gaps in care. It’s here, custom healthcare software offers a tailored solution, ensuring improved care and effectiveness.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Looking for a reliable mobile app development company in Noida? Look no further than Drona Infotech. We specialize in creating customized apps for your business needs.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
31. Matrixed
Organizations
Limited Access
to Subject Matter
Expertise
Non-instantly
Available
Resources
Too Much Work
In Process
Shared
Requirements
Between Teams
Large Products
with Diverse
Technology
Team
32. Matrixed
Organizations
Limited Access
to Subject Matter
Expertise
Non-instantly
Available
Resources
Too Much Work
In Process
Shared
Requirements
Between Teams
Technical Debt &
Defects
Large Products
with Diverse
Technology
Team
33. Matrixed
Organizations
Limited Access
to Subject Matter
Expertise
Non-instantly
Available
Resources
Too Much Work
In Process
Low Cohesion &
Tight Coupling
Shared
Requirements
Between Teams
Technical Debt &
Defects
Large Products
with Diverse
Technology
Team
44. Culture
PracticesStructure
• Focused on changing
hearts and minds
• Focused on being agile
rather than doing agile
• Focused on values and
principles
• Belief that delivery
systems will emerge
based on new thinking
45. Practices
StructureCulture
• Focused on the things
that you do
• Focused on roles,
ceremonies, and artifacts
• Can be management
driven or technically
driven
46. Practices
StructureCulture
• Focused on the things
that you do
• Focused on roles,
ceremonies, and
artifacts
• Can be management
driven or technically
driven
• Belief that agile is a
process or way to work
48. Structure
CulturePractices
• Focused on forming
teams and governing the
flow of value
• Focused on aligning the
organization first
• Belief that culture and
practices only emerge
within a rational structural
and planning framework
81. Services Teams – These teams
support common services across
product lines. These teams support the
needs of the product teams.
Team
82. Product Teams – These teams
integrate services and write customer
facing features. This is the proto-
typical Scrum team.
Services Teams – These teams
support common services across
product lines. These teams support the
needs of the product teams.
Team
Team
83. 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.
Services Teams – These teams
support common services across
product lines. These teams support the
needs of the product teams.
Team
Team
Team
84. Portfolio Teams – These teams
govern the portfolio and make sure that
work is moving through the system.
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.
Services Teams – These teams
support common services across
product lines. These teams support the
needs of the product teams.
Team
Team
Team
Team
85. Team Team Team Team
TeamTeamTeam
Product &
Services
Teams
86. Team Team Team
Team Team Team Team
TeamTeamTeam
Product &
Services
Teams
Program
Teams
87. Team
Team Team Team
Team Team Team Team
TeamTeamTeam
Product &
Services
Teams
Program
Teams
Portfolio
Teams
115. Summary
By focusing on the fundamentals
of agile delivery, while
systematically and methodically
breaking dependencies, we can
achieve true enterprise agility
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
Matrixed management
Non-instantly available resources
Project funding models
Limited access to subject matter expertise
Shared requirements between teams
Technical debt
Defects
Tightly coupled architectures
Matrixed management
Non-instantly available resources
Project funding models
Limited access to subject matter expertise
Shared requirements between teams
Technical debt
Defects
Tightly coupled architectures
Matrixed management
Non-instantly available resources
Project funding models
Limited access to subject matter expertise
Shared requirements between teams
Technical debt
Defects
Tightly coupled architectures
Matrixed management
Non-instantly available resources
Project funding models
Limited access to subject matter expertise
Shared requirements between teams
Technical debt
Defects
Tightly coupled architectures
Matrixed management
Non-instantly available resources
Project funding models
Limited access to subject matter expertise
Shared requirements between teams
Technical debt
Defects
Tightly coupled architectures
Matrixed management
Non-instantly available resources
Project funding models
Limited access to subject matter expertise
Shared requirements between teams
Technical debt
Defects
Tightly coupled architectures
Matrixed management
Non-instantly available resources
Project funding models
Limited access to subject matter expertise
Shared requirements between teams
Technical debt
Defects
Tightly coupled architectures
Matrixed management
Non-instantly available resources
Project funding models
Limited access to subject matter expertise
Shared requirements between teams
Technical debt
Defects
Tightly coupled architectures
Matrixed management
Non-instantly available resources
Project funding models
Limited access to subject matter expertise
Shared requirements between teams
Technical debt
Defects
Tightly coupled architectures
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.
11. We start with high level requirements that become more detailed as we learn more about the product we are building. We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product. You might think of this as rolling wave planning or progressive elaboration. The idea is that we plan based on what we know, and plan more as we learn more.