The document discusses how to effectively manage the role of a product owner for large, complex products developed by multiple teams. It describes how the product owner role expands beyond a single person to encompass business analysis, engineering, and leadership capabilities across teams, projects, and the overall product portfolio. Different expressions of product ownership are explored, including scrum of scrums, product owner teams, integration teams, and lean/kanban approaches.
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.
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.
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!
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.
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.
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!
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.
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.
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
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.
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.
10 Safe Essential Elements to Achieve the Benefits of SAFeCprime
This presentation explores what could happen as the Agile Release Train progresses with each later Program Increment. You will learn how to keep the train on the tracks with 10 essentials of SAFe, so you can achieve the full benefits of SAFe.
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.
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.
The Agile Enterprise: The Role of Leadership & Organization Health in Scaling...Cprime
The Agile Enterprise is nimble and robust. Responsive to an ever-changing, high-speed marketplace, it anticipates customer needs and wants. Its capacity for innovation delights customers and employees alike. Implementing agile for software development is vital and not enough for full-scale agility. At scale, a company needs to be agile-informed in its purpose, structure, processes and culture. This allows it to use business agility—a shared understanding that generates a new way of thinking, working and delivering value—as a competitive advantage. The organizational health essential to enterprise agility occurs by intentional design: a top-down commitment to embody transformational leadership. In this webinar, you’ll learn:
· The two key, complementary value cycles that constitute Enterprise Agility
· Why the Agile Enterprise depends on Transformational Leadership
· The four organizational disciplines of the Agile Enterprise
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 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.
Learn how we saved 76% to 81% of our event costs by using virtual worlds, and how they can be used to do agile project management with distributed teams. Presented at the Agile2010 conference in Orlando.
Agile is often traditionally associated as being exclusively applicable to the field of software development. However, non-software development projects can take ownership and use agile values, principles and practices to great effect. In this session, I will offer some approaches, techniques and examples for introducing agile into parts of the organisation that traditionally may not have considered it such as central services like finance, HR, marketing, traditional business areas as well as other areas of IT like infrastructure and provide some real-life examples along the way.
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.
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.
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
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.
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.
10 Safe Essential Elements to Achieve the Benefits of SAFeCprime
This presentation explores what could happen as the Agile Release Train progresses with each later Program Increment. You will learn how to keep the train on the tracks with 10 essentials of SAFe, so you can achieve the full benefits of SAFe.
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.
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.
The Agile Enterprise: The Role of Leadership & Organization Health in Scaling...Cprime
The Agile Enterprise is nimble and robust. Responsive to an ever-changing, high-speed marketplace, it anticipates customer needs and wants. Its capacity for innovation delights customers and employees alike. Implementing agile for software development is vital and not enough for full-scale agility. At scale, a company needs to be agile-informed in its purpose, structure, processes and culture. This allows it to use business agility—a shared understanding that generates a new way of thinking, working and delivering value—as a competitive advantage. The organizational health essential to enterprise agility occurs by intentional design: a top-down commitment to embody transformational leadership. In this webinar, you’ll learn:
· The two key, complementary value cycles that constitute Enterprise Agility
· Why the Agile Enterprise depends on Transformational Leadership
· The four organizational disciplines of the Agile Enterprise
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 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.
Learn how we saved 76% to 81% of our event costs by using virtual worlds, and how they can be used to do agile project management with distributed teams. Presented at the Agile2010 conference in Orlando.
Agile is often traditionally associated as being exclusively applicable to the field of software development. However, non-software development projects can take ownership and use agile values, principles and practices to great effect. In this session, I will offer some approaches, techniques and examples for introducing agile into parts of the organisation that traditionally may not have considered it such as central services like finance, HR, marketing, traditional business areas as well as other areas of IT like infrastructure and provide some real-life examples along the way.
Seeing Constraints, Kanban Explained by Jon StahlLeanDog
I am passionate about kanban because without a lot of ceremony and time, I can get a team to self organize and communicating at a whole new level. Since constraints become visible, it allows people to be more willing to go out of their comfort zone and thus wear any hat that it takes to produce quality software. Seeing constraints, pulling value and eliminating waste is the goal of practicing kanban. This would be a "kanban explained" session for those who are not familiar with this practice. I use physical boards to illustrate the concepts and encourage good dialogue. We will discuss several types of kanban boards such as WIP, backlog and retrospectives.
This presentation has been tested at many user group meetings, at clients and conferences such as Agile 2009 & CodeMash 2010. The session takes 1 hour to present, 1 1/2 hours to have good dialogue during the presentation.
Kanban, while not a new concept, nor complex - it is often misunderstood by those who don't practice it. Intended audience is for people that understand agile story wall concepts and whole team. The best audience is a Scrum master who will learn how kanban can take their craft to the next level of a self organizing teams by seeing, not hearing about constraints.
In order to foster trust and credibility between a project team and its stakeholders, the team has the responsibility to clearly communicate the health of the project. As the leaders of a project, we can apply the metaphor of medical care and their use of "vital signs" to help form a holistic view of the state of the project. Come learn the five "Project Vital Signs", their associated quantitative metrics and how to enable a team to effectively use them as a tool to diagnose and treat project health problems.
Building an A-Team - I Love It When a Team Comes TogetherCraig Smith
Craig Smith presentation from Agile Australia 2010. High performing teams are something that all organisations aspire to, but how exactly do you turn a team from good to great? There is much discussion in the community about management versus leadership, working in a factory versus embracing a tribe and how to motivate a new generation of employees. In this presentation we will look at these topics and determine what makes a high performing team, how Agile techniques can help, what tools and techniques you can use to create this environment and how you can measure performance.
This presentation was given at the Agile Australia 2011 (http://www.agileaustralia.com/)
Startup businesses face significant risk in the search for a sustainable, profitable and scalable business model. Consequently, the success rate for Startups is low, making them a typically high risk investment. Agile methods offer a way of reducing the risk for both the technical implementation and the development of customers. This is achieved by increasing the ability for a Startup to adapt to change and to incorporate the lessons learned from early customer engagement. In this presentation the nature of technology Startups is examined and the application of Agile principles, practices and tools discussed.
This is the version of the talk that I did at Agilepalooza Charlotte and Agile 2009. I will be doing this talk at the PMI Global Congress and Agile Dev Practices in the next few months.
Kaizen With GreenHopper: Visualising Agile & Kanban StorywallsCraig Smith
Best practices and lessons learned from a real-world software development team. Suncorp adopted a Kanban-based lean software development approach using JIRA, Greenhopper and other Atlassian tools.
Key Takeaways:
* Overview of agile software techniques
* How Kanban can be applied to software development, maintenance and support
* How to ensure kaizen (improvement) is part of your dev process.
Making decision in the presence of uncertainty requires estimating the impact of the outcome of those decisions. Here;s a collection of resources can can be used to guide that process
Creating a delightful user experience (UX) is becoming an increasingly important success factor for many digital products, and Scrum is the most popular agile method to build software products. But integrating the UX work with Scrum can be tricky: Scrum provides no guidance on which UX artefacts should be used, when they are created, who creates them and how they fit into the product backlog. This slide deck helps you understand how you can successfully combine UX and Scrum to create software products with a great user experience.
Starting with an EIA–748–C compliant Earned Value Management System, integrating an Agile Software Development Lifecycle (Agile) is straightforward when there is a Bright Line between the Performance Measurement Baseline (PMB) and the Sprints and Tasks of the Agile Software Development Process.
Agilia Budapest - Driving Business Decisions with Pirate MetricsOri Bendet
One of the major problems of developing new products is the fact that we assume how our users will use it. We try to think like our users and anticipate what they will do. We usually trust our gut feelings rather than real data. We think, hence we know. In today’s world of constant change – we can’t allow ourselves any crucial mistakes or wrong assumptions as it will lead to abandonment of users. Users expect nothing less than perfect when interacting with new apps and will leave immediately if they don’t understand it or have a bad experience with it.
In this session, I’ll introduce the Pirate Metrics framework and how it can help you improve your product and create happy users.
New is Easy but Right is Hard: Hacking Product ManagementBernard Leong
Talk given on 15 Nov 2013, in Hackers & Painters (http://http://hackersandpainters.sg/), Singapore @ Blk 71.
Synopsis: A great product is a synthesis of technology and business thinking. How do we decide what goes into the product and determine the roadmap of the product? How do we establish the balance between the business and technology of the product? In this session, we discuss some interesting lessons learned on product management and why both business leaders and technologists don't get it.
Agile Agency Scrum: An Introduction to Flexible Project Management for Produc...Tim Hamilton
Scrum works because the product owner gets to drive. Discover the process of successful agile scrum for agencies, from methodology and project management, to timeline and budget.
Three Secrets of Agile Leadership: From Working Hard to Working SmartPeter Stevens
Updated Version. Keynote Talk at Agile Business Day 2020. Agility as a movement started with software developers uncovering better ways of doing what they do. Today that movement is driving even business leaders to rethink how they lead their organizations. What does it mean to "be" agile? How can agility be applied to leading organizations? Where do successful agile leaders start? Three stories, three secrets and three tips to apply agility for more impact in your life and work.
This deck describes the key learnings from a coaching engagement I did in early 2009 for VersionOne. . Might be called... how to do Scrum and deliver nothing ;-)
My presentation in the Conference Agile Spain 2014
This is an introduction of Scrum where you can find an awesome big picture with each event, artifact and roles involved to make Scrum works.
Simple and easy to remember.
Free Download Here: http://slidemart.net/probusiness-free-powerpoint-template/
This Free Powerpoint template is perfect for your company overview presentation. It is a really professionally crafted, using wide 16:9. So with this size it is perfect for wide screen. The layout and design style is flat, modern and minimalist with outline iconic style. Perfect for a technology or a creative company.
It consists of 10 slides : Cover, Introduction, Our Philosophy, Our Company Values, 2 Pages Portfolio Sample, 1 Project Detail, Comparative Diagram, 2 Pages Editable Chart.
Yes it is cool :) , the chart can be edited, you just edit the data source, and the chart will be automatically updated. To edit data, Right Click > Edit Data …
And of course you can edit, the picture, and text with your company information.
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.
A presentation covering various tools used throughout an agile development lifecycle including NUnit, FitNesse, TeamCity and others. This was given at the South Florida Code Camp in March 2010.
Similar to How to own a really big complex product v3 (20)
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.
Introduction to Agile Project Planning and Project ManagementMike Cottmeyer
Agile introduces a number of tools and techniques designed to help the team figure out how much software we can build for the time we have, and the amount of money our customer is willing to spend. This talk will introduce the fundamental concepts necessary to break down and estimate our product backlog, how to organize delivery of that backlog for early risk reduction and rapid customer feedback, and how to get stable throughput and predictability as you mature your agile practices. This talk is for those looking to understand how (and why) agile methods lead to better business outcomes.
The Agile PMP: Teaching An Old Dog New Tricks (90 minutes)Mike Cottmeyer
This is a 90 minute presentation that helps traditional project managers understand how and why software project management breaks down and how agile can help deal with uncertainty.
1. How to Own a Really Big Complex Product Presented by: Mike Cottmeyer
2. Mike CottmeyerEnterprise Agile Coachmike@cottmeyer.com404.312.1471leadingagile.comfacebook.com/leadingagiletwitter.com/mcottmeyerlinkedin.com/in/cottmeyer
33. Product Owner is a BIG Job! Product Manager… vision and direction
34. Product Owner is a BIG Job! Product Manager… vision and direction Project Manager… sequence and status
35. Product Owner is a BIG Job! Product Manager… vision and direction Project Manager… sequence and status Business Analyst… elaborating requirements
36. Product Owner is a BIG Job! Product Manager… vision and direction Project Manager… sequence and status Business Analyst… elaborating requirements Quality Assurance… inspecting outcomes
37. Product Owner is a BIG Job! Product Manager… vision and direction Project Manager… sequence and status Business Analyst… elaborating requirements Quality Assurance… inspecting outcomes Management… terminating and changing
38. Product Owner is a BIG Job! Product Manager… vision and direction Project Manager… sequence and status Business Analyst… elaborating requirements Quality Assurance… inspecting outcomes Management… terminating and changing User Experience… usability
39. Product Owner is a BIG Job! Product Manager… vision and direction Project Manager… sequence and status Business Analyst… elaborating requirements Quality Assurance… inspecting outcomes Management… terminating and changing User Experience… usability Team Member… participates with the team
45. Owning a Complex Product Biller Transactions Fin Inst. Transactions Credit Card Payments ACH Payments Fraud/Risk Identity/ Enrollment SAS SAP Corporate Billing Web IVR Payments Risk Business Intelligence Corporate Financials Partner Communication Bus Intel/ Reporting
52. Biller Transactions Fin Inst. Transactions Credit Card Payments ACH Payments Fraud/Risk Identity/ Enrollment SAS SAP Corporate Billing Web IVR Payments Risk Business Intelligence Corporate Financials Partner Communication Bus Intel/ Reporting
53. Biller Transactions Fin Inst. Transactions Credit Card Payments ACH Payments Fraud/Risk Identity/ Enrollment SAS SAP Corporate Billing Web IVR Payments Risk Business Intelligence Corporate Financials Partner Communication Bus Intel/ Reporting
54. Biller Transactions Fin Inst. Transactions Credit Card Payments ACH Payments Fraud/Risk Identity/ Enrollment SAS SAP Corporate Billing Web IVR Payments Risk Business Intelligence Corporate Financials Partner Communication Bus Intel/ Reporting
55. Biller Transactions Fin Inst. Transactions Credit Card Payments ACH Payments Fraud/Risk Identity/ Enrollment SAS SAP Corporate Billing Web IVR Payments Risk Business Intelligence Corporate Financials Partner Communication Bus Intel/ Reporting
56. Biller Transactions Fin Inst. Transactions Credit Card Payments ACH Payments Fraud/Risk Identity/ Enrollment SAS SAP Corporate Billing Web IVR Payments Risk Business Intelligence Corporate Financials Partner Communication Bus Intel/ Reporting
57. Biller Transactions Fin Inst. Transactions Credit Card Payments ACH Payments Fraud/Risk Identity/ Enrollment SAS SAP Corporate Billing Web IVR Payments Risk Business Intelligence Corporate Financials Partner Communication Bus Intel/ Reporting
61. Team 1 User Story Feature Epic User Story Feature User Story Team 2 Feature User Story Feature Epic User Story User Story Feature Epic User Story Feature Team 3 User Story User Story Epic User Story
97. Product Owner Capabilities Agile as Business Analysis Agile as Engineering Agile as Leadership & Coordination
98. Business Analysis CapabilitiesHelping organizations develop the capabilities to achieve Enterprise Agility Product Development Product Strategy Solution Requirements Develop Product Launch Product Operate and Support Product Understand Needs of the Customer Establish Product Vision Plan Launch Establish Development Environment Support Operations Understand Requirements Develop Product Strategy Define Product Roadmap Coordinate Launch Provide Customer Support Maintain Architecture Integration Testing Manage Product Portfolio Define Business Requirements Support Implementation Coordinate Work Achieve Customer Acceptance Perform Maintenance and Customizations Define Product Backlog Design and Engineer Solution Deploy Product Environment Planning Manage Suppliers Maintain Product Quality Maintain Work Environment Learn from Outside Sources Develop Team Commit To Agility Everyone Engage Stakeholders Ensure Process Adherence Identify and Remove Impediments Ensure Internal Communication Manage Risks Provide Job Training
99. Engineering CapabilitiesHelping organizations develop the capabilities to achieve Enterprise Agility Product Development Product Strategy Solution Requirements Develop Product Launch Product Operate and Support Product Understand Needs of the Customer Establish Product Vision Plan Launch Establish Development Environment Support Operations Understand Requirements Develop Product Strategy Define Product Roadmap Coordinate Launch Provide Customer Support Maintain Architecture Integration Testing Manage Product Portfolio Define Business Requirements Support Implementation Coordinate Work Achieve Customer Acceptance Perform Maintenance and Customizations Define Product Backlog Design and Engineer Solution Deploy Product Environment Planning Manage Suppliers Maintain Product Quality Maintain Work Environment Learn from Outside Sources Develop Team Commit To Agility Everyone Engage Stakeholders Ensure Process Adherence Identify and Remove Impediments Ensure Internal Communication Manage Risks Provide Job Training
100. Leadership & Coordination CapabilitiesHelping organizations develop the capabilities to achieve Enterprise Agility Product Development Product Strategy Solution Requirements Develop Product Launch Product Operate and Support Product Understand Needs of the Customer Establish Product Vision Plan Launch Establish Development Environment Support Operations Understand Requirements Develop Product Strategy Define Product Roadmap Coordinate Launch Provide Customer Support Maintain Architecture Integration Testing Manage Product Portfolio Define Business Requirements Support Implementation Coordinate Work Achieve Customer Acceptance Perform Maintenance and Customizations Define Product Backlog Design and Engineer Solution Deploy Product Environment Planning Manage Suppliers Maintain Product Quality Maintain Work Environment Learn from Outside Sources Develop Team Commit To Agility Everyone Engage Stakeholders Ensure Process Adherence Identify and Remove Impediments Ensure Internal Communication Manage Risks Provide Job Training
115. Summary Product Owners don’t scale Common strategies don’t work It takes more than one team to deliver value
116. Summary Product Owners don’t scale Common strategies don’t work It takes more than one team to deliver value By thinking about organizational capabilities
117. Summary Product Owners don’t scale Common strategies don’t work It takes more than one team to deliver value By thinking about organizational capabilities We can create situationally specific strategies
118. Mike CottmeyerEnterprise Agile Coachmike@cottmeyer.com404.312.1471leadingagile.comfacebook.com/leadingagiletwitter.com/mcottmeyerlinkedin.com/in/cottmeyer
119. How to Own a Really Big Complex Product Presented by: Mike Cottmeyer
Editor's Notes
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
So here is our small agile team.
Agile teams are cross functional units that have everything they need to deliver some increment of business value. In a software organization… the agile team is going to have one or more developers…
They will have one or more QA testers. Sometimes teams have technical testers that are responsible for writing unit tests… sometimes this is left up to the developers. Sometimes teams have manual testers… possibly exercising the UI. Many teams will do both kinds of testing.
Sometimes a team will someone playing the role of business analyst. This can be a dedicated position on the team… or it might be blended with some other role… maybe a lead developer. Often times teams will have a BA that is serving as a proxy product owner for the real customer or product owner. Dedicated or blended Custome proxy
Small agile teams don’t typically have or need a project manager. I believe that there is a place for project management on an agile teams… but often project managers are coordinating the activities of several teams and doing some higher level planning activities and providing.
Agile teams will usually have someone in the role of ScrumMaster or Agile process coordinator. This can be a dedicated position on the team or a role that is shared with another role on the team. Sometimes you have a dedicated ScrumMaster but they are working with more than one agile team at a time.
Last but not least we have a product owner. They are the interface between the team and the business. They are the single wringable neck and responsible for the business outcomes of the product. They define requirements, set the priorties, and othewise help the team converge on the best possible outcome to meet the business objectives. Agile teams have all these roles in some form or fashion… they are self contained and independent. This kind of team is the backdrop to almost everything you read about adopting agile. This is such an important concept because if this isn't’ the kind of team you are building as you adopt agile… some of the things you are learning about just aren’t going to work.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
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.
12. Our goal is to recognize, that on projects where we have a tremendous amount of uncertainty... we don't want to create plans that don't reflect our current understanding of reality. We don't want to assume the process overhead of change management, when change is going to be the norm. Agile gives us a way to manage our projects, in the face of uncertainty, while aggressively working to reduce risk and uncertainty.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
Setup:Get blue tapeCreate a backlog sheetTape up cardsCreate a story boardCreate 4 sprint boardsCreate an impediments boardCreate a parking lot boardCreate a Birthday card