PCA14: Intro to agile for product managers
•
4 likes•2,378 views
This document provides an introduction to agile development for product managers. It discusses some key differences between traditional waterfall development and empirical agile processes. The document also outlines the scrum process, including product owner responsibilities like maintaining the product backlog and collaborating with stakeholders. It emphasizes that working software is the primary measure of progress in agile.
Report
Share
Report
Share
Download to read offline
Recommended
PCA14: Accelerate Learning and Overcome the 6 Traps of Agile
The document discusses 6 common traps that teams fall into when working in an agile way. These traps are: 1) making decisions too early and locking them in, 2) not having a shared understanding of purpose, 3) long feedback cycles with no validation, 4) being overwhelmed by opportunities, 5) not getting work fully completed ("done"), and 6) treating all work as equally important. For each trap, the document provides examples and proposes solutions like deferring decisions, using user story mapping, employing lean startup principles, limiting work in progress, focusing on completion over features, and prioritizing work. The overall message is that teams need to accelerate learning, deliver value faster, and avoid these traps in order to be
Agile methods and dw mha
This document discusses applying agile concepts to data warehousing projects to deliver results faster. It begins with the presenter's background and an overview of Snowflake Computing. It then covers the 12 principles of agile, explaining how each could be applied in a data warehousing context, such as having daily standups with business users, using prioritized backlogs and user stories, delivering working code/reports frequently in short iterations focused on a subject area, and using data vault modeling techniques. Retrospectives are emphasized as important for continuous improvement.
Managing Scaled Agile at Rosetta Stone
The realities of working in an enterprise (distributed teams, multiple stakeholders, etc) present a series of challenges when trying to plan and scale agile development. Learn how Rosetta Stone knit together a dozen existing JIRA Agile boards into a coherent program-level view of their Scaled Agile Framework (SAFe) release train using JIRA Portfolio – without sacrificing team autonomy.
Large Scale Scrum at Powerhouse.
This document contains copyright information for AgiliX Agile Consulting B.V. from 2014-2015. It discusses organizing teams into value areas based on customer domains to improve understanding. It also contains quotes from teams about challenges with testing, helping other teams, and standards. Finally, it outlines moving to self-managing feature teams organized for flow of customer value.
Scaled Agile Framework in 10 minutes (CAS2015)
Scaled Agile Framework in 10 minutes (SAFe 3.0)
- Scaled: SAFe is designed for large-scale software development ecosystems of 50-125 people who need to resolve inter-dependencies
- Agile: SAFe is based on 9 Lean-Agile principles
- Framework: SAFe is a collection of a proven efficacy tools, and you only have to use what you need
https://www.youtube.com/watch?v=vysQQx7pQzg
El objetivo de la Lightning Talk es dar una visión "light" pero completa de lo que propone Scaled Agile Framework 3.0 como marco de referencia para el escalado de Agile.
Scaled Agile Framework es uno de los marcos de referencia para escalado de Agile que mayor aceptación está teniendo a día de hoy, sobre todo cuando hablamos de grandes organizaciones. El marco SAFe parte de las capas de abstracción clásicas de una organización para estructurar un cambio de perspectiva y de cultura basándose en los 4 valores y 9 principios Lean-Agile, apoyándose además en las prácticas Scrum-XP de desarrollo de productos. En la charla descubriremos de manera rápida los roles, artefactos y ceremonias que plantea el marco para conseguir un cambio de paradigma sostenible en las organizaciones.
Unai Roldán
UST Global
Leading enterprise transformation lessons adopting agile in government
The document summarizes lessons learned from adopting agile practices at the National Geospatial Technical Operations Center (NGTOC). It describes how NGTOC previously managed systems development in a disorganized way without clear processes or communication. It then explains changes made by adopting agile tools and methods like prioritizing requirements, organizing work into teams, and improving communication platforms. As a result, NGTOC saw improved code quality, workforce collaboration, planning, and ability to manage uncertainty. The document outlines leadership strategies that helped enable the agile transformation, such as allowing experimentation, spreading lessons learned, understanding what decisions to make themselves versus empowering the workforce, and facilitating cultural change.
Comparing Ways to Scale Agile at Agile Product and Project Manager Meetup
Session "Comparing Ways to Scale Agile" at the Agile Product and Project Manager Meetup in Melbourne, Australia.
These days organisations are looking for support to scale their Agile environment. There’s a difference between having one Agile team on its own, or to have several Agile teams providing value to the customer and interacting with each other.
This session will give an overview and comparison of all the different Agile scaling approaches out there, i.e.:
* Scaled Agile Framework (SAFe)
* Evidence-Based Management (EBMgt)
* Disciplined Agile Delivery (DAD)
* Enterprise Transition Framework (ETF)
* Large-Scale Scrum (LeSS)
* ScALeD Agile Lean Development
* Scaling Agile @ Spotify (SA@S)
* Product Development Flow by Reinertsen (PDFbyR)
The Service-Delivery Review: The Missing Agile Feedback Loop [Lean and Agile ...
The document discusses the need for a service-delivery review feedback loop between customer and delivery teams. It proposes a regular, quantitative review to discuss the fitness of a team's service delivery for its intended purpose. Key metrics like delivery times, blockers, value-demand ratio would be reviewed. Establishing clear service-level expectations and collecting feedback helps teams understand failures and improve their service to better meet customer needs. Regular reviews in a collaborative spirit can strengthen relationships and build customer trust and loyalty.
Recommended
PCA14: Accelerate Learning and Overcome the 6 Traps of Agile
The document discusses 6 common traps that teams fall into when working in an agile way. These traps are: 1) making decisions too early and locking them in, 2) not having a shared understanding of purpose, 3) long feedback cycles with no validation, 4) being overwhelmed by opportunities, 5) not getting work fully completed ("done"), and 6) treating all work as equally important. For each trap, the document provides examples and proposes solutions like deferring decisions, using user story mapping, employing lean startup principles, limiting work in progress, focusing on completion over features, and prioritizing work. The overall message is that teams need to accelerate learning, deliver value faster, and avoid these traps in order to be
Agile methods and dw mha
This document discusses applying agile concepts to data warehousing projects to deliver results faster. It begins with the presenter's background and an overview of Snowflake Computing. It then covers the 12 principles of agile, explaining how each could be applied in a data warehousing context, such as having daily standups with business users, using prioritized backlogs and user stories, delivering working code/reports frequently in short iterations focused on a subject area, and using data vault modeling techniques. Retrospectives are emphasized as important for continuous improvement.
Managing Scaled Agile at Rosetta Stone
The realities of working in an enterprise (distributed teams, multiple stakeholders, etc) present a series of challenges when trying to plan and scale agile development. Learn how Rosetta Stone knit together a dozen existing JIRA Agile boards into a coherent program-level view of their Scaled Agile Framework (SAFe) release train using JIRA Portfolio – without sacrificing team autonomy.
Large Scale Scrum at Powerhouse.
This document contains copyright information for AgiliX Agile Consulting B.V. from 2014-2015. It discusses organizing teams into value areas based on customer domains to improve understanding. It also contains quotes from teams about challenges with testing, helping other teams, and standards. Finally, it outlines moving to self-managing feature teams organized for flow of customer value.
Scaled Agile Framework in 10 minutes (CAS2015)
Scaled Agile Framework in 10 minutes (SAFe 3.0)
- Scaled: SAFe is designed for large-scale software development ecosystems of 50-125 people who need to resolve inter-dependencies
- Agile: SAFe is based on 9 Lean-Agile principles
- Framework: SAFe is a collection of a proven efficacy tools, and you only have to use what you need
https://www.youtube.com/watch?v=vysQQx7pQzg
El objetivo de la Lightning Talk es dar una visión "light" pero completa de lo que propone Scaled Agile Framework 3.0 como marco de referencia para el escalado de Agile.
Scaled Agile Framework es uno de los marcos de referencia para escalado de Agile que mayor aceptación está teniendo a día de hoy, sobre todo cuando hablamos de grandes organizaciones. El marco SAFe parte de las capas de abstracción clásicas de una organización para estructurar un cambio de perspectiva y de cultura basándose en los 4 valores y 9 principios Lean-Agile, apoyándose además en las prácticas Scrum-XP de desarrollo de productos. En la charla descubriremos de manera rápida los roles, artefactos y ceremonias que plantea el marco para conseguir un cambio de paradigma sostenible en las organizaciones.
Unai Roldán
UST Global
Leading enterprise transformation lessons adopting agile in government
The document summarizes lessons learned from adopting agile practices at the National Geospatial Technical Operations Center (NGTOC). It describes how NGTOC previously managed systems development in a disorganized way without clear processes or communication. It then explains changes made by adopting agile tools and methods like prioritizing requirements, organizing work into teams, and improving communication platforms. As a result, NGTOC saw improved code quality, workforce collaboration, planning, and ability to manage uncertainty. The document outlines leadership strategies that helped enable the agile transformation, such as allowing experimentation, spreading lessons learned, understanding what decisions to make themselves versus empowering the workforce, and facilitating cultural change.
Comparing Ways to Scale Agile at Agile Product and Project Manager Meetup
Session "Comparing Ways to Scale Agile" at the Agile Product and Project Manager Meetup in Melbourne, Australia.
These days organisations are looking for support to scale their Agile environment. There’s a difference between having one Agile team on its own, or to have several Agile teams providing value to the customer and interacting with each other.
This session will give an overview and comparison of all the different Agile scaling approaches out there, i.e.:
* Scaled Agile Framework (SAFe)
* Evidence-Based Management (EBMgt)
* Disciplined Agile Delivery (DAD)
* Enterprise Transition Framework (ETF)
* Large-Scale Scrum (LeSS)
* ScALeD Agile Lean Development
* Scaling Agile @ Spotify (SA@S)
* Product Development Flow by Reinertsen (PDFbyR)
The Service-Delivery Review: The Missing Agile Feedback Loop [Lean and Agile ...
The document discusses the need for a service-delivery review feedback loop between customer and delivery teams. It proposes a regular, quantitative review to discuss the fitness of a team's service delivery for its intended purpose. Key metrics like delivery times, blockers, value-demand ratio would be reviewed. Establishing clear service-level expectations and collecting feedback helps teams understand failures and improve their service to better meet customer needs. Regular reviews in a collaborative spirit can strengthen relationships and build customer trust and loyalty.
How to Jumpstart Enterprise Agile Adoption
- Alan Padula presented on how to jumpstart enterprise agile adoption based on his experience leading Intuit Financial Services' (IFS) transformation to agile.
- IFS followed Kotter's 8-step change model, starting with establishing urgency and guiding teams, then getting the vision right and communicating it. They enabled action through extensive training, transition elements, and governance processes. Short-term wins and continuous improvement helped make the change stick.
- Key lessons included focusing on promoters over naysayers, allocating dedicated resources, investing in training and coaches, finding leaders to drive the change, and accepting it takes time for a mindset change.
Foundations of the Scaled Agile Framework: Be Agile. Scale Up. Stay Lean. And...
Foundations of the Scaled Agile Framework: Be Agile. Scale Up. Stay Lean. And...IBM Rational software
Recording of this presentation: http://youtu.be/H_752O8P_Bs
More info DevOps Community: http://bit.ly/DevOpsSAFeThe secret life of an Agile Business Analyst - Sydney Agile Meetup group - 13...
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.
SAFe Planning In Action by Nick McKenna
The Scaled Agile Framework (SAFe) has a special event that is held for every Program Increment (5 sprints-ish). This is a large scale, collaborative event including everyone from the Agile Release Train (50 people plus). This workshop will be a highly interactive event where all participants will be involved in one of many teams collaborating together to plan a single Program Increment for a single product.
The schedule will roughly contain:
Overview of SAFe Program Increment Planning
(Fictional) Business Context
Product / Solution Vision
Architecture Vision And Development Practices
Planning Session 1
Draft Plan Review
Planning Session 2
Final Plan Review
Risk ROAMing
Confidence Vote
Retrospective
Scaled Agile Framework® Overview
Do you have highly functional scrum teams but are wondering how to get them to work in sync with each other, or wondering how get "start-up" efficiency in a large enterprise? Or maybe you just heard that the Scaled Agile Framework for the Enterprise (SAFe®) is gaining traction and you want to find out more about it. Before the year is out, we want to give you a primer on SAFe, so you can decide if it should be on your list of resolutions for the new year!
We continue to see that Agile and Scrum deliver value and are catching the eyes of leadership individuals. But how does a large enterprise thrive with a Scrum framework that was made for 5-9 individuals? SAFe has garnered a lot of attention as a potential framework for enterprises with large product teams (5 or more scrum teams on a product line). It calls for the overall alignment throughout the organization so that the Scrum teams making up a large product development team can deliver valuable, high quality product increments with transparency and technical excellence. The program execution is achieved by leveraging the existing Scrum Team practices and interfacing with the higher Program and Portfolio layers in the organization.
cPrime SAFe coach, Sri will provide an overview of the SAFe framework and show why it appeals not only to the engineers and architects, but also to the product management, customer support and the executive team.
AgileLIVE – Accelerate Enterprise Agile with the Scaled Agile Framework®: Part I
Interested in finding out how to scale agile faster, easier and smarter using the Scaled Agile Framework® (SAFe)? If so, make sure you watch this two-part webinar series!
Scrum, XP, Kanban and related methods have been proven to provide step changes in productivity and quality for software teams. However, these methods do not have the native constructs necessary to scale across the enterprise. What the industry desperately needs is a solution that moves from a set of simplistic, disparate, development-centric methods, to a scalable, unified approach that addresses the complex constructs and additional stakeholders in the organization – and accelerates the realization of enterprise-class product or service initiatives via aligned and cooperative solution development.
Part I: Join Dean Leffingwell, software industry veteran and Lean Systems Society Fellow, for an overview of SAFe, a publicly–accessible knowledge base of proven lean and agile practices for enterprise-class software development.
Dean Leffingwell, software industry veteran and Lean Systems Society Fellow, has spent his career helping software teams achieve their goals. A renowned methodologist, author, coach, entrepreneur and executive, Dean's most recent project is the Scaled Agile Framework (scaledagileframework.com), a public-facing website which describes a comprehensive system for scaling lean and agile practices to the largest software enterprises.
Andy Powell is Product Evangelist for VersionOne and Scaled Agile Framework Program Consultant. During his 12-year career in the software development industry, Andy has assisted in numerous 500+ person agile tool rollouts with companies such as Siemens, Adobe, EMC and Sabre, giving him considerable experience in leading major projects. Andy received a Bachelor of Science degree in Mechanical Engineering from the University of Notre Dame and graduated magna cum laude.
Lee Cunningham is an Enterprise Agile Coach for VersionOne focused on agile program and portfolio management. Lee has trained and consulted with hundreds of teams in organizations of all sizes in the US, Canada and the UK. Lee served in the United States Air Force and earned a Bachelor of Business Administration degree from the University of North Florida.
The Agile BA
Slides from a presentation given by Steve Thomson to a meeting of IIBA UK's Scotland branch on 11 June 2015.
Agile transformation : From Scattered to Scaled
This document discusses transforming an organization from scattered agile practices to scaled agile. It begins by describing signs of scattered agile, such as inconsistent ceremonies, resistance to change, and teams operating on different cadences. It then recommends a step-by-step approach starting with small wins, identifying two problems to fix, customizing processes, and training teams. Aligning to a common cadence supported by regular demos and estimating capacity using relative estimation are presented as intermediate steps. The final step is scaled agile with faster time to market, ability to react swiftly to changes, and increased productivity and employee happiness. Key takeaways include taking a stepwise approach, focusing on small wins, selecting the appropriate framework, introspect
Foundations of scaling agile with SAFe
Abstract:
More and more organizations are realizing that in order to achieve business agility they need to go beyond implementing agile in specific teams/projects. Real agility requires scaling agile to the program/portfolio/enterprise level. In this session we will explore the options organizations have when looking to scale agile, with an emphasis on SAFe(tm) - the Scaled Agile Framework - one of the most popular options these days.
Learning Objectives:
• When does it make sense to Scale Agile
• What are the leading scaling approaches
• An introduction to SAFe's Big Picture and implementation configurations
• How to implement SAFe - The Implementation Roadmap
• Typical Results of implementing SAFe
• Key risks/red flags to be aware of when implementing SAFe
Evolving Goals: IT vs. Product Mindset
The document contrasts an IT mindset with a product mindset. An IT mindset focuses on serving perceived business needs through requirements gathering and functional silos, while a product mindset focuses on customer needs through product discovery and cross-functional teams. It introduces four levels of maturity - delivered, working, engaging, and valuable products - with goals at each level that enable progress to the next. These levels move from a focus on project management metrics like schedule and budget, to engineering metrics like bugs and uptime, to product metrics around happiness and retention, and finally business metrics like revenue and ROI.
Intro to agile portfolio governance v6
Every large enterprise needs to manage portfolios of business initiatives. Portfolio Management encompasses
• The formulation of initiatives, and the assessment of their value, effort, and Return on Investment
• The approval and scheduling of initiatives
• The evaluation of the status of ongoing initiatives
• The decision to continue or terminate an ongoing initiative
This webinar will provide guidance on effective ways to conduct Portfolio Management, using our concepts of Agile Governance to simplify and expedite the key decisions. These techniques can applied for Agile, hybrid, and classic plan-driven processes.
My Inspect & Adapt Life - Computershare ConneCTShe
Victoria Schiffer has had a varied career spanning roles in software engineering, product management, business analysis, delivery lead, agile coaching, and leadership coaching. She shares her career journey and insights on adapting to change, embracing challenges, and maintaining a growth mindset. She emphasizes the importance of being a role model, pushing herself outside her comfort zone, and creating opportunities for other women in technology.
Scaling agile Principles and Practices
This document discusses principles and practices for scaling agile approaches in organizations. It begins by introducing Josef Scherer as an agile management consultant with experience helping large companies adopt scaled agile frameworks. It then poses questions to consider when scaling agile, such as goals, the type of scaling needed, and potential practices. The document outlines vertical and horizontal scaling and describes scaled roles, artifacts, and events in the Scaled Agile Framework. It also discusses scaling practices at Spotify, including feature teams and microservice architecture. Finally, it emphasizes that principles are more important than practices when scaling and should drive autonomy through purpose and motivation.
Scaling Quality by Building It In - Agile Tour Montreal 2017
Presentation at Agile Tour Montreal 2017 by Maurizio Mancini of Exempio. This presentation is a "Ted Like talk" of the presentation done at Ottawa Agile Tour 2017. It provides a focus from the view of an Agile Coach and how to help large organizations to Scale quality by building in quality early in the software cycle.
User Stories Suck - David Hawks, Agile 2018
Enjoy the full slide deck from David Hawks' presentation, User Stories Suck, from Agile 2018.
The current Epic and User Story process is stale and needs to go. David Hawks presented a new discovery centered model driven by Objectives, Hypothesis, and Experiments.
User Stories Suck - David Hawks & Reese Schmit - IIBA Austin January 2019
The User Story concept was invented almost 20 years ago, and it’s time for an update. This outdated process supports an old way of working focused on predictable requirements delivery instead of product discovery. Wouldn’t you like to know much earlier which features are not going to be valued by your market? We need techniques that shorten the feedback loop with customers, not stakeholders. We need to prioritize based on riskiest assumptions and iterate quickly through small experiments in order to (in)validate our ideas as fast as possible.
Pair programming pair testing working together with the developers by Simon ...
In my scrum team, as a tester, I'm responsible for the test work to be done. Most of that test work is done manually. We need to automate those test cases. But, when? And how?
The developers and and the tester can do a lot together. Some times we test together. Some times we program together. Some times I'm on my own, testing or creating/writing automation scripts.
In my talk I will share my experiences what I'm doing with my developer colleagues. From the moment we start development on the feature (Epic or user story) up until we ship it.
We explore, build and test the feature. Based on that we create scripts for automation on various levels. From unit test level up until end to end testing.
Take aways from this session are:
- How to work together with your developer(s)
- Motivate your stakeholders to work this way
- Give tester a way to participate in coding and learn from the experience
- Provide Agile coaches a way how to set up automation in a scrum team
Scaling agile. Agile across the enterprise
This document discusses scaling agile across large organizations. It introduces agile mindset, values, principles and practices. It also covers several frameworks for scaling agile such as Large Scale Scrum (LeSS), Scaled Agile Framework (SAFe), and Disciplined Agile Delivery (DAD). Adopting agile requires changes to organizational culture and giving autonomy and mastery to self-organizing teams. Scaling agile is not just about processes but transforming the mindset and empowering people.
Scaling Agile
A common practice among teams in IT companies adopting the latest trends, Agile can be scaled to enterprise level once applied properly. In this Innovation Session, Maduri Senadheera from the Project Management team talks about the Agile mindset, the need for scaling and the benefits of a Scaled Agile Framework for better aligning business processes.
Agile Business Transformation
In this unique presentation, Kevin will discuss his experience at Adobe, Microsoft, Spotify and now at a legal online marketplace, Avvo. In each organization, Kevin used his background in Operational Excellence to transform businesses. Kevin has created nimble innovation cultures at Adobe & Microsoft, and has used operational excellence tools to help innovation at Spotify. He will discuss how:
* How Avvo’s leadership team focuses on the larger strategy at this rapidly growing company, empowering employees to make decisions
* Articulating and communicating the strategy in a way that employees understand
* Aligning and prioritizing innovation projects at Spotify to overall business goals and objectives
* How to benefit from speed and how to operate on a larger scale.
SCRUM, an introduction
Scrum is an agile framework for managing work. It is iterative, incremental and focuses on collaboration and adaptation. Key aspects of Scrum include short iterations called sprints where work is completed and reviewed, daily stand-up meetings to track progress, and roles like Product Owner, Scrum Master and Development Team. Scrum aims to increase transparency, drive progress through commitment to sprints, and provide signals on project status through its meetings and reviews.
Agile and the BA
The document discusses the role of the business analyst in agile software development. Some key points of agile methodologies include iterative development, prioritizing individual/team interactions over processes/tools, and collaborating closely with customers. For business analysts, agile means working on just-in-time requirements in short iterations, using lightweight documentation and user stories to plan work in sprints, and adapting to change through collaboration and scope negotiation with developers. Challenges include managing requirement changes across iterations and ensuring effective communication in distributed teams.
More Related Content
What's hot
How to Jumpstart Enterprise Agile Adoption
- Alan Padula presented on how to jumpstart enterprise agile adoption based on his experience leading Intuit Financial Services' (IFS) transformation to agile.
- IFS followed Kotter's 8-step change model, starting with establishing urgency and guiding teams, then getting the vision right and communicating it. They enabled action through extensive training, transition elements, and governance processes. Short-term wins and continuous improvement helped make the change stick.
- Key lessons included focusing on promoters over naysayers, allocating dedicated resources, investing in training and coaches, finding leaders to drive the change, and accepting it takes time for a mindset change.
Foundations of the Scaled Agile Framework: Be Agile. Scale Up. Stay Lean. And...
Foundations of the Scaled Agile Framework: Be Agile. Scale Up. Stay Lean. And...IBM Rational software
Recording of this presentation: http://youtu.be/H_752O8P_Bs
More info DevOps Community: http://bit.ly/DevOpsSAFeThe secret life of an Agile Business Analyst - Sydney Agile Meetup group - 13...
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.
SAFe Planning In Action by Nick McKenna
The Scaled Agile Framework (SAFe) has a special event that is held for every Program Increment (5 sprints-ish). This is a large scale, collaborative event including everyone from the Agile Release Train (50 people plus). This workshop will be a highly interactive event where all participants will be involved in one of many teams collaborating together to plan a single Program Increment for a single product.
The schedule will roughly contain:
Overview of SAFe Program Increment Planning
(Fictional) Business Context
Product / Solution Vision
Architecture Vision And Development Practices
Planning Session 1
Draft Plan Review
Planning Session 2
Final Plan Review
Risk ROAMing
Confidence Vote
Retrospective
Scaled Agile Framework® Overview
Do you have highly functional scrum teams but are wondering how to get them to work in sync with each other, or wondering how get "start-up" efficiency in a large enterprise? Or maybe you just heard that the Scaled Agile Framework for the Enterprise (SAFe®) is gaining traction and you want to find out more about it. Before the year is out, we want to give you a primer on SAFe, so you can decide if it should be on your list of resolutions for the new year!
We continue to see that Agile and Scrum deliver value and are catching the eyes of leadership individuals. But how does a large enterprise thrive with a Scrum framework that was made for 5-9 individuals? SAFe has garnered a lot of attention as a potential framework for enterprises with large product teams (5 or more scrum teams on a product line). It calls for the overall alignment throughout the organization so that the Scrum teams making up a large product development team can deliver valuable, high quality product increments with transparency and technical excellence. The program execution is achieved by leveraging the existing Scrum Team practices and interfacing with the higher Program and Portfolio layers in the organization.
cPrime SAFe coach, Sri will provide an overview of the SAFe framework and show why it appeals not only to the engineers and architects, but also to the product management, customer support and the executive team.
AgileLIVE – Accelerate Enterprise Agile with the Scaled Agile Framework®: Part I
Interested in finding out how to scale agile faster, easier and smarter using the Scaled Agile Framework® (SAFe)? If so, make sure you watch this two-part webinar series!
Scrum, XP, Kanban and related methods have been proven to provide step changes in productivity and quality for software teams. However, these methods do not have the native constructs necessary to scale across the enterprise. What the industry desperately needs is a solution that moves from a set of simplistic, disparate, development-centric methods, to a scalable, unified approach that addresses the complex constructs and additional stakeholders in the organization – and accelerates the realization of enterprise-class product or service initiatives via aligned and cooperative solution development.
Part I: Join Dean Leffingwell, software industry veteran and Lean Systems Society Fellow, for an overview of SAFe, a publicly–accessible knowledge base of proven lean and agile practices for enterprise-class software development.
Dean Leffingwell, software industry veteran and Lean Systems Society Fellow, has spent his career helping software teams achieve their goals. A renowned methodologist, author, coach, entrepreneur and executive, Dean's most recent project is the Scaled Agile Framework (scaledagileframework.com), a public-facing website which describes a comprehensive system for scaling lean and agile practices to the largest software enterprises.
Andy Powell is Product Evangelist for VersionOne and Scaled Agile Framework Program Consultant. During his 12-year career in the software development industry, Andy has assisted in numerous 500+ person agile tool rollouts with companies such as Siemens, Adobe, EMC and Sabre, giving him considerable experience in leading major projects. Andy received a Bachelor of Science degree in Mechanical Engineering from the University of Notre Dame and graduated magna cum laude.
Lee Cunningham is an Enterprise Agile Coach for VersionOne focused on agile program and portfolio management. Lee has trained and consulted with hundreds of teams in organizations of all sizes in the US, Canada and the UK. Lee served in the United States Air Force and earned a Bachelor of Business Administration degree from the University of North Florida.
The Agile BA
Slides from a presentation given by Steve Thomson to a meeting of IIBA UK's Scotland branch on 11 June 2015.
Agile transformation : From Scattered to Scaled
This document discusses transforming an organization from scattered agile practices to scaled agile. It begins by describing signs of scattered agile, such as inconsistent ceremonies, resistance to change, and teams operating on different cadences. It then recommends a step-by-step approach starting with small wins, identifying two problems to fix, customizing processes, and training teams. Aligning to a common cadence supported by regular demos and estimating capacity using relative estimation are presented as intermediate steps. The final step is scaled agile with faster time to market, ability to react swiftly to changes, and increased productivity and employee happiness. Key takeaways include taking a stepwise approach, focusing on small wins, selecting the appropriate framework, introspect
Foundations of scaling agile with SAFe
Abstract:
More and more organizations are realizing that in order to achieve business agility they need to go beyond implementing agile in specific teams/projects. Real agility requires scaling agile to the program/portfolio/enterprise level. In this session we will explore the options organizations have when looking to scale agile, with an emphasis on SAFe(tm) - the Scaled Agile Framework - one of the most popular options these days.
Learning Objectives:
• When does it make sense to Scale Agile
• What are the leading scaling approaches
• An introduction to SAFe's Big Picture and implementation configurations
• How to implement SAFe - The Implementation Roadmap
• Typical Results of implementing SAFe
• Key risks/red flags to be aware of when implementing SAFe
Evolving Goals: IT vs. Product Mindset
The document contrasts an IT mindset with a product mindset. An IT mindset focuses on serving perceived business needs through requirements gathering and functional silos, while a product mindset focuses on customer needs through product discovery and cross-functional teams. It introduces four levels of maturity - delivered, working, engaging, and valuable products - with goals at each level that enable progress to the next. These levels move from a focus on project management metrics like schedule and budget, to engineering metrics like bugs and uptime, to product metrics around happiness and retention, and finally business metrics like revenue and ROI.
Intro to agile portfolio governance v6
Every large enterprise needs to manage portfolios of business initiatives. Portfolio Management encompasses
• The formulation of initiatives, and the assessment of their value, effort, and Return on Investment
• The approval and scheduling of initiatives
• The evaluation of the status of ongoing initiatives
• The decision to continue or terminate an ongoing initiative
This webinar will provide guidance on effective ways to conduct Portfolio Management, using our concepts of Agile Governance to simplify and expedite the key decisions. These techniques can applied for Agile, hybrid, and classic plan-driven processes.
My Inspect & Adapt Life - Computershare ConneCTShe
Victoria Schiffer has had a varied career spanning roles in software engineering, product management, business analysis, delivery lead, agile coaching, and leadership coaching. She shares her career journey and insights on adapting to change, embracing challenges, and maintaining a growth mindset. She emphasizes the importance of being a role model, pushing herself outside her comfort zone, and creating opportunities for other women in technology.
Scaling agile Principles and Practices
This document discusses principles and practices for scaling agile approaches in organizations. It begins by introducing Josef Scherer as an agile management consultant with experience helping large companies adopt scaled agile frameworks. It then poses questions to consider when scaling agile, such as goals, the type of scaling needed, and potential practices. The document outlines vertical and horizontal scaling and describes scaled roles, artifacts, and events in the Scaled Agile Framework. It also discusses scaling practices at Spotify, including feature teams and microservice architecture. Finally, it emphasizes that principles are more important than practices when scaling and should drive autonomy through purpose and motivation.
Scaling Quality by Building It In - Agile Tour Montreal 2017
Presentation at Agile Tour Montreal 2017 by Maurizio Mancini of Exempio. This presentation is a "Ted Like talk" of the presentation done at Ottawa Agile Tour 2017. It provides a focus from the view of an Agile Coach and how to help large organizations to Scale quality by building in quality early in the software cycle.
User Stories Suck - David Hawks, Agile 2018
Enjoy the full slide deck from David Hawks' presentation, User Stories Suck, from Agile 2018.
The current Epic and User Story process is stale and needs to go. David Hawks presented a new discovery centered model driven by Objectives, Hypothesis, and Experiments.
User Stories Suck - David Hawks & Reese Schmit - IIBA Austin January 2019
The User Story concept was invented almost 20 years ago, and it’s time for an update. This outdated process supports an old way of working focused on predictable requirements delivery instead of product discovery. Wouldn’t you like to know much earlier which features are not going to be valued by your market? We need techniques that shorten the feedback loop with customers, not stakeholders. We need to prioritize based on riskiest assumptions and iterate quickly through small experiments in order to (in)validate our ideas as fast as possible.
Pair programming pair testing working together with the developers by Simon ...
In my scrum team, as a tester, I'm responsible for the test work to be done. Most of that test work is done manually. We need to automate those test cases. But, when? And how?
The developers and and the tester can do a lot together. Some times we test together. Some times we program together. Some times I'm on my own, testing or creating/writing automation scripts.
In my talk I will share my experiences what I'm doing with my developer colleagues. From the moment we start development on the feature (Epic or user story) up until we ship it.
We explore, build and test the feature. Based on that we create scripts for automation on various levels. From unit test level up until end to end testing.
Take aways from this session are:
- How to work together with your developer(s)
- Motivate your stakeholders to work this way
- Give tester a way to participate in coding and learn from the experience
- Provide Agile coaches a way how to set up automation in a scrum team
Scaling agile. Agile across the enterprise
This document discusses scaling agile across large organizations. It introduces agile mindset, values, principles and practices. It also covers several frameworks for scaling agile such as Large Scale Scrum (LeSS), Scaled Agile Framework (SAFe), and Disciplined Agile Delivery (DAD). Adopting agile requires changes to organizational culture and giving autonomy and mastery to self-organizing teams. Scaling agile is not just about processes but transforming the mindset and empowering people.
Scaling Agile
A common practice among teams in IT companies adopting the latest trends, Agile can be scaled to enterprise level once applied properly. In this Innovation Session, Maduri Senadheera from the Project Management team talks about the Agile mindset, the need for scaling and the benefits of a Scaled Agile Framework for better aligning business processes.
Agile Business Transformation
In this unique presentation, Kevin will discuss his experience at Adobe, Microsoft, Spotify and now at a legal online marketplace, Avvo. In each organization, Kevin used his background in Operational Excellence to transform businesses. Kevin has created nimble innovation cultures at Adobe & Microsoft, and has used operational excellence tools to help innovation at Spotify. He will discuss how:
* How Avvo’s leadership team focuses on the larger strategy at this rapidly growing company, empowering employees to make decisions
* Articulating and communicating the strategy in a way that employees understand
* Aligning and prioritizing innovation projects at Spotify to overall business goals and objectives
* How to benefit from speed and how to operate on a larger scale.
What's hot (20)
Foundations of the Scaled Agile Framework: Be Agile. Scale Up. Stay Lean. And...
Foundations of the Scaled Agile Framework: Be Agile. Scale Up. Stay Lean. And...
The secret life of an Agile Business Analyst - Sydney Agile Meetup group - 13...
The secret life of an Agile Business Analyst - Sydney Agile Meetup group - 13...
AgileLIVE – Accelerate Enterprise Agile with the Scaled Agile Framework®: Part I
AgileLIVE – Accelerate Enterprise Agile with the Scaled Agile Framework®: Part I
My Inspect & Adapt Life - Computershare ConneCTShe
My Inspect & Adapt Life - Computershare ConneCTShe
Scaling Quality by Building It In - Agile Tour Montreal 2017
Scaling Quality by Building It In - Agile Tour Montreal 2017
User Stories Suck - David Hawks & Reese Schmit - IIBA Austin January 2019
User Stories Suck - David Hawks & Reese Schmit - IIBA Austin January 2019
Pair programming pair testing working together with the developers by Simon ...
Pair programming pair testing working together with the developers by Simon ...
Viewers also liked
SCRUM, an introduction
Scrum is an agile framework for managing work. It is iterative, incremental and focuses on collaboration and adaptation. Key aspects of Scrum include short iterations called sprints where work is completed and reviewed, daily stand-up meetings to track progress, and roles like Product Owner, Scrum Master and Development Team. Scrum aims to increase transparency, drive progress through commitment to sprints, and provide signals on project status through its meetings and reviews.
Agile and the BA
The document discusses the role of the business analyst in agile software development. Some key points of agile methodologies include iterative development, prioritizing individual/team interactions over processes/tools, and collaborating closely with customers. For business analysts, agile means working on just-in-time requirements in short iterations, using lightweight documentation and user stories to plan work in sprints, and adapting to change through collaboration and scope negotiation with developers. Challenges include managing requirement changes across iterations and ensuring effective communication in distributed teams.
How to Become a Thought Leader in Your Niche
Are bloggers thought leaders? Here are some tips on how you can become one. Provide great value, put awesome content out there on a regular basis, and help others.
DecisionsFirst Modeler and IBM ODM Demonstration
DecisionsFirst Modeler enables organizations to accurately specify their business using decision requirements models; structure and manage the supporting business rules; and streamline business process design.
The Enterprise Edition integration with IBM ODM delivers traceability from business objectives through decision requirements to the business rules running in production. This ensures that DecisionsFirst Modeler users have full access to all the rule editing, validation, simulation, deployment and management capabilities of IBM ODM.
DecisionsFirst Modeler is a collaborative decision modeling solution using the new Decision Model and Notation (DMN) standard. DecisionsFirst Modeler provides a diagram-based, business user friendly front-end to the business rules environment.
Strategies to split user stories
This document discusses user stories (also called PBIs), which are short descriptions of a software feature written from the perspective of an end user. It provides templates and examples for writing user stories, as well as tips on splitting large stories into smaller, testable pieces. Some key points covered include writing stories that focus on the user's goal and benefit, using personas to discover needed features, and decomposing large "epic" stories until they are clear and feasible to implement.
Unlocking Excellence with Agile Metrics
Learn about the importance of measuring the right things and how to use metrics and data to improve performance. Get the right metrics and KPIs to improve performance so you can deliver on your organization’s most important initiatives.
Read The Seven Deadly Sins of Agile Measurement http://2ral.ly/Zqa to make sure you’re measuring performance in a way that actually improves results.
Self Awareness - LEAD session
This document discusses the concepts of fixed and growth mindsets. It explains that a fixed mindset views traits as innate abilities while a growth mindset sees them as qualities that can be developed through effort. It encourages cultivating a growth mindset by believing we can become anything through focused effort and purposeful engagement. The document suggests striving for excellence and continuous growth rather than becoming stagnant. It poses the question of how AIESEC in 2015 could be envisioned from a growth mindset perspective.
The Decision Model and Notation (DMN) standard - a worked example
This paper provides a worked example of decision modelling using the 1.0 beta spec of the Decision Model and Notation (DMN), approved by the Object Management Group (OMG) in January 2014.
This paper gives a taster of DMN - what it looks like, how it fits in with the Business Process Model and Notation (BPMN) and how it can be used to analyse real world situations. It is based on learning directly from the specification.
BA Agile Cert
The document is a certificate from the International Consortium for Agile certifying that Ahmed Sidky has completed the learning and evaluation requirements to be recognized as an ICAgile Certified Professional in Business Value Analysis. The certificate was issued on May 16, 2016 and is signed by Kat McLaurin and Shane Hastie of Software Education Global, verifying Ahmed Sidky has acquired the necessary knowledge in Agile Management as assessed by instructors.
Scrum Gathering: Coaching Trust
This document outlines an agenda for a session on the role of coaching and building trust within teams. The agenda includes: defining coaching; aligning teams around goals and values; building trust; and creating an action plan. It discusses tools for coaching, common team dysfunctions, and conducting an exercise to assess team trust. Methods are presented for improving trust through sharing experiences, open communication, and establishing team values. The document provides guidance and exercises for teams to identify their core and aspirational values, as well as intrinsic motivators. It emphasizes taking action to demonstrate that values matter in building an aligned, high-trust team.
Transitioning our Toolkit
Slides from a presentation given by Andy Williams to a meeting of IIBA UK's South West branch on 21 April 2015
Business Analysis/Analysts - 'The Past, Present and Future
Sildes from a presentation given by Christina Lovelock to the North branch of IIBA UK on 24 November 2016.
BA World - BA in AGILE Projects
The document discusses business analysis on Agile teams. It provides an overview of Agile concepts like Scrum and how its roles, artifacts, and meetings work. It also compares traditional analysis approaches to Agile analysis, noting that Agile focuses on just-enough planning, prioritization by the customer, and documenting user stories and acceptance tests versus full specifications.
Agile Velocity - Deliver double the value in half the time
Learn practical techniques to guide your teams and escape the top 6 traps preventing organizations from realizing the full benefits of agile.
64% of product features built in software development are rarely or never used. Too many teams focus on increasing the amount of output. Not enough teams focus on delivering the most value with the least amount of output. In this interactive presentation, David Hawks will share the key factors that sabotage product success and what to do about it. Learn practical tools and techniques that accelerate learning throughout the product development cycle to deliver double the value in half the time.
Agile Business Analyst - Huong Tran
The document discusses the role of a business analyst in agile projects. It begins by defining the business analyst and their role in understanding business problems and recommending solutions. It then contrasts the traditional vs agile business analyst, noting that agile BAs work iteratively to define requirements in small batches through collaboration rather than upfront documentation. The document also discusses the value of documentation in agile projects and provides examples of an agile requirements hierarchy and the INVEST model for defining requirements. It concludes by listing 8 steps to being an effective agile business analyst.
The BA career from Apprentice to Practice Leader
Slides from a presentation given by Lawrence Darvill to the Midlands branch of IIBA UK on 6 September 2016.
The Power of Story
Slides from a presentation given by Debbie Clement-Large to a meeting of the South-West branch of IIBA UK on 24 November 2016.
Agile Presentation To IIBA MInneapolis
The document is a presentation about the role of a business analyst on an agile project. It begins with an introduction of the presenter and their background and experience. The agenda then outlines topics to be covered, including a brief overview of agile, the role of a business analyst on traditional and agile projects, why business analysts are important, and a question and answer session. It discusses challenges with traditional software development and how agile aims to address these.
Next Generation BA: what new skills and behaviours do BAs need to develop in ...
Slides from a presentation given by Robert Moores to a meeting of IIBA UK's North branch on 21 April 2015
How to Sell Your Creative Talents
This document discusses creativity and innovation. It defines creativity as the generation of new ideas, while innovation is implementing those ideas into action. The document emphasizes that creativity can be learned and developed, not just an innate trait. It provides various techniques to spark creativity, such as brainstorming, reversing perspectives, and designing with intended users. Fostering an environment of freedom, clear goals, and accepting mistakes can encourage creativity. The key is taking time to pause and find new solutions, then following ideas with action through an innovation process.
Viewers also liked (20)
The Decision Model and Notation (DMN) standard - a worked example
The Decision Model and Notation (DMN) standard - a worked example
Business Analysis/Analysts - 'The Past, Present and Future
Business Analysis/Analysts - 'The Past, Present and Future
Agile Velocity - Deliver double the value in half the time
Agile Velocity - Deliver double the value in half the time
Next Generation BA: what new skills and behaviours do BAs need to develop in ...
Next Generation BA: what new skills and behaviours do BAs need to develop in ...
Similar to PCA14: Intro to agile for product managers
Intro to agile for product managers
In this session you will learn what is Agile and how it compares to traditional waterfall development. We will also explore the advantages of Agile for increasing visibility and shortening the feedback loop. Then we will introduce you to Scrum, the most popular agile process improvement framework. We will finish with a description of the Product Owner role and its involvement in Scrum.
David Hawks is a Certified Scrum Coach and Certified Scrum Trainer. He founded Agile Velocity when he noticed companies ineffectively building innovative software products. David brings his broad experience working with Fortune 50 companies and early stage startups to challenge organizations to think differently about how they build software.
Product Management In Agile Practice
1. The document discusses an agenda for an Agile transformation workshop focusing on the product owner role, product backlog grooming, and sprint planning.
2. It describes Scrum roles, ceremonies, and artifacts including the product owner, scrum master, product backlog, sprint backlog, and daily standups.
3. The document provides tips for product owners on prioritizing product backlogs, writing user stories, estimating work, and mapping stories to sprints and releases to help teams adopt Agile practices.
PMI-ACP Agile free sample from EVOLVE
https://evolvetrainingmaterials.com
pmp training materials, pmp training material free download, pmp course material free download pdf, pmp instructor materials, pmbok, pmbok 7th edition, pmbok guide, guide to pmbok, pmbok 6th edition, pmp certification, pmbok pdf, pmbok download, pmp
Evolving Role of Product Manager
This document discusses the evolving role of product managers. Traditionally, product managers acted as gatekeepers who protected engineering teams from business needs and owned product decisions. However, the role is evolving where product managers now act as conduits who connect teams to customers and business needs, facilitate collaboration, and drive outcomes rather than outputs. The document provides examples of how traditional and evolving product managers differ in their approaches to specification, design, delivery, and working with engineering teams. It also introduces a product framework and task brief template for defining and solving product problems.
Agile Practice at MyVisionExpress
The document provides an overview of agile concepts and processes for adopting an agile methodology. It discusses key agile roles like the Scrum Master and Product Owner. It also summarizes agile ceremonies like daily stand-ups, sprint planning, reviews and retrospectives. The document outlines how these concepts were applied in migrating a team to agile using tools like JIRA and managing releases through multiple sprints.
Plan.pptx
The document outlines the product workflow process including research, development, marketing, sales, and integration & testing. It describes an agile methodology used including sprints, product backlogs, and a sprint process model. Key advantages of the agile approach are also listed such as transparency, accuracy, fast development, and less testing.
Managing Product Development Chaos with Jira Software and Confluence
Launching a product can be a herculean task to any team, particularly a product team. With relentless prioritization, requirements revisions, and status reporting, Product Managers are often overwhelmed. It was no different at Square, but one product team decided to try something different.
Ronald Lai, ex Product Manager at Square, will discuss how his team used JIRA Software and Confluence to automate workflows to replace their most time-consuming tasks and focused on creating product value.
Scrum Team Workshop Training Agenda
This 2-day workshop teaches teams how to apply agile and Scrum principles through hands-on simulations and exercises. The workshop covers agile concepts like product vision, user stories, sprint planning, daily stand-ups and retrospectives. Attendees will learn how to establish agile processes, identify bottlenecks, and enhance practices through collaborative teamwork. The trainer has over 18 years experience in agile software development and helping companies successfully adopt agile methods.
The Agile Analyst: Making Agile Methods Work for You
The document discusses how business analysts can succeed working on agile teams. It explains that agile methods are inevitable as more organizations adopt them, and that BAs are needed to help address gaps in requirements, design, and business process knowledge. The document outlines typical activities for BAs on agile teams, such as business modeling, requirements gathering, prioritization, and user acceptance testing. It emphasizes that to succeed, BAs should focus on facilitation over documentation, collaboration over independence, and sufficiency over perfection. BAs are encouraged to shift their focus from documenting requirements to helping customers determine their needs.
Intro To Scrum.V3
Tommy Norman gave a presentation on introducing agile software development using Scrum. He began with an overview of agile principles compared to traditional waterfall development. The key aspects of Scrum were then outlined, including sprint planning, daily standups, product backlog refinement, and sprint reviews and retrospectives. The benefits of agile such as visibility, adaptability, and risk reduction were highlighted. Challenges to adopting agile like management buy-in and organizational change were also discussed. The presentation concluded with next steps around research, training, involvement, and coaching.
Agile Methodology
An agile team works collaboratively in short iterations to develop products. The team is self-organizing and cross-functional, welcoming changing requirements. They identify customer priorities and build products through continuous delivery and testing in two-week sprints. This allows for transparent, progressive development and fast delivery of high quality, satisfying products that meet current needs.
Tech talk - Scrum and XP
Scrum and Extreme Programming (XP) are popular agile frameworks. Scrum uses a framework of roles, events, and artifacts like the product backlog, sprints, daily scrums, and retrospectives. It focuses on transparency, inspection, and adaptation. XP uses values of communication, simplicity, feedback, courage, and respect. Its principles include pair programming, test-driven development, and continuous integration. Both aim to help teams deliver working software frequently through an empirical and people-focused approach.
InterConnect 2016 Continuous Visibility DTA-3268
The document discusses achieving continuous visibility across the DevOps lifecycle. It argues that local optimizations and lack of integration between tools has led to manual processes that slow down delivery. It promotes the use of integration patterns and infrastructure to provide end-to-end visibility by connecting tools across planning, development, testing and operations. This allows for continuous flow, earlier detection of issues, and opportunities for more automation and less variance.
Achieving Continuous Visibility Across the DevOps Lifecycle
The document discusses achieving continuous visibility across the DevOps lifecycle. It argues that local optimizations and lack of integration between tools has led to manual processes that slow down delivery. It promotes the use of integration patterns and infrastructure to provide end-to-end visibility by connecting tools across planning, development, testing and operations. This allows teams to see dependencies, impacts, quality status and automate deployment for less variance and faster delivery.
Webinar de Comunidad Ágil - Rumbo a la certificación Disciplined Agile-SCRUM
¿Su equipo está flotando en el agua usando cascada (waterfall)? ¿Se siente atrapado en un marco ágil? ¿Le gustaría encontrar soluciones a los problemas con los que ha estado luchando? ¿Está buscando formas de mejorar la agilidad de su equipo?
Libérese de sus viejas costumbres eligiendo una forma de trabajo (WoW Way of Working) que se adapte al contexto de su equipo. Encuentre estrategias para mejorar sus procesos y fortalecer su equipo con el kit de herramientas Disciplined Agile.
Disciplined Agile Scrum Master es un curso de nueve lecciones, dirigido por un instructor que le muestra cómo utilizar Disciplined Agile (DA) para mejorar la forma de trabajar de su equipo. En solo dos días, se familiarizará con las prácticas ágiles y esbeltas fundamentales que admite DA, practicará el uso del kit de herramientas para resolver problemas y aprenderá a crear equipos de alto rendimiento.
Lleno de actividades, animaciones, lectura suplementaria y más, este curso le preparará para el examen de Disciplined Agile Scrum Master (DASM) y, igualmente importante, empezar a usar Disciplined Agile inmediatamente.
PMI CH AMM2023 - Bye Bye Project Manager - SwissQ.pptx
For projects like building a power plant or a train tunnel, tough project managers are needed. But when it comes to developing digital or physical products, the role of a project manager has an increasingly difficult standing. During agile or digital transformations, new roles emerge to take over project management tasks. So, are project managers needed in these areas in the future?
Agile foundation online - slide share
This document provides an overview and agenda for an Agile Foundation training session on Scrum, Kanban, and SAFe. The session will cover setting the context for Agile, the Agile Manifesto, Scrum basics, and keywords. It will also discuss Scrum Master certifications and provide a deep dive into Scrum fundamentals and an overview of SAFe. The session aims to be interactive with participation from attendees.
Introduction to Scrum by Manoj Vadakan-conscires agile practices
Agile , What is in it for me Webinar by Manoj and Conscires Agile Practices . An Introduction to Scrum and Agile.
Lean 6 Sigma Training | By ex-Deloitte & McKinsey Consultants
Lean 6 sigma training in Powerpoint | By ex-Deloitte & McKinsey Consultants | Downloadable at www.slidebooks.com | Include re-usable Powerpoint slides, templates, tools and frameworks
Introduction to Agile for Managers
This presentation shows the 12 Agile principles, factors for a successful Agile implementation, and solutions to common implementation issues
Similar to PCA14: Intro to agile for product managers (20)
Managing Product Development Chaos with Jira Software and Confluence
Managing Product Development Chaos with Jira Software and Confluence
The Agile Analyst: Making Agile Methods Work for You
The Agile Analyst: Making Agile Methods Work for You
Achieving Continuous Visibility Across the DevOps Lifecycle
Achieving Continuous Visibility Across the DevOps Lifecycle
Webinar de Comunidad Ágil - Rumbo a la certificación Disciplined Agile-SCRUM
Webinar de Comunidad Ágil - Rumbo a la certificación Disciplined Agile-SCRUM
PMI CH AMM2023 - Bye Bye Project Manager - SwissQ.pptx
PMI CH AMM2023 - Bye Bye Project Manager - SwissQ.pptx
Introduction to Scrum by Manoj Vadakan-conscires agile practices
Introduction to Scrum by Manoj Vadakan-conscires agile practices
Lean 6 Sigma Training | By ex-Deloitte & McKinsey Consultants
Lean 6 Sigma Training | By ex-Deloitte & McKinsey Consultants
More from David Hawks
Agile Leadership
The document discusses problems organizations face and solutions to increase engagement and agility. It addresses three main problems: focusing only on output, a changed workforce, and lack of engagement. To solve these, the document recommends self-organizing teams with autonomy, servant leadership, daily huddles and visual boards for collaboration, and regular retrospectives. This allows teams to prioritize work in a backlog and finish projects through user stories.
Overcome the 6 Traps of Agile
The document is a presentation on overcoming six traps of Agile. It discusses making decisions too early and locking them in. It advocates deferring decisions to the last responsible moment to avoid this trap. It also discusses teams not having a shared understanding of their purpose and advocates shifting from a requirements delivery process to a requirements discovery process through techniques like user story mapping. The presentation provides examples of how to address these common Agile traps.
Pitfalls of an Agile Transformation
The document discusses 10 common pitfalls that can occur during an agile transformation. The first pitfall is thinking agile is just a process change rather than a cultural shift. Other pitfalls include providing no guidance during the transformation, leadership not being properly aligned, transparency being abused, and organizational culture remaining misaligned after the transition to agile. The document stresses the importance of establishing a continuous improvement culture, aligning teams to products and customers, and gaining organizational alignment across the entire company for a successful agile transformation.
SAP Keynote Presentation
The document discusses problems with leadership and engagement in the modern workforce. It proposes that self-organizing teams with servant leaders who support rather than dictate can lead to better outcomes and engagement. Regular retrospectives, visibility of work, and team prioritization of backlogs can help with collaboration, alignment and finishing work to satisfy stakeholders through shortened feedback loops. The key is balancing servant leadership, team ownership and visibility to drive engagement, innovation and improvement.
Agile velocity - Requirements Discovery Presentation
1. The document discusses challenges with user stories and provides strategies for splitting stories into smaller pieces.
2. It then covers how agile practices like Scrum can help with execution and testing, while lean startup practices aid discovery and learning from customers.
3. The key message is that teams should seek to shorten the learning cycle by treating requirements as hypotheses and getting customer feedback quickly through methods like paper prototyping and explainer videos.
Lean Product Discovery
Would you like to be able to increase the adoption rate of your product? In this session, we will introduce you to cutting edge concepts and techniques to shift your product development process from output to outcome driven. We will combine elements of Lean Startup, Product Discovery, and Experiment Driven Development to accelerate learning to quickly build products customer love.
Create User Stories that Don't Suck!
In this interactive workshop, David Hawks will share best practices for writing user stories, acceptance criteria, the INVEST approach, and breaking down user stories. Using these approaches you will be able to effectively convey your vision to the development team so they can output what you want.
KAA: Deliver Double the Value in Half the Time
The document discusses six common traps that teams can fall into when working in an agile way. These traps are: making decisions too early and locking them in; not having a shared understanding of purpose; long or no feedback cycles; being overwhelmed by opportunities; not actually getting to a "done" state for features; and treating everything as equally important. It provides strategies for overcoming each trap, such as deferring decisions, using user story mapping, implementing lean startup and MVP approaches, focusing on highest value work, defining "done" rigorously, and prioritizing work.
Deliver double the value in half the time
The document discusses how to deliver double the value in half the time through agile principles and practices. It identifies common problems such as making decisions too early, long feedback cycles, lack of prioritization, and lack of focus. Solutions proposed include deferring decisions, frequent validation of work, limiting work in progress, focusing on completing work rather than starting new work, and prioritizing the backlog. Adopting these agile practices can help teams deliver 80% of value in 20% of the time.
Agile Austin - Deliver Double the Value in Half the Time
Learn practical techniques to guide your teams and escape the top 6 traps preventing organizations from realizing the full benefits of agile.
64% of product features built in software development are rarely or never used. Too many teams focus on increasing the amount of output. Not enough teams focus on delivering the most value with the least amount of output. In this interactive presentation, David Hawks will share the key factors that sabotage product success and what to do about it. Learn practical tools and techniques that accelerate learning throughout the product development cycle to deliver double the value in half the time.
Deliver Double the Value in Half the Time
This session was presented at the PMI Austin Development Day Conference in Sept 2014. We explore the difference between "Doing Agile" vs. "Being Agile." Establishing a learning culture is critical. Six problems are presented and solutions are shown which lead to the team's ability to deliver double the value in half the time.
Deliver Double the Value in Half the Time - PCA13 - PCATX
64% of product features built in software development are rarely or never used. Too many teams focus on increasing the amount of output, as opposed to focusing on delivering the most value with the least amount of output. In this interactive presentation, David Hawks will share the key factors that sabotage product success and what to do about it. Learn practical tools and techniques that accelerate learning throughout the product development cycle to deliver double the value in half the time.
Presented at ProductCamp Austin 13 on August 2nd, 2014
David Hawks is a Certified Scrum Coach and Certified Scrum Trainer. David guides software organizations to deliver innovative products faster. David brings his broad experience working with Fortune 50 companies and early stage startups to challenge organizations to think differently about how they build products.
KAA How to get your Good agile teams to Great
The document provides tips for getting an agile team from good to great by focusing on outcomes over outputs, allocating time to incremental improvements to reduce technical debt, and limiting work in progress to focus on finishing projects instead of starting new ones in order to deliver value earlier. The presentation also discusses building trust, handling conflicts constructively, establishing team values and policies, and developing team members' breadth and depth of skills.
How to Keep Going Fast - Agile Velocity - Product Camp Austin
Features often get delivered quickly on new software projects and slow to an exponentially slower pace over time. Teams are usually on their own to discover, implement, and even get buy-in for improving the technical capability to deliver. In this session we'll discuss how technical debt accrues and impacts the flow of features over time as well as how Product Owners can encourage and support teams to improve. We will run a simulation of a software project that demonstrates the impact of employing technical practices and addressing other technical debt.
Agile Velocity Story Mapping Session from Product Camp Austin 11 #PCATX
User Story Mapping is a technique for organizing and prioritizing user stories. It addresses challenges with traditional backlogs by providing context and showing relationships between stories. The process shifts from requirements delivery to requirements discovery, recognizing that customers discover wants and developers discover solutions as things change. User story mapping decomposes user tasks into smaller tasks and organizes them into activities to form user stories. It is collaborative and fosters co-ownership by helping understand the user perspective and test for gaps by walking through the map.
Agile Velocity Stop Starting. Start Finishing. PMI - Austin
The document discusses how focusing on finishing work rather than starting new work can improve productivity. It notes that many companies are "drowning in a sea of opportunity" by taking on too much work at once and not completing anything. The document advocates for limiting work in progress to improve flow and focus, balancing demand with throughput, and delivering work frequently to build trust. It provides examples of how multi-tasking reduces efficiency compared to focusing on one task at a time.
Stop Starting. Start Finishing. APLN Houston
The document discusses how companies can improve their technology development processes through adopting Agile and Lean principles. It argues that companies often try to maximize utilization and multi-tasking, which causes waste and slows everything down. Better approaches include focusing on one task at a time to improve flow, limiting work in progress to identify bottlenecks, and balancing demand with throughput. Implementing Kanban techniques like visualizing work and imposing work-in-progress limits can help achieve more efficient flow and frequent delivery of value.
Stop Starting. Start Finishing - ProductCampAustin10 - PCA10
The document discusses how focusing on improving throughput and limiting work in progress can help organizations finish work more quickly. It suggests that companies should balance demand against throughput by throttling input into the system. This will expose bottlenecks and enable the team to try improvements to optimize the whole process and achieve level flow. A Kanban board can be used to visualize and limit work in progress.
More from David Hawks (18)
Agile velocity - Requirements Discovery Presentation
Agile velocity - Requirements Discovery Presentation
Agile Austin - Deliver Double the Value in Half the Time
Agile Austin - Deliver Double the Value in Half the Time
Deliver Double the Value in Half the Time - PCA13 - PCATX
Deliver Double the Value in Half the Time - PCA13 - PCATX
How to Keep Going Fast - Agile Velocity - Product Camp Austin
How to Keep Going Fast - Agile Velocity - Product Camp Austin
Agile Velocity Story Mapping Session from Product Camp Austin 11 #PCATX
Agile Velocity Story Mapping Session from Product Camp Austin 11 #PCATX
Agile Velocity Stop Starting. Start Finishing. PMI - Austin
Agile Velocity Stop Starting. Start Finishing. PMI - Austin
Stop Starting. Start Finishing - ProductCampAustin10 - PCA10
Stop Starting. Start Finishing - ProductCampAustin10 - PCA10
PCA14: Intro to agile for product managers
- 1. INTRO TO AGILE FOR PRODUCT MANAGERS
- 2. Years of AgileExperience David Hawks Agile Velocity Role 12 yrs Name Company Agile Coach david@agilevelocity.com Email Address (If you would like a copy of the slides & to receive periodic information about agile)
- 4. Intro to Agile for Product Managers Why Agile?
- 6. Defined Process Control Model 8
- 7. Empirical Process Control Model 11
- 8. Intro to Agile for Product Managers Marshmallow Challenge
- 11. Agile Requirements Design Development Sprint 1 QA Requirements Design Development Sprint 2 QA Requirements Design Development Sprint 3 QA Requirements Design Development Sprint 4 QA Potentially Releasable Product Increment Working software is the primary measure of progress 18
- 12. Release Burnup 20 40 60 80 2 4 6 8 10 12 Weeks Points Scope Work Complete 19
- 13. Product Owner Responsibilities Product Owner Drives Product Success Creates the Product Vision Creates and Maintains the Product Backlog Collaborates with the Team Collaborates with Stakeholders Participates in Sprint Meetings 25
- 14. Characteristics Required of a PO 26 Knowledge) Authority) Time) )
- 15. 30
- 17. Story Funnel 32
- 18. What is one thing you learned in this session?