The document provides examples of tools and templates that can be used to plan an agile project launch, referred to as an "Inception Deck". It includes:
1. Why We Are Here - Outlines the purpose and objectives of the project.
2. What Can You Expect - Describes the project approach, timeline, resources needed.
3. What Are We Being Asked To Do - Identifies assumptions, risks, and next steps to establish shared understanding.
The examples cover topics such as benefits, stakeholders, estimates, constraints, and tests to set the project up for success.
The document outlines the Agile Inception Deck, which is a presentation used to get alignment on a project before starting. It discusses 10 questions to ask, including the purpose of the project, elevator pitch, scope, risks, timeline and budget. The goal is to eliminate confusion, set expectations and get buy-in from stakeholders on how the project will be approached before beginning the work.
Agile Product Development Playbook - Popular Tools and TechniquesAndy Birds
This Playbook provides an overview of some popular agile product development tools and techniques that Andy has found useful when building products. The Playbook focuses on Product Roadmaps as a keystone tool and provides a very high-level overview of other tools including; Product Vision Canvas, Product Canvas, Business Model Canvas, and Lean Canvas.
The Playbook is ideal for Product Managers, Product Owners, Business Analysts, User Experience Designers and anyone who works on an agile team or squad.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
This document discusses actionable agile metrics including work in progress, cycle time, and throughput. It defines each metric and explains why they are useful for understanding process stability, predictability, and improvements. Visualizations like cumulative flow diagrams and scatter plots of cycle times can help teams identify patterns and anomalies to investigate. Analyzing metrics over time through run charts also supports monitoring trends and capacity planning. The key message is that these quantitative metrics can trigger process improvements when used to learn rather than assess teams.
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
The document discusses using cycle time and scatterplots to measure and visualize workflow to better predict completion dates for work items. It introduces the concept of thinking probabilistically rather than deterministically when forecasting, since multiple outcomes are possible. Specific metrics like the 50th, 85th and 95th percentiles of a cycle time scatterplot can provide forecasts of when a given percentage of items may complete. Factors like work in progress, blockers and dependencies affect cycle times as well. The document promotes tracking start and end dates to measure flow and cycle times as fundamental metrics for gaining predictability.
Mini UX Workshop: Creating Persona & ScenarioNatt Phenjati
1. The document outlines an agenda for a UX design workshop on creating personas and scenarios. It includes lectures on personas, examples of personas, exercises to create personas and scenarios for two client companies, and criteria for grading the workshop outputs.
2. Participants will work in groups to study a product, build a persona, design a new product feature, and create a scenario depicting the persona using the new feature. They will present their work to the class.
3. The workshop aims to help designers understand how to create realistic personas and scenarios to identify customer needs and help guide product design decisions.
User Story Mapping (USM) helps teams get a common understanding of requirements from the user's perspective to facilitate backlog creation. It improves backlog quality and team communication. USM creates a map with user stories arranged in a usage flow. Each story follows the "As a <user>, I want <goal> so that <benefit>" format. Together, the mapped stories provide an overview of a product from the user experience while maintaining granular stories for planning and testing.
The document outlines the Agile Inception Deck, which is a presentation used to get alignment on a project before starting. It discusses 10 questions to ask, including the purpose of the project, elevator pitch, scope, risks, timeline and budget. The goal is to eliminate confusion, set expectations and get buy-in from stakeholders on how the project will be approached before beginning the work.
Agile Product Development Playbook - Popular Tools and TechniquesAndy Birds
This Playbook provides an overview of some popular agile product development tools and techniques that Andy has found useful when building products. The Playbook focuses on Product Roadmaps as a keystone tool and provides a very high-level overview of other tools including; Product Vision Canvas, Product Canvas, Business Model Canvas, and Lean Canvas.
The Playbook is ideal for Product Managers, Product Owners, Business Analysts, User Experience Designers and anyone who works on an agile team or squad.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
This document discusses actionable agile metrics including work in progress, cycle time, and throughput. It defines each metric and explains why they are useful for understanding process stability, predictability, and improvements. Visualizations like cumulative flow diagrams and scatter plots of cycle times can help teams identify patterns and anomalies to investigate. Analyzing metrics over time through run charts also supports monitoring trends and capacity planning. The key message is that these quantitative metrics can trigger process improvements when used to learn rather than assess teams.
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
The document discusses using cycle time and scatterplots to measure and visualize workflow to better predict completion dates for work items. It introduces the concept of thinking probabilistically rather than deterministically when forecasting, since multiple outcomes are possible. Specific metrics like the 50th, 85th and 95th percentiles of a cycle time scatterplot can provide forecasts of when a given percentage of items may complete. Factors like work in progress, blockers and dependencies affect cycle times as well. The document promotes tracking start and end dates to measure flow and cycle times as fundamental metrics for gaining predictability.
Mini UX Workshop: Creating Persona & ScenarioNatt Phenjati
1. The document outlines an agenda for a UX design workshop on creating personas and scenarios. It includes lectures on personas, examples of personas, exercises to create personas and scenarios for two client companies, and criteria for grading the workshop outputs.
2. Participants will work in groups to study a product, build a persona, design a new product feature, and create a scenario depicting the persona using the new feature. They will present their work to the class.
3. The workshop aims to help designers understand how to create realistic personas and scenarios to identify customer needs and help guide product design decisions.
User Story Mapping (USM) helps teams get a common understanding of requirements from the user's perspective to facilitate backlog creation. It improves backlog quality and team communication. USM creates a map with user stories arranged in a usage flow. Each story follows the "As a <user>, I want <goal> so that <benefit>" format. Together, the mapped stories provide an overview of a product from the user experience while maintaining granular stories for planning and testing.
The document describes "The Arrow" kanban board layout for managing workflow. It uses columns for work statuses (Done, Doing, etc.), priority levels (P1-P3), and work stages (Analysis, Design, etc.). Work flows from backlog priorities to stages to Done using "The Arrow" visualization where tasks literally move as arrows across the board as work is completed. The goal is to make dependencies and status visible at a glance to make improvements flow smoothly.
User Story Maps: Secrets for Better Backlogs and PlanningAaron Sanders
User story mapping is an intuitive way to build and organize a product backlog. During this session you’ll get hands-on experience building a user story map. You’ll learn:
How story mapping drives productive conversations with users and stakeholders.
How to plan incremental releases of your product using minimal holistic slices that deliver value at each product release.
Secrets to effective prioritization for both planning releases, and figuring out what to build next.
Tactical management of your backlog as you grow your working software to releasability.
The backlog building and managing strategies in this session will take you well beyond the agile basics.
This document discusses the state of agile adoption based on a survey of over 6,000 respondents. It finds that while agile adoption is increasing to meet business demands, organizations are not fully unlocking its benefits due to uneven implementation and remaining waterfall processes. Barriers to adoption include perceived threats to processes and resistance to change. The document advocates an incremental approach to change through visualization and limiting work in progress to drive improvements.
The document discusses product roadmaps in an agile context. It defines a product roadmap as a plan showing how a product will evolve over coming months or versions. Roadmaps provide continuity, alignment, and communicate strategy. Goal-oriented rather than feature-based roadmaps are recommended. The roadmap sits within the wider product strategy and helps focus the product backlog. Regular reviews ensure the roadmap stays dynamic and aligned with goals.
User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko
User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments.
"A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."
The document discusses a presentation on using user story mapping to build better products. The presentation aims to teach how to use a user story backlog to describe a user's experience with a product. It covers mapping user stories based on user experience, planning valuable incremental releases from the story map, and iteratively constructing software. The presentation discusses starting with user stories, mapping them based on tasks and activities, and slicing the story map into valuable product releases.
What is agile? Where did it come from, and how can it help me?
This session will go through a history of agile, including the origins of waterfall, the Toyota Production System and lean manufacturing, the creation of the agile manifesto, and how these all lead to the modern agile development frameworks we use today. By exploring the original design and intent behind agile principles and practices, we'll also uncover common pitfalls to agile adoption, and insights into overcoming them.
modern approaches share a focus on producing exceptional outcomes and growing an outstanding culture. Today, it makes far more sense to bypass antiquated agility in favor of modern approaches.
Modern agile methods are defined by four guiding principles:
- Make people awesome
- Make safety a prerequisite
- Experiment & learn rapidly
- Deliver value continuously
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
How to Get Started with Lean Portfolio ManagementCprime
Properly functioning Lean Portfolio Management will position your enterprise for profitable growth by delivering maximum customer value. You can get started with a few simple steps! Join Cprime and Apptio experts to learn how to:
-Structure your lean portfolio
-Put the right decision-makers in place
-Establish basic Lean Portfolio Management practices
-Clearly measure the health of the Lean Portfolio using Apptio
This document discusses work-in-process (WIP) limits in Kanban systems. It explains that WIP limits help improve workflow by surfacing problems. There are three types of WIP limits: personal, team execution limits to improve flow, and organizational structural limits to provide focus. Managing WIP limits can be challenging due to variability, constraints, and personal work styles, but lowering WIP limits over time helps identify issues. The document recommends several resources for learning more about Kanban and WIP limits.
Product Backlog - Refinement and Prioritization TechniquesVikash Karuna
This presentation describes the important techniques used in Product Backlog refinement and prioritization in Agile development. The various techniques described here are very useful for product managers, product owners, scrum masters, and agile teams.
Estimation is dead - long live sizing, by John Coleman 24Nov22.pdfOrderly Disruption
Estimation is dead - long live sizing, by John Coleman 24 Nov 22 to Agile Azerbaijan in person and Pozitive Technologies online
As per https://www.infoq.com/articles/sizing-forecasting-scrum/
The document discusses various product management artifacts used in Agile development such as user stories, product vision, product roadmap, product backlog, and sprint backlog. It describes how the product roadmap informs the prioritized product backlog, which contains short user stories that guide development work tracked in sprint backlogs on a sprint-by-sprint basis. Effective use of these artifacts helps ensure alignment between product strategy and development activities.
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.
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.
The document describes "The Arrow" kanban board layout for managing workflow. It uses columns for work statuses (Done, Doing, etc.), priority levels (P1-P3), and work stages (Analysis, Design, etc.). Work flows from backlog priorities to stages to Done using "The Arrow" visualization where tasks literally move as arrows across the board as work is completed. The goal is to make dependencies and status visible at a glance to make improvements flow smoothly.
User Story Maps: Secrets for Better Backlogs and PlanningAaron Sanders
User story mapping is an intuitive way to build and organize a product backlog. During this session you’ll get hands-on experience building a user story map. You’ll learn:
How story mapping drives productive conversations with users and stakeholders.
How to plan incremental releases of your product using minimal holistic slices that deliver value at each product release.
Secrets to effective prioritization for both planning releases, and figuring out what to build next.
Tactical management of your backlog as you grow your working software to releasability.
The backlog building and managing strategies in this session will take you well beyond the agile basics.
This document discusses the state of agile adoption based on a survey of over 6,000 respondents. It finds that while agile adoption is increasing to meet business demands, organizations are not fully unlocking its benefits due to uneven implementation and remaining waterfall processes. Barriers to adoption include perceived threats to processes and resistance to change. The document advocates an incremental approach to change through visualization and limiting work in progress to drive improvements.
The document discusses product roadmaps in an agile context. It defines a product roadmap as a plan showing how a product will evolve over coming months or versions. Roadmaps provide continuity, alignment, and communicate strategy. Goal-oriented rather than feature-based roadmaps are recommended. The roadmap sits within the wider product strategy and helps focus the product backlog. Regular reviews ensure the roadmap stays dynamic and aligned with goals.
User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko
User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments.
"A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."
The document discusses a presentation on using user story mapping to build better products. The presentation aims to teach how to use a user story backlog to describe a user's experience with a product. It covers mapping user stories based on user experience, planning valuable incremental releases from the story map, and iteratively constructing software. The presentation discusses starting with user stories, mapping them based on tasks and activities, and slicing the story map into valuable product releases.
What is agile? Where did it come from, and how can it help me?
This session will go through a history of agile, including the origins of waterfall, the Toyota Production System and lean manufacturing, the creation of the agile manifesto, and how these all lead to the modern agile development frameworks we use today. By exploring the original design and intent behind agile principles and practices, we'll also uncover common pitfalls to agile adoption, and insights into overcoming them.
modern approaches share a focus on producing exceptional outcomes and growing an outstanding culture. Today, it makes far more sense to bypass antiquated agility in favor of modern approaches.
Modern agile methods are defined by four guiding principles:
- Make people awesome
- Make safety a prerequisite
- Experiment & learn rapidly
- Deliver value continuously
User Story Mapping, Discover the whole storyJeff Patton
Variations of these slides have been used in a variety of talks.
These slides support discussions on why stories work, and when they don't. And, on story mapping, how and why it works.
How to Get Started with Lean Portfolio ManagementCprime
Properly functioning Lean Portfolio Management will position your enterprise for profitable growth by delivering maximum customer value. You can get started with a few simple steps! Join Cprime and Apptio experts to learn how to:
-Structure your lean portfolio
-Put the right decision-makers in place
-Establish basic Lean Portfolio Management practices
-Clearly measure the health of the Lean Portfolio using Apptio
This document discusses work-in-process (WIP) limits in Kanban systems. It explains that WIP limits help improve workflow by surfacing problems. There are three types of WIP limits: personal, team execution limits to improve flow, and organizational structural limits to provide focus. Managing WIP limits can be challenging due to variability, constraints, and personal work styles, but lowering WIP limits over time helps identify issues. The document recommends several resources for learning more about Kanban and WIP limits.
Product Backlog - Refinement and Prioritization TechniquesVikash Karuna
This presentation describes the important techniques used in Product Backlog refinement and prioritization in Agile development. The various techniques described here are very useful for product managers, product owners, scrum masters, and agile teams.
Estimation is dead - long live sizing, by John Coleman 24Nov22.pdfOrderly Disruption
Estimation is dead - long live sizing, by John Coleman 24 Nov 22 to Agile Azerbaijan in person and Pozitive Technologies online
As per https://www.infoq.com/articles/sizing-forecasting-scrum/
The document discusses various product management artifacts used in Agile development such as user stories, product vision, product roadmap, product backlog, and sprint backlog. It describes how the product roadmap informs the prioritized product backlog, which contains short user stories that guide development work tracked in sprint backlogs on a sprint-by-sprint basis. Effective use of these artifacts helps ensure alignment between product strategy and development activities.
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.
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.
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
The document discusses considering Scrum as a collection of working agreements rather than rigid rules. It suggests identifying patterns from successful past projects and agreeing as a team to implement those patterns. Examples of patterns include short feedback loops, clear priorities and responsibilities, and empowered team members. The document proposes treating Scrum as opportunities to ask powerful questions at each event, such as setting reasonable sprint goals and ensuring work quality.
The Civil Service Fast Stream is one of the UK's leading graduate recruitment programs, employing graduates in various professions through different schemes. The Fast Stream allows participants to gain diverse experience through postings in different government departments and locations over a short period of time. The HR Fast Stream specifically focuses on careers in human resources and involves two 18-month placements to expose graduates to a wide range of HR functions and equip them to become future HR leaders in the Civil Service. The selection process for the Fast Stream includes online tests, an e-tray exercise, and an assessment center involving exercises like policy writing, group tasks, and an interview.
How To Optimize Your Tech Recruiting Stack
Patrick Christell, Senior Sourcer at Hire4ce, meets all the qualifications of “MASTER.”
We’re talking a Full-Lifecycle Recruiter, Project Manager and Agile sourcing pod-builder with seven-plus years of progressive experience recruiting for technology companies across the boards.
He also has a rather impressive tech stack, which is what this is all about.
Patrick is here to give you 60-minutes of training and live Q&A that will help you learn to recruit top talent.
In this webinar we will cover:
- How to search.
Tools like Hiretual, Seekout, AmazingHiring (and their plusses and minuses).
The difference between searching for senior-level engineers, how to know if you are on a purple squirrel hunt, and what to with a BONUS live demo that iterates a single string.
- How to run a sourcing pod.
Learn how Patrick creates his own CRM that can do outreach and reporting
- How to understand tech without being a techie.
What a software stack even is, understanding how it fits together, learning what each part of the stack technologies are associated with.
- How to engage talent.
Why a mixture of broad spectrum outreach and personalized outreach is best.
What cadence works best in 2019.
Why only using inmails screws you, and how to leverage the phone even if you hate using it (TextNow).
Nobody’s got time for a floppy stack.
Let Patrick show you how to build in functionality and results.
The document discusses various aspects of testing in an agile environment. It covers roles like testers, product owners, and scrum masters. It also discusses testing practices like unit testing, exploratory testing, test automation. Other topics include test levels like unit, integration and end-to-end testing. Team dynamics and how testing fits in the agile process are also summarized.
ScrumMaster Education Programme - The StoryHelen Meek
The document describes a ScrumMaster education program created by Ripple Rock to support ScrumMasters in their development.
The program included:
- Weekly coaching sessions covering various Agile topics selected by the community
- Assigning mentors and providing training, both in and out of context
- Developing a competency model to help ScrumMasters self-assess and identify areas for growth
An evaluation found that participation increased participants' knowledge and abilities in most areas of the competency model over 6 months. Two ScrumMasters in particular demonstrated significant improvement in their Agile skills. The program was considered successful in continually developing the ScrumMaster community.
This document discusses retrospectives and contains advice for conducting effective retrospectives. It provides:
1) An overview of why retrospectives are important for organizations undergoing change to allow people to express feelings and thoughts about changes in a structured way.
2) Common objections to retrospectives and reasons they may not be effective if done incorrectly, such as focusing too much on the past, having unconnected ideas, or unclear outcomes.
3) A simple framework and checklist for planning and running retrospectives, including setting the stage, gathering data, generating insights, deciding on actions, and closing the retrospective.
4) Descriptions of various exercises that can be used in retrospectives, such as "Remember the Future",
Анна Мамаєва “Retrospective: Total Recall” - Lviv PMDayLviv Startup Club
This document discusses retrospectives and contains advice for conducting effective retrospectives. It provides:
1. An overview of why retrospectives are important for organizations undergoing change and examples of things teams say to avoid retrospectives.
2. Tips for running retrospectives effectively such as using a simple framework of setting the stage, gathering data, generating insights, deciding on actions, and closing the retrospective.
3. Descriptions of various exercises that can be used in retrospectives like "Remember the Future" and "Margolis Wheel" to engage participants and surface different perspectives.
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.
Agile Topics - Explained Simply - Practical Agilist.pptxBrian Link
This document provides an overview of various agile topics that are explained simply by Brian Link of PracticalAgilist.com. It covers running effective standups and understanding agile roles, writing user stories and estimating work, maintaining a product backlog, having valuable sprint reviews and feedback loops, facilitating retrospectives, and connecting strategy to delivery through OKRs and roadmaps. The document emphasizes building trust within teams and cultivating an iterative, learning-focused agile mindset. It provides contact information for Brian Link and mentions his free book on 21 common agile misconceptions.
The document discusses values, principles, and practices related to agile transformation. It begins by defining values, principles, and practices, using examples like feedback and unit testing. It then discusses concepts like minimum viable product, stand-ups, and retrospectives, examining whether they are rituals or practices. The document advocates discerning when rituals help or hinder and suggests principles and values should underpin practices. It also maps agile values and practices to universal ideals like truth, strength, beauty, fraternity, equality and liberty. Finally, it encourages permeating agility with feedback and manifesting ideals through small steps.
This document summarizes how a scrum team conducts various scrum activities including sprint demos, retrospectives, and slack time between sprints. It provides details on:
- Conducting sprint demos and insisting they include a demo at the end of each sprint for feedback.
- Organizing sprint retrospectives to identify what went well, opportunities for improvement, and action items for the next sprint.
- The importance of slack time between sprints for rest and learning, such as dedicating lab days for skills development.
This document summarizes how one agile team implements Scrum. It discusses how the team manages their product backlog, preparing and planning for sprints. The team focuses on getting work done over theoretical practices. They prioritize customer needs and concrete deliverables in the product backlog. Estimates are relative and in story points to focus on the work rather than timelines.
Aubrey Smith, Sparked Advisory
In this training, we will build on the foundation established in Lean Startup 101 and 201 by delving into examples and cases of the Lean Startup concepts in action. Attendees of Lean Startup 301 will be exposed to cutting edge work from thought leaders and experts using Lean Startup in practice today — at startups and within the enterprise. Participation in this session is essential: You will be asked to help design an MVP and experiment to test critical Leap of Faith Assumption(s) in groups and will be encourage to share experiences. The session is designed to allow attendees to stretch their skills and to push one-another to ‘learn by doing’. The session will also include:
Sample cases and live interviews with practitioners highlighting the application of core concepts;
Exercises designed to bring the concepts to life and challenge participants to deepen their skills;
Discussion of advanced topics such organizational culture and governance as well as industry-specific concepts such as using Lean Startup in heavily regulated markets.
Thanks to Lean Startup Co.’s law firm, Orrick, for being the sponsor for this track.
This document discusses distributed scrum and the challenges of working with distributed teams across different time zones and cultures. It recommends ways to improve communication for distributed teams, such as using video conferencing and documentation, building trust through frequent feedback and contact, and organizing short development cycles. Maintaining a low level of distribution and cross-functional collocated teams can help reduce challenges. Understanding scrum principles is also important for effective distributed teams.
This document provides an overview of an Agile and Scrum workshop presented by Rasmus Runberg. It includes an introduction to Rasmus and the workshop agenda. The document then covers the key topics in the workshop: What is Agile, the Agile Manifesto, Scrum values and process, and the Scrum roles of the Development Team, Scrum Master, and Product Owner. It describes group activities for participants to discuss the Agile Manifesto principles and benefits of Agile. It also provides information on the Product Backlog and how stories are prioritized from high-level Epics down to individual User Stories.
Similar to Inception deck and lift off examples (20)
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...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 automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
2. 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
‘Parrots Arrr
Us’ example
4. 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)
Conference
workshop
example
5. 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
Conference
workshop
example
6. 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
Conference
workshop
example
8. 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
Conference
workshop
example
10. Our ‘Meet The Neighbours’
Conference
workshop
example
11. Our Assumption MapOur Assumption MapOur 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
Conference
workshop
example
15. 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.
Conference
workshop
example
16. 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
Conference
workshop
example
17. 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
Generic
example
18. 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
Generic
example
19. 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
Conference
workshop
example
20. 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
Conference
workshop
example
21. Our ‘Final Test’
We do we 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!
Conference
workshop
example
22. 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.
25. The first choice 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 ‘Parrots Arrr
Us’ example
26. 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.
‘Parrots Arrr
Us’ example
27. Alignment
Exercises and Artefacts that help the
team understand each other, and how
they can each make their maximum
contribution to the project
28. Simple Rules Example
1. Integrity - We do what we say we will do
2. Ingenuity - We collaborate to help us come up with the
best ideas
3. Impact - We focus on delivering value to the customer in
everything we do
4. Teamwork - We look out for each other and always offer to
help
Simple Rules
These are the things we value and believe in
A few (5 plus or minus 2) short descriptions of the values and beliefs that the team find important.
Start with an action verb. Eg: “Ingenuity - We collaborate to help us come up with the best ideas.” @simongirvan
Based on ideas from “Liftoff”, by Diana Larson and Ainsley Nies
Generic
example
29. Working Agreement Example
Generic
example1. We don’t work on anything that isn’t on the Sprint Backlog
2. Our calendars are always up to date with location and
availability
3. All our meetings matter - No meeting purpose; no meeting
4. We have fun and don’t take ourselves too seriously
5. We respect each other’s quiet time - Headphones on means
no interruptions.
Working Agreement
These few (5 plus or minus 2) statements describe the contract between the team members. They describe specific
actions that the team have decided are important to them and will call each other out on. They will evolve with the team.
For example: “We respect each other’s quiet time - headphones on means no interruptions” @simongirvan
Based on ideas from “Liftoff”, by Diana Larson and Ainsley Nies
As a team, we work together best when…
30. 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.
33. 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
‘Parrots Arrr
Us’ example