This document discusses how to manage product ownership at scale for complex, multi-team products. It notes that product owners do not scale effectively and common strategies like assigning one product owner per team do not work. Instead, it advocates developing organizational capabilities for business analysis, engineering, and leadership/coordination. These capabilities can be expressed differently depending on the level of scale, such as through product owner teams, Scrum of Scrums, integration teams, and alignment of culture. The key is delivering value across multiple teams by thinking holistically about capabilities rather than focusing on individual roles.
I recently delivered a talk to product owners at Cisco. While I would normally cover this stuff over a period of two days, this was a 90 minute talk about some of the aspects of product ownership. None of this is my own creation - for I have learnt all this from the practitioner community, I am more than happy to share it with the community.
Note: If any attribution is missing, I will be happy to correct my mistake :)
Improve customer experience through operational transformation and investment...Devbridge Group
Highlights three areas that banks should focus on to improve customer experience, accelerate products to market amid rapid digitization and deescalate costs. Learn more at www.devbridge.com
The Devbridge Way: Lean Requirements, Rapid Prototyping, Dual-track Scrum and...Devbridge Group
On September 13, 2016, Devbridge Group hosted the Chicago Agile community to discuss Lean Requirements, Rapid Prototyping, Dual-track Scrum and Scrum at Scale. Professionals from Devbridge Group's Product Management Team shared their real-life experiences with these practices. For more on these topics, visit devbridge.com.
I recently delivered a talk to product owners at Cisco. While I would normally cover this stuff over a period of two days, this was a 90 minute talk about some of the aspects of product ownership. None of this is my own creation - for I have learnt all this from the practitioner community, I am more than happy to share it with the community.
Note: If any attribution is missing, I will be happy to correct my mistake :)
Improve customer experience through operational transformation and investment...Devbridge Group
Highlights three areas that banks should focus on to improve customer experience, accelerate products to market amid rapid digitization and deescalate costs. Learn more at www.devbridge.com
The Devbridge Way: Lean Requirements, Rapid Prototyping, Dual-track Scrum and...Devbridge Group
On September 13, 2016, Devbridge Group hosted the Chicago Agile community to discuss Lean Requirements, Rapid Prototyping, Dual-track Scrum and Scrum at Scale. Professionals from Devbridge Group's Product Management Team shared their real-life experiences with these practices. For more on these topics, visit devbridge.com.
The secret life of an Agile Business Analyst - Sydney Agile Meetup group - 13...Ryan McKergow
The Agile Business Analyst seems to be a bit of an unknown quantity to some people. Frameworks like Scrum and SAFe have no mention of the Business Analyst. Is it because they don't understand us? Is it because to outsiders we're living in secret? Andrew and Ryan will explain how the Agile Business Analyst is an essential role that is evolving as our the world around us is constantly change and becoming increasingly more complex. Our focus is shifting from just requirements to delivering value. Throughout this talk and discussion with the audience we will demystify the secret life of the Agile Business Analyst.
Agile has become mainstream in the IT industry, since that the multiplication of Agile practices which makes Agile implementation complex and uncertain, we have started to see failure in Agile implementations.
During this presentation we will start a simplification process by going back to the source of Agile, understand what Agile is and what it is not. We will discover what is the Heart of Agile, its essence, and how it embraces management.
Reference: Agile Manifesto, Heart of Agile blogs Alistair Cockburn, plus historical information about Agile mouvement
Agile ME Meetup: Agile A-Z - Chapter 1: AgileAgile ME
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organizations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
This Chapter (1/6): Agile
In this first chapter, we will have a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? We will cover the following topics:
• The Agile Manifesto and it's principles
• Agile Methodology vs. Mindset and Culture
• The value of Agile
• SCRUM
• Kanban
IxDA October Event: Prototyping Approaches and OutcomesIxDA Chicago
Prototyping is not a new concept, but the role it plays in the design process has changed dramatically in the last few years. Proliferation of agile methods and the grassroots nature of design thinking have opened up new opportunities where research and design happen simultaneously. New tools for building digital prototypes have given design teams numerous options from very simple demos to complex proof of concepts.
Learn about the Devbridge Design team's experience as they explore cases where prototyping has driven the design and research process. With varying levels of complexity and fidelity, each has had a different outcome.
Agile Anti-Patterns. Yes your agile projects can and will fail too.Sander Hoogendoorn
This is the slide deck for a smooth presentation on agile and agile anti-patterns I did recently at several international conferences, including GIDS (Bangalore), ACCU (Oxford), Camp Digital (Manchester), Agile Open Holland (Dieren) and Jazoon (Zurich).
What is "Agile"?
Why would someone like to be agile?
What are the 3 pillars for agile software development?
How can you achieve technical excellence in your software teams?
Are developer skills more important than languages, methods or frameworks?
Agile ME Meetup: Agile A-Z - Chapter 1: The Product OwnerRasmus Runberg
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organisations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
In the first chapter, we had a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? - In this chapter we will go more into the details with the Product Owner.
As a Product Owner you’re responsible for your product, together with your team and the client setting the direction of the product, making sure everyone is happy with the outcome. In this chapter, we will cover the following topics:
• Vision
• Backlog
• Epic and User Stories
• Agile Planning
The secret life of an Agile Business Analyst - Sydney Agile Meetup group - 13...Ryan McKergow
The Agile Business Analyst seems to be a bit of an unknown quantity to some people. Frameworks like Scrum and SAFe have no mention of the Business Analyst. Is it because they don't understand us? Is it because to outsiders we're living in secret? Andrew and Ryan will explain how the Agile Business Analyst is an essential role that is evolving as our the world around us is constantly change and becoming increasingly more complex. Our focus is shifting from just requirements to delivering value. Throughout this talk and discussion with the audience we will demystify the secret life of the Agile Business Analyst.
Agile has become mainstream in the IT industry, since that the multiplication of Agile practices which makes Agile implementation complex and uncertain, we have started to see failure in Agile implementations.
During this presentation we will start a simplification process by going back to the source of Agile, understand what Agile is and what it is not. We will discover what is the Heart of Agile, its essence, and how it embraces management.
Reference: Agile Manifesto, Heart of Agile blogs Alistair Cockburn, plus historical information about Agile mouvement
Agile ME Meetup: Agile A-Z - Chapter 1: AgileAgile ME
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organizations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
This Chapter (1/6): Agile
In this first chapter, we will have a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? We will cover the following topics:
• The Agile Manifesto and it's principles
• Agile Methodology vs. Mindset and Culture
• The value of Agile
• SCRUM
• Kanban
IxDA October Event: Prototyping Approaches and OutcomesIxDA Chicago
Prototyping is not a new concept, but the role it plays in the design process has changed dramatically in the last few years. Proliferation of agile methods and the grassroots nature of design thinking have opened up new opportunities where research and design happen simultaneously. New tools for building digital prototypes have given design teams numerous options from very simple demos to complex proof of concepts.
Learn about the Devbridge Design team's experience as they explore cases where prototyping has driven the design and research process. With varying levels of complexity and fidelity, each has had a different outcome.
Agile Anti-Patterns. Yes your agile projects can and will fail too.Sander Hoogendoorn
This is the slide deck for a smooth presentation on agile and agile anti-patterns I did recently at several international conferences, including GIDS (Bangalore), ACCU (Oxford), Camp Digital (Manchester), Agile Open Holland (Dieren) and Jazoon (Zurich).
What is "Agile"?
Why would someone like to be agile?
What are the 3 pillars for agile software development?
How can you achieve technical excellence in your software teams?
Are developer skills more important than languages, methods or frameworks?
Agile ME Meetup: Agile A-Z - Chapter 1: The Product OwnerRasmus Runberg
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organisations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
In the first chapter, we had a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? - In this chapter we will go more into the details with the Product Owner.
As a Product Owner you’re responsible for your product, together with your team and the client setting the direction of the product, making sure everyone is happy with the outcome. In this chapter, we will cover the following topics:
• Vision
• Backlog
• Epic and User Stories
• Agile Planning
In Agile/Scrum the skills of a BA are still needed, especially in more complex efforts. This describes BA skills applied in Agile. Should the BA be a Product Owner? On the scrum team?
Session 5 Everything You Should Know About PMP & CAPM CertificationsSeshne Govender
This series will help Project Management Professionals to learn more about the scope of the certifications and shed more light on the intricacies surrounding the PMP® and CAPM® certifications.
Learn more about PMP® and CAPM® and the positive impact they may have on your professional career. Both PMP® and CAPM® from PMI could help you achieve that elusive promotion or get you that golden ticket to joining your dream organization.
Registration Link: https://bit.ly/42iE5rJ
Session Dates: 15th November'23 / 20th December'23 / 17th January'24
Session Timings: 09:30 AM - 10:30 AM (BST) / 10:30 AM - 11:30 AM (CEST/SAST) / 11:30 AM - 12:30 PM (EAT/AST) / 12:30 PM - 01:30 PM (GST) / 02:00 PM - 03:00 PM (IST) / 03:30 PM - 04:30 PM (ICT/WIB) / 04:30 PM - 05:30 PM (SGT/PHST) / 07:30 PM - 08:30 PM (AEDT)
Only final registrants to the event in the link (https://bit.ly/42iE5rJ) can avail of a 50% discount on all online PMP/CAPM programs of vCare Project Management conducted by Seshne Govender PgMP, PMP, DASM, DASSM, PDM, BSc Eng in 2023 & 2024.
The product owner and the scrum team. Can one person do this at scale?Derek Huether
Presented at IIBA Baltimore on March 11, 2014. The last 10 years of Agile have focused on the team. The next 10 years of Agile will focus on the enterprise. That said, should the Product Owner continue to be a single person or does it need to evolve as well? Let's cover the basics and then see how LeadingAgile has been successful at leveraging the Product Owner role at scale.
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 ;-)
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.
I had a good session yesterday as a guest lecturer at UCT to discuss the value of Business Architecture in executing projects using agile as the delivery method to the group completing the Postgraduate Diploma in Enterprise Systems and Business Process Management.
Showcase the fundamentals of the agile methodology through the aid of stunning visuals using Agile Planning PowerPoint Presentation Slides. This compelling project planning PPT theme is replete with infographics, and other diagrams to help you convey the information precisely. Project managers can compare agile with other techniques like waterfall methodology and compile results through agile management PPT template. Illustrate agile methodologies like Scrum and extreme programming with the help of stimulating flowcharts included in agile project plan PowerPoint theme. Develop and present the team structure for agile in a concise manner by the means of agile process PPT slideshow. This agile framework PowerPoint presentation gives you a layout to present agile planning levels, and agile development lifecycle. Also, by using our scrum approach to planning PPT deck you can demonstrate the agile planning challenges and review sprints. Download the scrum model PowerPoint slideshow to get easy-to-edit slides like column chart, timeline graph, and percentage charts. https://bit.ly/3kWm3bS
The Butterfly Principle for Product Management by GameBench CEOProduct School
Startups have changed the way technology companies perceive product management. Experimentation and application of lean principles are no longer just for startups. Large enterprises want to cultivate a startup mindset and mimic such an environment.
So what’s the startup product mindset? How does obsession with a customer problem help startups succeed? And what makes them fail?
Sri shared his experiences and real examples around customer-centric and pragmatic product management that gives enterprises an edge over their competitors. He discussed the butterfly principle in product creation and how it helps create products customer love.
In the last 24 months, we've transformed the way we work using the Scaled Agile Framework. To help with the transformation, we are also using UX practices, design thinking and lean startup methods.
By the end of this presentation, you will understand how we have leveraged UX practices, innovation games and design sprints to improve the maturation of the business needs and their prioritisation to best fit what our users want and deliver value in a continuous flow.
What is Agile & Agile Project Management?. Introduction to Plan-based vs value-driven development; Scrum framework and roles and ceremonies; self-organised team, agile values. and leadership
This slide share will help users to understand the agile software development methodology and how does it work. It also defines the whole process to implement scrum methodology.
Similar to Mike Cottmeyer - How to Own a Really big complex Product (20)
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
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
42. Owning Complex Products 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
43. User Story Screen User Story Team User Story Report User Story User Story Database User Story User Story
44. User Story Screen User Story Team User Story Report User Story User Story Database User Story User Story
54. 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
93. Product Owner Capabilities Agile as Business Analysis Agile as Engineering Agile as Leadership & Coordination
94. 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
95. 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
96. 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
108. Summary Product Owners don’t scale Common strategies don’t work It takes more than one team to deliver value
109. 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
110. 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
111. mike cottmeyervice-president, pillar technology semcottmeyer@pillartechnology.com+1.404.312.1471www.pillartechnology.comwww.leadingagile.comtwitter.com/mcottmeyer
112. 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.
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.