The document provides an overview of a workshop on launching agile projects. It includes sections on preparing for the voyage by creating an inception deck covering topics like vision, context and expected outcomes. It also discusses elements to include in the inception deck like an elevator pitch and product box. The document outlines exercises the workshop will cover like creating a NOT list, assumption map and awake list. It describes expected outcomes like choosing an approach, estimating the project size, and determining flexibility. The summary concludes with an exercise for participants to practice one of the workshop elements.
Welcome To The Matrix! Organizational Structures To Support Agile (Keep Austi...Agile Velocity
Traditional organizations focus on roles and controls. If you're a developer, you probably report to a development manager. If you're QA, you probably report to a QA manager. This can lead to some dysfunctions and challenges when you're on an Agile team.
In this session for Keep Austin Agile 2016, Doc List shares real world examples of organizational structures and challenges followed by group discussions where participants categorize their own organization's structures, explore alternatives, and craft a plan for change.
Agile Mumbai 2019 Conference | Right to left | Mike BurrowsAgileNetwork
Session Title : Right to left
Session Overview : What does a Lean-Agile delivery process look like? If you had to describe one, where would you start - "from the left", with a backlog of work to plough through, or "from the right", with needs met by working software? And does the difference in perspective matter?
The difference does indeed matter; we'll see that learning to describe and introduce Agile and its frameworks "from the right" brings considerable benefits. And it's not hard - we can all do it!
Cross-team Pair Testing: Lessons of a Testing Traveler (German Testing Day 2019)Lisi Hocke
Opening keynote for German Testing Day 2019
Abstract:
Did you ever wonder how to improve your testing skills? Well, I did. So I decided to run an experiment. My hypothesis: “I believe that pairing and mobbing with fellow testers from the community on hands-on exploratory testing and automation will result in continuously increasing skills and knowledge as well as serendipitous learning.
I’ll know I have succeeded when I noted down at least one concrete new insight or applied one new technique per testing session and shared that with the community.”
In this talk, I will share the lessons learned on my journey as well as tips for doing pair testing sessions yourself. Let’s uncover if my hypothesis proved true, that a testing tour is indeed a feasible and valuable way to improve your testing knowledge and skills!
Welcome To The Matrix! Organizational Structures To Support Agile (Keep Austi...Agile Velocity
Traditional organizations focus on roles and controls. If you're a developer, you probably report to a development manager. If you're QA, you probably report to a QA manager. This can lead to some dysfunctions and challenges when you're on an Agile team.
In this session for Keep Austin Agile 2016, Doc List shares real world examples of organizational structures and challenges followed by group discussions where participants categorize their own organization's structures, explore alternatives, and craft a plan for change.
Agile Mumbai 2019 Conference | Right to left | Mike BurrowsAgileNetwork
Session Title : Right to left
Session Overview : What does a Lean-Agile delivery process look like? If you had to describe one, where would you start - "from the left", with a backlog of work to plough through, or "from the right", with needs met by working software? And does the difference in perspective matter?
The difference does indeed matter; we'll see that learning to describe and introduce Agile and its frameworks "from the right" brings considerable benefits. And it's not hard - we can all do it!
Cross-team Pair Testing: Lessons of a Testing Traveler (German Testing Day 2019)Lisi Hocke
Opening keynote for German Testing Day 2019
Abstract:
Did you ever wonder how to improve your testing skills? Well, I did. So I decided to run an experiment. My hypothesis: “I believe that pairing and mobbing with fellow testers from the community on hands-on exploratory testing and automation will result in continuously increasing skills and knowledge as well as serendipitous learning.
I’ll know I have succeeded when I noted down at least one concrete new insight or applied one new technique per testing session and shared that with the community.”
In this talk, I will share the lessons learned on my journey as well as tips for doing pair testing sessions yourself. Let’s uncover if my hypothesis proved true, that a testing tour is indeed a feasible and valuable way to improve your testing knowledge and skills!
Presentation about the article 13 Big Ideas from Spotify Engineering Culture https://medium.com/@andrefaria/14-spotify-engineering-culture-big-ideas-cb18f822f9ad
What does a Scrum Master do all day if a Daily Scrum is only 15 minutes? This talk - “A Day in the Life of a Scrum Master” - will explore the role beyond simple facilitation of the Sprint Ceremonies. Attendees learn four different areas of focus for a balanced approach to the role.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2HkIr87.
Justin Becker focuses on the jerk part of “brilliant jerk”. He talks about the Emotional Intelligence and why it matters in developing and operating software systems effectively. He provides opinions and perspective from his experience as an engineer and then manager at Netflix and answers the questions: “what is and why we can’t afford to have a brilliant jerk” and “Am I a brilliant jerk?”. Filmed at qconsf.com.
Justin Becker is an engineering manager for the Playback API team at Netflix. He has worked at Netflix for seven years, the first five years as an engineer. His focus is building scalable, high availability, services running in a cloud environment.
Making choices is hard. As developers, we make choices all the time: architectures, frameworks, libraries, cloud providers, etc. So, if you have been around for a while, you probably ended up regretting at least some of those choices.
In this talk, you will learn how to make choices responsibly and what to look out for if you want to minimize the chance of regretting them later. I dive into several situations where the choices we made as a team have gone horribly wrong. Luckily, I learned these lessons the hard way, so you don’t have to!
Now, if only there was a way to prove your newly acquired skills to your peers and superiors. Well, there is: RAD Certification! I will conclude my talk by telling you about this. And as a bonus, if you get certified during the conference, you can score your RAD certificate and corresponding swag!
How would you build a team from scratch? What techniques would you use? What metrics should you respond to?
In this talk you’ll see how we assembled a team, embedded agile values, a DevOps mindset and a clear purpose to create a squad with an infectious, high performing culture.
We’ll demonstrate the coaching and visualisation techniques we used to reduce batch size and improve quality. You’ll see how to reveal ‘hidden’ product backlogs, make the invisible visible, and use domain driven design, theory of constraints and language to optimise team resilience.
Advanced Topics in Agile Tsting: Focus on Automationlisacrispin
Slide deck for workshop facilitated by Lisa Crispin and Janet Gregory at Quality in Agile Vancouver 2015. Outcomes from the workshop including all the mind maps will appear eventually on lisacrispin.com.
Growing an Experiment-driven Quality Culture (Capgemini TestJam 2021)Lisi Hocke
Keynote given at Capgemini TestJam 2021
You know your own product team needs to improve when it comes to testing and quality, yet you are not sure how to tackle this challenge? Many teams out there feel the need to grow a quality mindset, considering this to be a major stumbling block in their environments. At my current company, tech leadership had a clear mission: improve the testing and quality culture of our product teams by leveling up knowledge, skills and practices. The problem: how to get there?
Experiments to the rescue! In a complex environment like ours, no one could tell what would work, so we had to try things out. I designed an experiment to increase transparency, raise awareness, and especially drive experimentation in individual teams to grow a quality culture. Together with a newly formed working group, I supported four pilot teams to design, run and evaluate their own measurable experiments in their own specific context. These teams tried various approaches like exploratory testing, pair and ensemble testing, or documenting architectural decisions.
In this talk I will share our lessons learned, the outcome and impact of these experiments, and what influenced the next experiments to try. Get inspired by our continuous journey towards making experiments a part of team culture across the company!
Takeaways:
- Understand why small, frugal experiments are crucial in complex environments
- Learn how to design your own measurable experiments, in your team or globally
- Get tips on how to run and evaluate experiments
- Gain insights on how to learn from experiment results and decide on next steps
- Start a movement towards an experiment-driven quality culture
Project Retrospectives are an important part of any software development process. The Principles Behind the Agile Manifesto state that, "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." How can this be done? By taking the time to reflect and learn and proactively determine what should be done differently in the next iteration, release, or project. Linda's presentation will introduce techniques for project retrospectives, whether they are agile or not. The techniques help teams discover what they’re doing well so that successful practices can continue and identify what should be done differently to improve performance. Retrospectives are not finger pointing or blaming sessions, but rather a highly effective process in which teams reflect on the past to become more productive in the future. Linda will share her experiences with leading retrospectives of several kinds for dozens of projects—successful and unsuccessful, small and large, in academia and industry. Her lessons learned can be applied to any project to enable teams and organizations to become learning organizations.
The 5 Biggest Productivity Blockers (And How to Fix Them)Atlassian
Why is being productive so difficult? Turns out, the odds are against you: there are countless barriers preventing you from being your most productive self.
This session will explore the proven scientific solutions to help you better prioritize, manage time, focus, get feedback, and ultimately, stop feeling so overwhelmed.
Growing an Experiment-driven Quality Culture (QS-Barcamp 2021)Lisi Hocke
Keynote given at QS-Barcamp 2021
You know your own product team needs to improve when it comes to testing and quality, yet you are not sure how to tackle this challenge? Many teams out there feel the need to grow a quality mindset, considering this to be a major stumbling block in their environments. At my current company, tech leadership had a clear mission: improve the testing and quality culture of our product teams by leveling up knowledge, skills and practices. The problem: how to get there?
Experiments to the rescue! In a complex environment like ours, no one could tell what would work, so we had to try things out. I designed an experiment to increase transparency, raise awareness, and especially drive experimentation in individual teams to grow a quality culture. Together with a newly formed working group, I supported four pilot teams to design, run and evaluate their own measurable experiments in their own specific context. These teams tried various approaches like exploratory testing, pair and ensemble testing, or documenting architectural decisions.
In this talk I will share our lessons learned, the outcome and impact of these experiments, and what influenced the next experiments to try. Get inspired by our continuous journey towards making experiments a part of team culture across the company!
Takeaways:
- Understand why small, frugal experiments are crucial in complex environments
- Learn how to design your own measurable experiments, in your team or globally
- Get tips on how to run and evaluate experiments
- Gain insights on how to learn from experiment results and decide on next steps
- Start a movement towards an experiment-driven quality culture
The 7 Secrets of Highly Effective Retrospectives (DCSUG)Excella
Slides from the DC Scrum User Group event on 4/25/2016 titled, "The 7 Secrets of Highly Effective Retrospectives" by David Horowitz.
http://www.meetup.com/DC-Scrum/events/228807928/
Retrospectives are the core of agility. And yet they are often the scrum ceremony that is most frequently skipped. Many teams like the idea of the retrospective but find them boring, or worse ineffective.
Join Retrium CEO and Co-Founder David Horowitz as he reveals seven secrets that lead to effective retrospectives. You'll learn:* The best way to ensure your retrospectives lead to real change* The "pledge" everyone on your team must take before participating* How to know who to include in each retrospective* The single most important thing you can do to keep your team engaged during the retro* And much, much more!
How would we define Scrum? How could we convince people to do Scrum? I believe that agreements are more powerful than rules. I also believe that Scrum implements patterns that most of us have experienced in our own most successful projects. Let's test that belief and see how we can apply that to facilitating Scrum adoption. During this interactive workshop, we:
• Share and reflect on the experiences from our own best projects
• Look for patterns in those projects
• Compare Scrum with our own best experiences
• Explore an agreement-based adoption strategy
The workshop also includes some additional food for thought: What if we considered the Scrum Flow as a series of opportunities to ask ourselves powerful questions?
Slides from a 5/10/2017 talk at the Nasdaq Entrepreneurial Center (@theCenter) about a lean research mindset, the mechanics of learning from users, and the structure of a research prototype test session.
Presentation about the article 13 Big Ideas from Spotify Engineering Culture https://medium.com/@andrefaria/14-spotify-engineering-culture-big-ideas-cb18f822f9ad
What does a Scrum Master do all day if a Daily Scrum is only 15 minutes? This talk - “A Day in the Life of a Scrum Master” - will explore the role beyond simple facilitation of the Sprint Ceremonies. Attendees learn four different areas of focus for a balanced approach to the role.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2HkIr87.
Justin Becker focuses on the jerk part of “brilliant jerk”. He talks about the Emotional Intelligence and why it matters in developing and operating software systems effectively. He provides opinions and perspective from his experience as an engineer and then manager at Netflix and answers the questions: “what is and why we can’t afford to have a brilliant jerk” and “Am I a brilliant jerk?”. Filmed at qconsf.com.
Justin Becker is an engineering manager for the Playback API team at Netflix. He has worked at Netflix for seven years, the first five years as an engineer. His focus is building scalable, high availability, services running in a cloud environment.
Making choices is hard. As developers, we make choices all the time: architectures, frameworks, libraries, cloud providers, etc. So, if you have been around for a while, you probably ended up regretting at least some of those choices.
In this talk, you will learn how to make choices responsibly and what to look out for if you want to minimize the chance of regretting them later. I dive into several situations where the choices we made as a team have gone horribly wrong. Luckily, I learned these lessons the hard way, so you don’t have to!
Now, if only there was a way to prove your newly acquired skills to your peers and superiors. Well, there is: RAD Certification! I will conclude my talk by telling you about this. And as a bonus, if you get certified during the conference, you can score your RAD certificate and corresponding swag!
How would you build a team from scratch? What techniques would you use? What metrics should you respond to?
In this talk you’ll see how we assembled a team, embedded agile values, a DevOps mindset and a clear purpose to create a squad with an infectious, high performing culture.
We’ll demonstrate the coaching and visualisation techniques we used to reduce batch size and improve quality. You’ll see how to reveal ‘hidden’ product backlogs, make the invisible visible, and use domain driven design, theory of constraints and language to optimise team resilience.
Advanced Topics in Agile Tsting: Focus on Automationlisacrispin
Slide deck for workshop facilitated by Lisa Crispin and Janet Gregory at Quality in Agile Vancouver 2015. Outcomes from the workshop including all the mind maps will appear eventually on lisacrispin.com.
Growing an Experiment-driven Quality Culture (Capgemini TestJam 2021)Lisi Hocke
Keynote given at Capgemini TestJam 2021
You know your own product team needs to improve when it comes to testing and quality, yet you are not sure how to tackle this challenge? Many teams out there feel the need to grow a quality mindset, considering this to be a major stumbling block in their environments. At my current company, tech leadership had a clear mission: improve the testing and quality culture of our product teams by leveling up knowledge, skills and practices. The problem: how to get there?
Experiments to the rescue! In a complex environment like ours, no one could tell what would work, so we had to try things out. I designed an experiment to increase transparency, raise awareness, and especially drive experimentation in individual teams to grow a quality culture. Together with a newly formed working group, I supported four pilot teams to design, run and evaluate their own measurable experiments in their own specific context. These teams tried various approaches like exploratory testing, pair and ensemble testing, or documenting architectural decisions.
In this talk I will share our lessons learned, the outcome and impact of these experiments, and what influenced the next experiments to try. Get inspired by our continuous journey towards making experiments a part of team culture across the company!
Takeaways:
- Understand why small, frugal experiments are crucial in complex environments
- Learn how to design your own measurable experiments, in your team or globally
- Get tips on how to run and evaluate experiments
- Gain insights on how to learn from experiment results and decide on next steps
- Start a movement towards an experiment-driven quality culture
Project Retrospectives are an important part of any software development process. The Principles Behind the Agile Manifesto state that, "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." How can this be done? By taking the time to reflect and learn and proactively determine what should be done differently in the next iteration, release, or project. Linda's presentation will introduce techniques for project retrospectives, whether they are agile or not. The techniques help teams discover what they’re doing well so that successful practices can continue and identify what should be done differently to improve performance. Retrospectives are not finger pointing or blaming sessions, but rather a highly effective process in which teams reflect on the past to become more productive in the future. Linda will share her experiences with leading retrospectives of several kinds for dozens of projects—successful and unsuccessful, small and large, in academia and industry. Her lessons learned can be applied to any project to enable teams and organizations to become learning organizations.
The 5 Biggest Productivity Blockers (And How to Fix Them)Atlassian
Why is being productive so difficult? Turns out, the odds are against you: there are countless barriers preventing you from being your most productive self.
This session will explore the proven scientific solutions to help you better prioritize, manage time, focus, get feedback, and ultimately, stop feeling so overwhelmed.
Growing an Experiment-driven Quality Culture (QS-Barcamp 2021)Lisi Hocke
Keynote given at QS-Barcamp 2021
You know your own product team needs to improve when it comes to testing and quality, yet you are not sure how to tackle this challenge? Many teams out there feel the need to grow a quality mindset, considering this to be a major stumbling block in their environments. At my current company, tech leadership had a clear mission: improve the testing and quality culture of our product teams by leveling up knowledge, skills and practices. The problem: how to get there?
Experiments to the rescue! In a complex environment like ours, no one could tell what would work, so we had to try things out. I designed an experiment to increase transparency, raise awareness, and especially drive experimentation in individual teams to grow a quality culture. Together with a newly formed working group, I supported four pilot teams to design, run and evaluate their own measurable experiments in their own specific context. These teams tried various approaches like exploratory testing, pair and ensemble testing, or documenting architectural decisions.
In this talk I will share our lessons learned, the outcome and impact of these experiments, and what influenced the next experiments to try. Get inspired by our continuous journey towards making experiments a part of team culture across the company!
Takeaways:
- Understand why small, frugal experiments are crucial in complex environments
- Learn how to design your own measurable experiments, in your team or globally
- Get tips on how to run and evaluate experiments
- Gain insights on how to learn from experiment results and decide on next steps
- Start a movement towards an experiment-driven quality culture
The 7 Secrets of Highly Effective Retrospectives (DCSUG)Excella
Slides from the DC Scrum User Group event on 4/25/2016 titled, "The 7 Secrets of Highly Effective Retrospectives" by David Horowitz.
http://www.meetup.com/DC-Scrum/events/228807928/
Retrospectives are the core of agility. And yet they are often the scrum ceremony that is most frequently skipped. Many teams like the idea of the retrospective but find them boring, or worse ineffective.
Join Retrium CEO and Co-Founder David Horowitz as he reveals seven secrets that lead to effective retrospectives. You'll learn:* The best way to ensure your retrospectives lead to real change* The "pledge" everyone on your team must take before participating* How to know who to include in each retrospective* The single most important thing you can do to keep your team engaged during the retro* And much, much more!
How would we define Scrum? How could we convince people to do Scrum? I believe that agreements are more powerful than rules. I also believe that Scrum implements patterns that most of us have experienced in our own most successful projects. Let's test that belief and see how we can apply that to facilitating Scrum adoption. During this interactive workshop, we:
• Share and reflect on the experiences from our own best projects
• Look for patterns in those projects
• Compare Scrum with our own best experiences
• Explore an agreement-based adoption strategy
The workshop also includes some additional food for thought: What if we considered the Scrum Flow as a series of opportunities to ask ourselves powerful questions?
Slides from a 5/10/2017 talk at the Nasdaq Entrepreneurial Center (@theCenter) about a lean research mindset, the mechanics of learning from users, and the structure of a research prototype test session.
During the Agile adoption, its a common complain that many team in many organizations get caught up in the ceremonies or mechanics of Agile and fail to understand/appreciate the true value and spirit of Agile. And because of this, the original intent of the Agile movement itself is lost. This is a serious issue!
This workshop will highlight, a well-proven approach to transformation (not adoption) and show the distinct steps in this journey that an individual or a collective goes through when learning anything new. Activities, serving as examples, in the workshop, will focus to show the journey - that is, how to begin with rituals, then gradually move to practices, arriving at principles and eventually internalizing the values. Witnessing this gradual process of transformation will help participants discover for themselves their current progression. We hope this will serve as a guiding light during their Agile journey.
Finally, we will leave the participants to ponder upon and discover for themselves their ideals in life and work as this is not only applicable to software development, but also to any discipline where humans are involved, including life itself.
Designing for Agile Delight! Customer Obsessed Innovation at IntuitAtlassian
Innovating effectively in an Agile environment is no easy feat. Learn how Intuit applies an innovation culture and their own "Design for Delight" (D4D) process to deliver and enhance their enterprise agility program—and keep both internal teams and customers happy.
Explore this unique process around customer-driven innovation, deep customer empathy, and how to navigate rapid iterations with customers. Learn about how they applied their agile D4D process to solve key customer problems, and leave with the knowledge of how to deliver both features and customer delight.
Agile Topics - Explained Simply - Practical Agilist.pptxBrian Link
I've put together this simple deck chock full of helpful tips and reminders about things like: running healthy standups, writing effective user stories, improving your backlog refinement and maintenance, focusing on getting value from sprint reviews, using retros to your greatest advantage, getting better at applying strategy using OKRs and roadmaps to align your backlog, and the importance of understanding why agile even works by studying the seven key mindsets and cultures that make up the Agile Mindset.
Agile teams operate in the context of an organization, whether it's a small start-up or a global corporation. Organizations that are clear about why they are in business will have a mission identified that expresses what they're all about. A great mission can provide the spice that transforms a team from one that delivers features and projects, to one that passionately delivers business value with fire-breathing intensity. This session will explore how you can utilize the mission of an organization to spice up a team's work, and how a team with a great mission behind it can influence agility throughout an organization.
The people who will succeed today are those who figure out how to benefit from, or take advantage of, continuous disarray, disorder and disruption. In this webinar, Bill Jensen will identify the habits most necessary for success in today’s world full of disruption. Attendees will learn from disruptive heroes about how they have become masters of disruption simply because they refuse to accept the status quo.
Attendees of this webinar will learn:
Five habits most necessary for success in a disruptive world.
The how-tos and why-musts of disruption.
Key lessons from disruptive heroes about how they are changing the game.
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
Agile in Action - Agile Overview for DevelopersMatt Cowell
Excerpt from a presentation I gave to the University of Alabama Association for Computing Machinery in November 2010. I wanted to give the students a practical overview of Agile and Scrum and give them some perspective on what Agile means for developers.
Boston UXPA 2016 | What’s Worse: A Root Canal or Selecting Health InsuranceBecky Minervino
Why is selecting Health Insurance so painful? From the myriad of carrier choices to the endless amount of forms to the lack of transparency around what you’re are signing up for, the complexity around benefits selection is frustrating for both employees and employers. In order to make this process easier for everyone involved, Fidelity and BEAM set out to re-design this experience — taking an agile and collaborative approach to understanding how to make the process of selecting and managing health insurance better.
We'll talk about how we leveraged a variety of best practices and user-centered approaches to tackle this complex problem. This includes:
• Understanding the different constituents within the current Health Insurance experience: employees, employers, brokers and carriers;
• Our approach to understanding individual needs through interviews with benefits administrators across a variety of organizations;
• Distilling findings and incorporating design-sprints to arrive at “just enough” concepts en route to a full MVP;
• Validating concepts through prototyping and co-design with users to refine the experience;
• What worked well and what we are doing for the next phase of work.
Why Are We Stuck? Getting Agile Teams On The Path To Continuous ImprovementAgile Velocity
When things are going well, it is difficult to find motivation to go from good to great.
As an Agile leader, it’s important to be able to identify the symptoms your team or team-of-teams start to exhibit when they get stuck – when their momentum for positive growth and change stalls or plateaus – and what to do about it.
Presented at Global Scrum Gathering Minneapolis, this session was a highly interactive workshop with group discussions, table talks and concept centers that provided you with a toolbox to identify symptoms of a stuck team, determine why they are stuck, activities to get them unstuck and highlight potential dysfunctions and over-correction patterns.
Similar to Launching agile projects slide handout (20)
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.
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.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
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.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
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.
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.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
2. Crew Training Exercise
What Shall We Do With a Drunken Sailor?
2
Shave his belly with a rusty razor Put him in the hold with the Captain’s daughter
Put him in the scuppers with a hosepipe on him
What Shall We Do With an Agile Sailor?
Give him a sharpie and stacks of Post-its Tell her to limit the work in process
10 Syllable Phrases
Send all the team for a stand-up meeting
Exercise Music: ‘Drunken Sailor’ – Carl Peterson
3. Prepared exclusively for Richard Freeman
oad from Wow! eBook <www.wowebook.com>
Download the workshop materials - slides, examples and templates
4. Preparing for the Voyage
The Inception Deck
• The Bigger Picture
• What are we doing?
• What can we expect?
5. What’s in The Inception Deck
• The Bigger Picture?
• Vision, Context
• What Are We Being Asked To Do?
• Our current thinking on solution
• What Should We Expect?
• What do we think will happen?
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Awake ListThese are the things we are are worried may
keep us awake at night
What are the things that you personally are worrying about? This
is more than
just project risks. Include non-technical factors like people, facilities, processes,
skills, other demands on your time, office politics, etc. Discuss amongst the
team
what you can do about them
.
@simongirvan
Base
d on ideas from
“The
Agile
Samurai”, by Jona
than
Rasm
ussan
Assumption Map
Have
Evidence
Brainstorm all your assumptions and map onto the
horizontal axis first.
Then, map onto vertical axis ands decide what to do!
@simongirvan
No
Evidence
Important
Not
Important
Based on ideas from by @davidjbland, @danto_ma and @AlexOsterwalder.
6. The Bigger Picture?
• Who is this for?
• Why Are We Here statement.
• Elevator Pitch
• Product Box
7. Why Are We Here?
•What do we know about the project and its history?
• Who are the primary stakeholders?
• What is the business driver?
• What’s the relevant history?
• Who are the board level sponsors, etc
• Where is this work in corporate priorities
• (How will we know if things change?)
8. Elevator Pitch
For [users]
who [statement of need or opportunity]
the [thing we are creating]
is a [product category]
that [key benefit, compelling reason to buy].
Unlike [current solution or a competitor]
Our Product [statement of primary differentiation].
9. Elevator Pitch Example
For Pirates
who Need a new or additional parrot
the ‘Parrots Arrr Us’ Website
is a Pirate and Parrot matching service
that finds a parrot to perfectly match your needs
Unlike stealing one from another pirate
Our Product removes the risk of revenge attacks or a bad bird
11. Crew Training Exercise
• For your project, either
Write The Elevator Pitch, or
Design a Product Box
5
Elevator Pitch Template
Target customer
For
Who
Our Product Is
Customer need, opportunity or current dissatisfaction
That
Key benefit for this customer
Unlike
Alternative solution or competition
Our
Product
Product category - what your product will actually do
Why it meets the need better than the alternative@simongirvan
Based on a format from “Crossing The Chasm” by Geoffrey Moore
Time Remaining…
Exercise Music: ‘Turkish Revelry’ – Loudon Wainwright III
13. Our ‘Why Are We Here’
• On a personal level, we want to develop ourselves
• We want to reach Certified Team Coach® level with Scrum Alliance
• Running workshops and facilitating large groups is good evidence
• This is a good professional challenge for us both
• We are passionate about sharing our experiences and want others to
get good results from these approaches too
• The submission has been accepted, so it will definitely go ahead (low
risk of being cancelled)
14. Our ‘Elevator Pitch’ 1
For people at this Agile conference
who want to learn new techniques and how to apply them
the Launching Agile Projects Workshop
is an interactive and informative workshop
that is hands-on, fun and useful
Unlike other ways to learn
Our Product allows participants to immerse themselves in the
material, embedding the learning more effectively
15. Our ‘Elevator Pitch’ 2
For people at this Agile conference
who want to learn new techniques and how to apply them
the Launching Agile Projects Approach
is a way of preparing for the start of a project
that helps teams get sufficient knowledge to start a project
Unlike other project start-up techniques
Our Product is a lightweight approach that uses a just enough, just
in time philosophy
17. What are we doing?
• The NOT List
• Meet The Neighbours
• Assumption Map
• Candidate Solution
• Awake List
• Agile Wheel of Pain
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Awake ListThese are the things we are are worried may
keep us awake at night
What are the things that you personally are worrying about? This is more than
just project risks. Include non-technical factors like people, facilities, processes,
skills, other demands on your time, office politics, etc. Discuss amongst the
team what you can do about them.
@simongirvan
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
Assumption Map
Have
Evidence
Brainstorm all your assumptions and map onto the
horizontal axis first.
Then, map onto vertical axis ands decide what to do!
@simongirvan
No
Evidence
Important
Not
Important
Based on ideas from by @davidjbland, @danto_ma and @AlexOsterwalder.
In Scope
Not In Scope
Unsure
The NOT List
These are the things that you are certain are in scope for the project
These are the things that you are certain are NO
T in scope for the project
These are the things that you aren’t sure whether they are in scope or not in scope.
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
@simongirvan
18. In Scope Not In Scope
Unsure
The NOT List
These are the things that you are certain are in scope for the project These are the things that you are certain are NOT in scope for the project
These are the things that you aren’t sure whether they are in scope or not in scope.
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
@simongirvan
20. Assumption Map
Have
Evidence
Brainstorm all your assumptions and map onto the
horizontal axis first.
Then, map onto vertical axis ands decide what to do!
@simongirvan
No
Evidence
Important
Not
Important
Based on ideas from by @davidjbland, @danto_ma and @AlexOsterwalder.
22. 1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Awake List
These are the things we are are worried may
keep us awake at night
What are the things that you personally are worrying about? This is more than
just project risks. Include non-technical factors like people, facilities, processes,
skills, other demands on your time, office politics, etc. Discuss amongst the
team what you can do about them.
@simongirvan
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
23. Wheel of Pain
For each factor on the wheel, ask:
How does this factor help you work
with an agile mindset?
0 - It’s a perfect fit!
1 - It really helps us
2 - It’s OK
3 - It makes it difficult
4 - It makes it really hard
5 - It makes it almost impossible
24. Crew Training Exercise
• For your project (or ours), pick one of these
•NOT List
•Awake List
•Wheel of Pain In Scope Not In Scope
Unsure
The NOT List
These are the things that you are certain are in scope for the project These are the things that you are certain are NOT in scope for the project
These are the things that you aren’t sure whether they are in scope or not in scope.
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
@simongirvan
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Awake List
These are the things we are are worried may
keep us awake at night
What are the things that you personally are worrying about? This is more than
just project risks. Include non-technical factors like people, facilities, processes,
skills, other demands on your time, office politics, etc. Discuss amongst the
team what you can do about them.
@simongirvan
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
5
Time Remaining…
Exercise Music: ‘Rolling Sea’ – Eliza Carthy
26. In Scope Not In Scope
Unsure
The NOT List
These are the things that you are certain are in scope for the project These are the things that you are certain are NOT in scope for the project
These are the things that you aren’t sure whether they are in scope or not in scope.
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
@simongirvan
• Full Coverage of both Inception
Deck
• Limited coverage of LiftOff and
Chartering
• Exercises and Practical content
• Templates and Hand Outs
• Meaningful Examples
• Rehearse with at least one group
• Materials can be reused for other
events
• Exercises for all elements
• Feedback from every group
• Detailed discussion of each
element
• How to deal with detailed questions during the main sections
• Downloadable Resources?
• How far to go down the pirate route wrt costume, etc
28. Our Assumption Map
Assumption Map
Have
Evidence
Brainstorm all your assumptions and map onto the
horizontal axis first.
Then, map onto vertical axis ands decide what to do!
@simongirvan
No
Evidence
Important
Not
Important
Based on ideas from @davidjbland, @danto_ma and @AlexOsterwalder.
There is
demand for this
workshop
Technique
has merit
Technique
is portable
Workshop
format is good
enough for
learning
Room
layout is
suitable
Exercise
choices are
suitable
People haven’t
heard much of
this before
Weighting
between ID
and LO is
OK
Weighting
between
content and
exercises is OK
Two presenters
are better than
one
Timeslot allocated
is conducive to the
workshop format
Pirate theme is
appropriate
30. 1. Fitting in everything we want in the
time that we have
2. Having enough time to prepare
3. Will the exercises be useful?
4. Will people actually take part in the
exercises
5. Is the split right between the Inception
Deck and Liftoff?
Awake List
These are the things we are are worried may
keep us awake at night
31. Our ‘Wheel of Pain’
We are not based in same location so plan
at least 2 workshops where we can work
together. Use online collaboration tools.
There is a lot of information to try to get
across. Use pilot groups to test format.
Create templates and handouts to help
attendees remember the content.
32. What Should We Expect?
• Choose Your Approach
• How Big Is This Ship?
• What’s Gonna Give?
• The Final Test
What’s Gonna Give? Decide the extent to which you expect each factor to
be flexible or fixed.
If too many are too fixed, consider forcing a minimum
number of points (say 10 if scoring 4 factors)
@simongirvan
Deliver AllThe Features
Based on an idea from “The Agile Samurai” by Jonathan Rasmusson
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
Stay OnBudget
Can be flexibleon this
Must dothis
Deliver on
Time
Deliver HighQuality
Others may include Useability, Security, Supportability, Accessibility, etc. If they matter to you or your stakeholders include them!
Must
Must
Must
Must
Must
Must
33. Choose Your Approach
How will we manage and
govern the project?
How will we
communicate with
stakeholders?
• Agile using Scrum
• 2 week Sprints
• Visible Backlog
• MMP as first release as early as
possible• All stakeholders invited to
Review/Demo• Real users from version 1 onwards
• Monthly update to Board
34. How Big Is This Ship? (Size It Up)
• Best guess rough estimate of size and duration
• Initial estimate of the team required to do this
Sprint 0
2 Senior Engineers
0.5 Infrastructure
MMP
Development
Standard Agile team
including BA, UX and
Architecture experience
Releases 2-n
Standard Agile team, including higher
level devops and test experience
2 Weeks 4 – 6 weeks
8 – 12 weeks
Start Developing in 2 weeks
MMP 4 – 6 weeks later
4-6 further versions
Team size 2-7
ROM Cost £180-£270k
ROM Duration 3 – 5 months
35. What’s Gonna Give?
Fixed Flexible
Feature Completeness
Usability
Security
Support
Accessibility
1 2 3 4 5
Stay on Budget
Deliver on Time
Deliver High Quality
Others?
36. The Final Test
Do we know enough about the project to
be sure that we know:
• What we are being asked to do;
• Why it is needed; and
• How we are going to start?
Do We Know Enough To Start Work?
37. Crew Training Exercise
• For your project,
Decide What’s Gonna Give
What’s Gonna Give? Decide the extent to which you expect each factor to
be flexible or fixed.
If too many are too fixed, consider forcing a minimum
number of points (say 10 if scoring 4 factors)
@simongirvan
Deliver All
The Features
Based on an idea from “The Agile Samurai” by Jonathan Rasmusson
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
Stay On
Budget
Can be flexible
on this
Must do
this
Deliver on
Time
Deliver High
Quality
Others may include Useability, Security, Supportability, Accessibility, etc. If they matter to you or your stakeholders include them!
Must
Must
Must
Must
Must
Must
3
Time Remaining…
Exercise Music: ‘Lighthouse’ – The Waifs
39. Our ‘Choose Your Approach’
• Adhoc planning approach
• Collaborative online and in person
• Iterative – low detail to start
• Keep actions in Teams
• Content on Sharepoint
• No formal reporting
40. Our ‘How Big Is This Ship?’
Inception Deck
Good Enough for
Rehearsal
Include reviewers and
pilot workshop attendees
By end Jan 2019 By end Feb 2019 By end March
4 months duration
17 days effort (8.5 each)
Less than £100
First
Rehearsal
Revise and
more rehearsal
Prep &
Deliver
Preferably at least
one more
runthrough
Order print
materials
During April 10 May
2019
41. What’s Gonna Give? Decide the extent to which you expect each factor to
be flexible or fixed.
If too many are too fixed, consider forcing a minimum
number of points (say 10 if scoring 4 factors)
@simongirvan
Deliver All
The Features
Based on an idea from “The Agile Samurai” by Jonathan Rasmusson
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
0 1 2 3 4 5
Stay On
Budget
Can be flexible
on this
Must do
this
Deliver on
Time
Deliver High
Quality
Others may include Useability, Security, Supportability, Accessibility, etc. If they matter to you or your stakeholders include them!
Must
Must
Must
Must
Must
Must
Clarity of
Message
Portable
Ongoing
Support
42. Our ‘Final Test’
We do know enough about this project:
• We know what’s required to have enough
material available to present;
• We know how we intend to test it;
• We know what the first steps are.
We are ready to start!
43. Summary of the Inception Deck
• Why Are We Here:
• Why are we here?
• Elevator Pitch
• Product Box
What Can You Expect?
• Choose Your Approach
• Size it Up
• What’s Gonna Give?
• The Final Test
What Are We Being Asked To Do?
• The NOT List
• Meet The Neighbours
• Assumption Map
• Candidate Solution
• Awake List
• Wheel of Pain
In Scope Not In Scope
Unsure
The NOT List
These are the things that you are certain are in scope for the project These are the things that you are certain are NOT in scope for the project
These are the things that you aren’t sure whether they are in scope or not in scope.
Based on ideas from “The Agile Samurai”, by Jonathan Rasmussan
@simongirvan
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Awake ListThese are the things we are are worried may
keep us awake at night
What are the thing
s that you personally are worrying
abou
t? This
is more
than
just proje
ct risks. Inclu
de non-technical
facto
rs like peop
le, facilities,
processes,
skills
, other demands
on your
time, office politics, etc. Discuss amongst
the
team
what
you can do abou
t them
.
@sim
ongirvan
Based
on ideas
from
“The
Agile
Samu
rai”, by Jonat
han Rasm
ussan
What’s Gonna Give?
Decide the
extent to which
you expect each factor to
be flexible or fixe
d.
If too
many are
too
fixe
d, consider forcing a minim
um
number of points (say 10 if sco
ring 4 factors)
@simongirvan
Deliver All
The Features
Bas
ed on an idea from
“Th
e Agile Sam
urai” by Jon
athan Ras
musso
n
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
0
1
2
3
4
5
Stay On
Budget
Can be
flexib
le
on
this
Mu
st do
this
Deliver on
Time
Deliver High
Quality
Oth
ers
may include Use
ability,
Sec
urity, Sup
portability, Acc
essibility, etc. If they matter
to you
or you
r stakeh
olders
include them!
Mu
st
Mu
st
Mu
st
Mu
st
Mu
st
Mu
st
Assumption Map
Have
Evidence
Brains
torm all your assum
ptions
and map onto the
horizontal axis first.
Then, map onto vertical axis ands decide what to do!
@simongirvan
No
Evidence
Important
Not
Important
Based
on ideas from by @david
jbland,
@danto
_ma and @AlexO
sterwa
lder.
48. Purpose
Elevator Pitch Template
Target customer
For
Who
Our Product Is
Customer need, opportunity or current dissatisfaction
That
Key benefit for this customer
Unlike
Alternative solution or competition
Our
Product
Product category - what your product will actually do
Why it meets the need better than
the alternative
@simongirvan
Based on
a format from “Crossing
The Chasm” by
Geoffrey Moore
Exercises and Artefacts that help the
team understand why their work
matters, and connects them to the
strategy and vision
49. The first choice website for pirates
across the seven seas
• We will understand what our customers need and develop our
services to meet a growing range of pirate needs, starting with
parrots.
• We will make the “Parrots Arrrr Us” website the first port of call for
pirates everywhere.
• We will make the “Parrots Arrrr Us” website accessible for pirates
with disabilities.
• We will be easy for our suppliers to do business with
Vision and Team Mission Examples
50. Crew Training Exercise
5
Time Remaining…
•In groups of 2/3,
Identify Mission Tests
• We will understand what our customers need and develop our
services to meet a growing range of pirate needs, starting with
parrots.
• We will make the “Parrots Arrrr Us” website the first port of call for
pirates everywhere.
• We will make the “Parrots Arrrr Us” website accessible for pirates
with disabilities.
• We will be easy for our suppliers to do business with
Exercise Music: ‘Fisherman’s Daughter’ – The Waifs
52. Mission Tests Example
• The first version of the Parrots Arrrr Us website is
accessible from each of the seven seas.
• By 6 months parrots can be delivered to each of the 7
seas.
• The first version of the website is usable by Pirates with
one hook arm and one eye patch.
• By 6 months, the website is fully accessible to
international standards (WCAG 2.0)
• By 9 months, at least one additional product or service has
been launched.
53. Alignment
Exercises and Artefacts that help the
team understand each other, and how
they can each make their maximum
contribution to the project
54. Simple Rules Example
Integrity - We do what we say we will do
Ingenuity – We collaborate to help us come up with
the best ideas
Impact – Everything we do results in value for the
customer
Teamwork – We look out for each other and always
offer to help
55. Working Agreement Example
• We don’t work on anything that isn’t on the Sprint
Backlog
• Our calendars are always be up to date with our
location and attendance
• All our meetings are meaningful – No meeting
purpose, No Meeting
• We have fun and don’t take ourselves too seriously
• We respect each other’s quiet time – headphones on
means no interruptions.
As a team, we work together best when…
56. Crew Training Exercise
5Time Remaining…
Exercise Music: ‘Thousands are Sailing’ – The Pogues
•In groups of 2/3,
Create a Working Agreement
•Brainstorm how your worst team imaginable behaves
•Identify one or two things that actually might happen
•Write one up as a Team Agreement
• We work best together when…
58. Context
Assumption Map
Have
Evidence
Brains
torm all your assum
ptions
and map onto the
horizontal axis first.
Then, map onto vertical axis ands decide what to do!
@simongirvan
No
Evidence
Important
Not
Important
Based
on ideas from by @david
jbland,
@danto
_ma and @AlexO
sterwa
lder.
Exercises and Artefacts that help the
team understand the external
environment and what they require of
others in order to succeed.
60. Committed Resources
These are the resources that the team need or
want to help them deliver the product
Based on ideas from “Liftoff”, by Diana Larson and Ainsley Nies
Committed Resource Priority
(M/S/C)
✔ AWS Hosting and storage M
✔ Travel Budget M
✔ Stationary Budget M
Training S
✔ Software Licence Upgrades C
Conference Attendance C
4k Monitors C
✔ Access to end users S
All Stakeholders at Sprint Reviews S
61. Prospective Analysis Imagine all the possible events that could happen over
the next few months, both positive and negative.
Assess their impact (positive and negative) on the
project and the likelihood of them happening. Be bold.
@simongirvanProbability
Won’t Happen
Based on ideas from “Liftoff”, by Diana Larson and Ainsley Nies
Unlikely 50/50 Chance Likely Will Happen
Impact
-3
-2
-1
0
3
2
1 Website V1 live
on June 1
Livestock license
rejected
First Successful
Order
Completed by
15 June
Process
orders from
Region 1
Delivery to all 7
seas available
Approval for
next project
idea
Problems
delivering to
certain areas
Full seven seas
service available
in version 1
Competitor will
launch before
we do
Idea is copied
by competitor
62. Summary
• Inception Deck and Liftoff are similar
but complementary
• Use Inception Deck to clarify a
project scope and manage
expectations from the outset
• Use Liftoff and Agile Chartering to
align the team with the project
vision and set them up to succeed
63. Retrospective
• One thing we should change
• One thing you got value from
• Put on the board by the door!
