James Birchler discusses scaling product development at IMVU using a Lean Startup approach. Initially, IMVU's product development process worked well for a small team but failed as the team grew. Changes included appointing a single product owner, adopting agile practices like Scrum with 3-week sprints, standardizing processes, limiting team sizes to 4 engineers, and continuously adapting the process based on lessons learned. Applying the Build-Measure-Learn loop helped transform teams into the most productive Birchler had seen.
Lean is a mindset focused on eliminating waste, amplifying learning, deciding late, delivering fast, empowering teams, building integrity, and seeing the whole project. It values eliminating non-value adding activities, irregularities, and excess. Kanban is used to help teams improve their software development process by visualizing their workflow and identifying bottlenecks using boards, limiting work in progress, and continuously improving as a team. Both Lean and Kanban emphasize starting with the current process and making incremental changes through collaboration and respecting existing roles and responsibilities.
This is the presentation handout from my recorded session at the 2016 Learning Solutions Conference. This version includes speaker notes, since the live one was mostly pictures.
This document provides an overview of a 4-step user-centered design process for creating apps and interfaces. The steps are: 1) Define the problem by understanding user needs through observation and interviews; 2) Prototype solutions quickly through paper prototypes and storyboards to get early feedback; 3) Evaluate designs using usability heuristics; and 4) Learn and iterate based on user testing to continually improve the design. The goal is to help readers with little design experience go through a process that will result in designs focused on solving users' problems.
Como implementar segurança sem afetar a experiência do cliente | Trilha de Pr...Product Camp Brasil
Augusto Pierzynski, Product Manager, Nubank
Em um mundo cada vez mais digital, os ataques cibernéticos e fraudes são uma realidade. As empresas estão começando a tomar consciência que precisam investir em segurança. O grande desafio é como trazer segurança sem estragar a experiência do cliente.
[DevDay2019] Things i wish I knew when I was a 23-year-old Developer - By Chr...DevDay Da Nang
Christophe will talk about what he's learned from his almost 20 years of experience in the IT industry, and his career and training advice for the upcoming generation. This include his personal experiences, what motivates him everyday, and hopefully may help you define your path to “success”. This is not about any specific technology.
Gaurav Agarwal, LensBricks , @agarwal__gaurav
Knowing your customers is difficult, and finding them can be an expensive endeavor. Gaurav Agarwal has learned a few easy, low cost tricks to help startups build a quick understanding of customers and market. His techniques leverage existing web analytics tools that are available to all. Aimed to help startups get more with less, when working in a resource-constrained environment.
Too busy to learn UX methods that can save you tons of time?
Wondering which UX techniques are most likely to provide useful results all along your project? Let's talk about some tactics we tried. Success stories and epic fails of methods we have tested to build digital products and interfaces consumers love to use.
Lean is a mindset focused on eliminating waste, amplifying learning, deciding late, delivering fast, empowering teams, building integrity, and seeing the whole project. It values eliminating non-value adding activities, irregularities, and excess. Kanban is used to help teams improve their software development process by visualizing their workflow and identifying bottlenecks using boards, limiting work in progress, and continuously improving as a team. Both Lean and Kanban emphasize starting with the current process and making incremental changes through collaboration and respecting existing roles and responsibilities.
This is the presentation handout from my recorded session at the 2016 Learning Solutions Conference. This version includes speaker notes, since the live one was mostly pictures.
This document provides an overview of a 4-step user-centered design process for creating apps and interfaces. The steps are: 1) Define the problem by understanding user needs through observation and interviews; 2) Prototype solutions quickly through paper prototypes and storyboards to get early feedback; 3) Evaluate designs using usability heuristics; and 4) Learn and iterate based on user testing to continually improve the design. The goal is to help readers with little design experience go through a process that will result in designs focused on solving users' problems.
Como implementar segurança sem afetar a experiência do cliente | Trilha de Pr...Product Camp Brasil
Augusto Pierzynski, Product Manager, Nubank
Em um mundo cada vez mais digital, os ataques cibernéticos e fraudes são uma realidade. As empresas estão começando a tomar consciência que precisam investir em segurança. O grande desafio é como trazer segurança sem estragar a experiência do cliente.
[DevDay2019] Things i wish I knew when I was a 23-year-old Developer - By Chr...DevDay Da Nang
Christophe will talk about what he's learned from his almost 20 years of experience in the IT industry, and his career and training advice for the upcoming generation. This include his personal experiences, what motivates him everyday, and hopefully may help you define your path to “success”. This is not about any specific technology.
Gaurav Agarwal, LensBricks , @agarwal__gaurav
Knowing your customers is difficult, and finding them can be an expensive endeavor. Gaurav Agarwal has learned a few easy, low cost tricks to help startups build a quick understanding of customers and market. His techniques leverage existing web analytics tools that are available to all. Aimed to help startups get more with less, when working in a resource-constrained environment.
Too busy to learn UX methods that can save you tons of time?
Wondering which UX techniques are most likely to provide useful results all along your project? Let's talk about some tactics we tried. Success stories and epic fails of methods we have tested to build digital products and interfaces consumers love to use.
Scale quality with kaizen - Tech.Rocks conferenceFabrice Bernhard
MVPs at full speed with a little team: OK. But once the project scales, how do you address the inevitable slowdown due to exponential complexity? Kaizen is Toyota's scalable solution and our results are impressive.
Agile Innovation - Product Management in Turbulent timesVasco Duarte
In today’s world we are constantly confronted with the message that the competition is breeding down our necks, that the market and environment are changing and we need to change with them. And most importantly, we are told that we need to listen to our customers to be able to provide the right products.
We as a Product Managers need to be able to see beyond the basic product decisions, e.g. do we add feature A or feature B? We need to think beyond the silo of our function.
UX Beers - A Story about product management at uman.ai - Jasper VerplankenUX Antwerp Meetup
After a consulting and agency career as a UX architect, Jasper is now involved in uman.ai, an AI startup involved in corporate learning and competency management. He focuses on building the product and the product marketing that comes with it.
Ascesis playbook - everything you want to know about AscesisAscesis
Ascesis Media is a digital marketing agency that offers services such as website development, graphic design, digital marketing, and video production. They use an agile, objective-based development process focused on continuous feedback and iteration. Clients are involved throughout the process and work closely with Ascesis' team to achieve their goals in a flexible manner. Ascesis aims to form partnerships with clients and help them succeed through innovative digital strategies.
1) There are several jobs available in the media sector including light technician, film director, video editor, and extras in movies/TV shows.
2) It is important to conduct yourself professionally in any media sector job by meeting deadlines, producing high quality work, and avoiding legal/ethical issues.
3) For jobs like director and video editor, building experience through internships, personal projects, and networking can help get your foot in the door. Maintaining online portfolios also allows potential employers to review samples of your work.
[DevDay2019] Growth Hacking - How to double the benefits of your startup with...DevDay Da Nang
What is growth hacking? Why do all startup need it? Examples of Growth Hack with 10 Classic (Facebook, Dropbox, Airbnb, etc.). How to create robot to automatize your task. How to find clients automatically in 5 minutes. 6 SEO hacks to grow up super fast on Google.
The document discusses how a project manager should regularly assess project agility by asking themselves questions about changes, customer needs, blocking issues, team stress levels, progress tracking, potential issues, risk levels, and management status updates. Some key questions include determining the impact of changes, if customer needs are being met, identifying and resolving blocking issues, noticing signs of team stress, monitoring progress, looking for emerging issues, and gauging overall risk level. Strong communication with teams and management is important for making adjustments that keep the project on track.
Lean Management Review at Volunteer MauritiusMushood Badulla
Start Up Mauritius provides lean management training to help participants successfully complete an entrepreneurial internship. The training covers lean startup techniques like developing value and growth hypotheses to test assumptions about business ideas. A key technique taught is creating a minimum viable product (MVP) - a basic version of the product with minimum features - to test assumptions without large investments. Participants will learn to test MVPs, analyze results, and either improve the product or "pivot" the business strategy based on what they learn to increase chances of success. The goal is for participants to gain experience from an initial failure in order to succeed in future business endeavors.
The document discusses different sources of funding for productions including self-financing, client financing, and crowdfunding. It also outlines the roles needed for a production team of 3 people including a photographer, copywriter, and graphic designer. Details are provided about finding locations, equipment, and managing risks and limitations for shooting recipe cards.
How we built Talentpioneer by ProductsquadsProductsquads
This is a digital product ferry tale, without the ferry tale. 100% Transparency. This is how we built digital products. No bullshit. Product Building at it's best.
The document provides definitions and explanations of different types of funding for productions, including self-financing, employer/client financing, and Kickstarter crowdfunding. It discusses which type of funding would be most suitable for the student's small recipe card production project, noting that self-financing would be sufficient and avoid unnecessary costs. Potential expenses like ingredients, equipment, and printing are identified. Maintaining a schedule and allocating contingency time are proposed as methods for ensuring deadlines are met. Legal requirements and regulatory bodies for images, recipes, food safety, and advertising are also addressed.
The document outlines the lean startup methodology for developing a minimum viable product (MVP) to test business hypotheses. It discusses defining customers and their problems, formulating hypotheses about solutions, identifying the riskiest assumptions to test, building the simplest MVP to test assumptions, and analyzing results to determine whether to persevere or pivot the idea. An example experiment tests the hypothesis that providing virtual UX feedback is a solution to bootstrapped startups' problem of getting UX feedback, with the riskiest assumption being finding a reliable feedback source. The results validated this assumption when 8 out of 10 founders were pitched the idea.
This document discusses applying lean thinking principles to software development. It describes lean's focus on reducing waste, defined as anything not adding value for the customer. Some key ways lean can be applied to software development discussed are: using a pull system to only start new tasks when previous ones are finished; reducing setup time between tasks; tracking and reducing queues that cause waiting; and identifying the seven common types of waste in manufacturing and how they translate to software development.
- As the startup grew from 2 to 15 people, they implemented Scrum processes like daily standups and sprint retrospectives to improve communication and collaboration across teams.
- Key roles like product manager and architect were added to plan features further out while engineers focused on the next 1-2 sprints.
- Processes were established for ideas to move from roadmap to development to production, including backlog grooming, epic and sprint planning, and end of sprint demos. Frequent meetings helped align teams working on interdependent features.
- Continuous improvement of processes and tools helped support the growing product complexity and multiple teams across timezones needed for large enterprise customers.
The product owner is responsible for maximizing the value of the product by ensuring that the appropriate features are implemented in each release. This includes managing the product backlog, which contains the features, enhancements and fixes prioritized by the product owner. The product owner works closely with the scrum master and development team to refine user stories, establish acceptance criteria, participate in planning and review sessions, and make decisions about the product.
Intro to Lean Startup - Women's Startup Lab April 2015Kevin Shutta
The document provides an overview of Lean Startup methodology compared to traditional approaches. It discusses conducting customer interviews and experiments to test hypotheses and reduce risks before building products. Key points covered include identifying customer problems, designing minimum viable products to solve problems, getting early feedback through MVP demos and sales pitches, and being willing to pivot the idea if it fails to gain traction. The presentation emphasizes learning quickly through cheap, hands-on experiments rather than spending months building something customers may not want.
Design Sprints: Learnings and Insights from the TrenchesBart Deferme
1. The document discusses learnings from conducting design sprints at Qwinix, a software development company. It summarizes insights from facilitating over 12 design sprints.
2. Key takeaways include the importance of producing a sprint report, ensuring collaboration through off-site lunches, careful recruitment of prototype testers, defining roles for facilitation, and keeping the goals of the sprint in focus to avoid going off track.
3. Other insights involve avoiding early discussions of monetization, helping clients identify their end users through questioning assumptions, understanding that the sprint is just the beginning of a user-centered design process, and managing expectations that the sprint is not a shortcut but a validation step.
The document summarizes Heek's product development process, which includes defining the problem, crafting personas, building prototypes, conducting private and public betas, and launching the product. Some key steps are identifying a problem by interviewing potential users, defining the "why, how, what" to clarify goals, creating personas to represent target users, iteratively prototyping based on user feedback, launching a minimum viable product, and using tools like Product Hunt to generate interest during public launch. The process aims to continuously validate assumptions and refine the product based on real-world user testing.
The document discusses the principles of agile development as outlined in the Agile Manifesto. It describes how agile values individuals and interactions, working software, customer collaboration, and responding to change over processes, tools, documentation, contracts, and plans. It then provides details on 11 key principles of agile development including delivering frequently to gain early customer feedback, adapting to changing requirements, maintaining a constant development pace, and allowing self-organizing teams. The overall goal of agile is to satisfy customers through early and continuous delivery of working software.
Scale quality with kaizen - Tech.Rocks conferenceFabrice Bernhard
MVPs at full speed with a little team: OK. But once the project scales, how do you address the inevitable slowdown due to exponential complexity? Kaizen is Toyota's scalable solution and our results are impressive.
Agile Innovation - Product Management in Turbulent timesVasco Duarte
In today’s world we are constantly confronted with the message that the competition is breeding down our necks, that the market and environment are changing and we need to change with them. And most importantly, we are told that we need to listen to our customers to be able to provide the right products.
We as a Product Managers need to be able to see beyond the basic product decisions, e.g. do we add feature A or feature B? We need to think beyond the silo of our function.
UX Beers - A Story about product management at uman.ai - Jasper VerplankenUX Antwerp Meetup
After a consulting and agency career as a UX architect, Jasper is now involved in uman.ai, an AI startup involved in corporate learning and competency management. He focuses on building the product and the product marketing that comes with it.
Ascesis playbook - everything you want to know about AscesisAscesis
Ascesis Media is a digital marketing agency that offers services such as website development, graphic design, digital marketing, and video production. They use an agile, objective-based development process focused on continuous feedback and iteration. Clients are involved throughout the process and work closely with Ascesis' team to achieve their goals in a flexible manner. Ascesis aims to form partnerships with clients and help them succeed through innovative digital strategies.
1) There are several jobs available in the media sector including light technician, film director, video editor, and extras in movies/TV shows.
2) It is important to conduct yourself professionally in any media sector job by meeting deadlines, producing high quality work, and avoiding legal/ethical issues.
3) For jobs like director and video editor, building experience through internships, personal projects, and networking can help get your foot in the door. Maintaining online portfolios also allows potential employers to review samples of your work.
[DevDay2019] Growth Hacking - How to double the benefits of your startup with...DevDay Da Nang
What is growth hacking? Why do all startup need it? Examples of Growth Hack with 10 Classic (Facebook, Dropbox, Airbnb, etc.). How to create robot to automatize your task. How to find clients automatically in 5 minutes. 6 SEO hacks to grow up super fast on Google.
The document discusses how a project manager should regularly assess project agility by asking themselves questions about changes, customer needs, blocking issues, team stress levels, progress tracking, potential issues, risk levels, and management status updates. Some key questions include determining the impact of changes, if customer needs are being met, identifying and resolving blocking issues, noticing signs of team stress, monitoring progress, looking for emerging issues, and gauging overall risk level. Strong communication with teams and management is important for making adjustments that keep the project on track.
Lean Management Review at Volunteer MauritiusMushood Badulla
Start Up Mauritius provides lean management training to help participants successfully complete an entrepreneurial internship. The training covers lean startup techniques like developing value and growth hypotheses to test assumptions about business ideas. A key technique taught is creating a minimum viable product (MVP) - a basic version of the product with minimum features - to test assumptions without large investments. Participants will learn to test MVPs, analyze results, and either improve the product or "pivot" the business strategy based on what they learn to increase chances of success. The goal is for participants to gain experience from an initial failure in order to succeed in future business endeavors.
The document discusses different sources of funding for productions including self-financing, client financing, and crowdfunding. It also outlines the roles needed for a production team of 3 people including a photographer, copywriter, and graphic designer. Details are provided about finding locations, equipment, and managing risks and limitations for shooting recipe cards.
How we built Talentpioneer by ProductsquadsProductsquads
This is a digital product ferry tale, without the ferry tale. 100% Transparency. This is how we built digital products. No bullshit. Product Building at it's best.
The document provides definitions and explanations of different types of funding for productions, including self-financing, employer/client financing, and Kickstarter crowdfunding. It discusses which type of funding would be most suitable for the student's small recipe card production project, noting that self-financing would be sufficient and avoid unnecessary costs. Potential expenses like ingredients, equipment, and printing are identified. Maintaining a schedule and allocating contingency time are proposed as methods for ensuring deadlines are met. Legal requirements and regulatory bodies for images, recipes, food safety, and advertising are also addressed.
The document outlines the lean startup methodology for developing a minimum viable product (MVP) to test business hypotheses. It discusses defining customers and their problems, formulating hypotheses about solutions, identifying the riskiest assumptions to test, building the simplest MVP to test assumptions, and analyzing results to determine whether to persevere or pivot the idea. An example experiment tests the hypothesis that providing virtual UX feedback is a solution to bootstrapped startups' problem of getting UX feedback, with the riskiest assumption being finding a reliable feedback source. The results validated this assumption when 8 out of 10 founders were pitched the idea.
This document discusses applying lean thinking principles to software development. It describes lean's focus on reducing waste, defined as anything not adding value for the customer. Some key ways lean can be applied to software development discussed are: using a pull system to only start new tasks when previous ones are finished; reducing setup time between tasks; tracking and reducing queues that cause waiting; and identifying the seven common types of waste in manufacturing and how they translate to software development.
- As the startup grew from 2 to 15 people, they implemented Scrum processes like daily standups and sprint retrospectives to improve communication and collaboration across teams.
- Key roles like product manager and architect were added to plan features further out while engineers focused on the next 1-2 sprints.
- Processes were established for ideas to move from roadmap to development to production, including backlog grooming, epic and sprint planning, and end of sprint demos. Frequent meetings helped align teams working on interdependent features.
- Continuous improvement of processes and tools helped support the growing product complexity and multiple teams across timezones needed for large enterprise customers.
The product owner is responsible for maximizing the value of the product by ensuring that the appropriate features are implemented in each release. This includes managing the product backlog, which contains the features, enhancements and fixes prioritized by the product owner. The product owner works closely with the scrum master and development team to refine user stories, establish acceptance criteria, participate in planning and review sessions, and make decisions about the product.
Intro to Lean Startup - Women's Startup Lab April 2015Kevin Shutta
The document provides an overview of Lean Startup methodology compared to traditional approaches. It discusses conducting customer interviews and experiments to test hypotheses and reduce risks before building products. Key points covered include identifying customer problems, designing minimum viable products to solve problems, getting early feedback through MVP demos and sales pitches, and being willing to pivot the idea if it fails to gain traction. The presentation emphasizes learning quickly through cheap, hands-on experiments rather than spending months building something customers may not want.
Design Sprints: Learnings and Insights from the TrenchesBart Deferme
1. The document discusses learnings from conducting design sprints at Qwinix, a software development company. It summarizes insights from facilitating over 12 design sprints.
2. Key takeaways include the importance of producing a sprint report, ensuring collaboration through off-site lunches, careful recruitment of prototype testers, defining roles for facilitation, and keeping the goals of the sprint in focus to avoid going off track.
3. Other insights involve avoiding early discussions of monetization, helping clients identify their end users through questioning assumptions, understanding that the sprint is just the beginning of a user-centered design process, and managing expectations that the sprint is not a shortcut but a validation step.
The document summarizes Heek's product development process, which includes defining the problem, crafting personas, building prototypes, conducting private and public betas, and launching the product. Some key steps are identifying a problem by interviewing potential users, defining the "why, how, what" to clarify goals, creating personas to represent target users, iteratively prototyping based on user feedback, launching a minimum viable product, and using tools like Product Hunt to generate interest during public launch. The process aims to continuously validate assumptions and refine the product based on real-world user testing.
The document discusses the principles of agile development as outlined in the Agile Manifesto. It describes how agile values individuals and interactions, working software, customer collaboration, and responding to change over processes, tools, documentation, contracts, and plans. It then provides details on 11 key principles of agile development including delivering frequently to gain early customer feedback, adapting to changing requirements, maintaining a constant development pace, and allowing self-organizing teams. The overall goal of agile is to satisfy customers through early and continuous delivery of working software.
The document discusses how to build a customer-driven product team. It recommends structuring teams with 3 people (engineer, tech lead, engineer) to allow for autonomy and accountability. Each team is paired with a product manager, designer, and marketer to gather customer feedback and iterate quickly. The approach scales by having teams own products end-to-end and share metrics with internal stakeholders. Continuous delivery is key, with teams shipping updates daily to get quick feedback. This creates a feedback loop that puts customers first.
David Cancel of Drift at BoS Conference USA 2016.
See all talks here: http://businessofsoftware.org/2016/07/all-talks-from-business-of-software-conferences-in-one-place-saas-software-talks/
This document discusses applying Agile principles to projects through examples. It provides 7 examples of Agile principles in action, including satisfying customers through early delivery, accepting changing requirements, delivering working software frequently, having business and developers work together daily, building around motivated individuals, using face-to-face communication, and using working software as the primary measure of progress. Each example compares an Agile approach to challenges with a traditional waterfall approach and discusses benefits of Agile in that situation.
Agile methodologies have quickly become central to the way we create and refine digital products. These rapid cycles of building, measuring, and learning are great for refining an already innovative product but these tools are being increasingly called upon to produce innovation itself and they suck at it.
In this high-level, philosophical talk, Scott draws from 25+ years of experience in digital product strategy and design to take a critical and sometimes controversial look at processes that claim to promote innovation but too often fail to deliver.
He also highlights some principles and practices that seem to promote real innovation and help it survive the perilous journey from the minds of innovators to the hands and hearts of users.
This document contains the transcript from a presentation on UX in South Africa. It discusses:
1) The current state of UX in South Africa, with some organizations not understanding user needs or how to handle complexity.
2) How companies that use design strategically grow faster, and the need for growth in South Africa.
3) How the 684 attendees can help drive positive change through understanding what UX is and what needs to change.
4) Various aspects of UX like vision, strategy, interaction design and more. It emphasizes the importance of user research, prototyping and getting products in front of users.
In her talk Anna will share learnings of frequently testing with users in agile teams. Also she will show that testing with users can be simple, effective & prove its value.
Anna is an interaction designer & UX researcher with 9 years of experience. She likes to challenge the ‘WHY‘ of user actions. Two years ago she started the UX Lab at IceMobile to give a voice to the user. Today the UX Lab validates all concepts & products with users. She created 'Pulse UX' a simple method of frequent user testing that lets agile teams develop better products faster. Pulse UX is now part of every sprint at IceMobile.
Product Tank Amsterdam Pulse UX Presentationicemobile
In her talk Anna shares learnings of frequently testing with users in agile teams. Also she will show that testing with users can be simple, effective & prove its value.
Anna is an interaction designer & UX researcher with 9 years of experience. She likes to challenge the ‘WHY‘ of user actions. Two years ago she started the UX Lab at IceMobile to give a voice to the user. Today the UX Lab validates all concepts & products with users. She created 'Pulse UX' a simple method of frequent user testing that lets agile teams develop better products faster. Pulse UX is now part of every sprint at IceMobile.
How Product Managers & Developers Deliver Value at AvvoDanielle Martin
I gave a talk at Code Fellows' Partner Power Hour series about how product managers and developers work together at Avvo -- including lessons we've learned and tips for dev students starting their careers.
This document provides an overview of rapid product development using a continuous feature improvement approach. It begins by introducing Zach Beer and his experience in product development roles. It then discusses some quick disclaimers about terminology and assumptions. The document advocates for determining the narrowest feature slice that can add value, delivering it quickly for customer feedback, learning from each delivery, and repeating. It provides examples of how to choose the right feature slice and develop critical feedback loops from customers. The document acknowledges challenges but argues the approach ultimately makes development easier and teams happier. It analogizes the process to incremental car feature development.
First presented at the Push Conference in October 2018 in Münich, Germany.
---
See more at ui-patterns.com
---
Are you stuck in product tunnel vision, still focusing on implementing ideas months old, only to find out they failed? Are you tired of spending time on building stuff nobody wants (other than your boss)?
Then let's go on a ride! Anders will tell you how to escape tunnel vision and start focusing on building the right thing. The silver bullet is systematic and constant product testing.
Anders will take the boring part out of testing and show you how easy it can be, so you product can start shining to more (and the right) people. He will reveal his playbook of cleverly thought out product experiments used by product builders at companies like Spotify, Booking.com, Facebook, Amazon, and Google and recommended by top universities like Havard, MIT, and Stanford.
Working together: Agile teams, developers, and product managersDanielle Martin
I spoke to students at Ada Developer Academy in Seattle, WA about how product managers and software engineers work together. In the presentation I cover: what's an agile team and how do they work; case studies of real work by my agile product development team; advice about behaviors that create successful product manager and developer working relationships; and other career/life advice for students starting their careers as software engineers.
The Lean Startup (book summary by Expert Program Management)Dennis Antolin
The Lean Startup Summary
Big idea #1: Startups are essentially 'Scientific Experiments'
Big idea #2: The biggest waste is building what nobody wants at all
Big idea #3: Don't argue about effort-prioritization - Use Split-Tests & Cohorts!
Big idea #4: You might be an Entrepreneur and not even know it!
Big idea #5: Use Actionable Metrics and avoid 'Vanity Metrics'
This document summarizes a workshop on creating lean research techniques. The workshop covered challenges in research such as delivering insights faster and recruiting users. It discussed lean UX principles like design thinking, agile development, and collaboration. Techniques for lean user research included creating a consolidated source of insights, educating all employees on users, conducting weekly user interviews, and running rapid iterative user testing. Challenges of these techniques like startup costs and managing large panels were also addressed. The goal was to facilitate collaboration and sharing of experiences to discover solutions already tried or brainstorm new methods.
Highest quality code in your SaaS project. Why should you care about it as a ...The Codest
We are launching a SaaS report dedicated to the whole SaaS market.
It is a useful pill of knowledge for the non-technical founders who are struggling with many challenges, especially the technological ones. In the report, we cover the specific problems/dilemmas such as:
- Is it worth making SaaS start-up if you are a non-technical founder?
- What are the biggest challenges to a non-technical founder?
- MVP as the most popular way to deliver product time to market
- Useful tips on how to build a SaaS product in 6 simple steps
Check out the report and make sure to eliminate common mistakes that can hurt your business. Are you a non-technical founder? Don’t worry!
In the short tutorial, you will learn how to successfully build a SaaS product with no programming skills.
5 Lessons Learned in Product Management by Twitch Senior PMProduct School
Main takeaways:
- How to take a non traditional path to product management
- How to leverage your unique background to differentiate yourself as a Product Manager
- Steps you can take to build your product management skills/portfolio while in other fields
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!
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
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!
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
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.
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.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
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.
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.
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...alexjohnson7307
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
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.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...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 integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
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. 🌟
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
44. Thank you!James BirchlerEmail: jbirchler@imvu.comTwitter: @jamesbirchlerTweet this talk! #imvugdc Title slide photo credit: Jewel Fish by www.flickr.com/psyberartist SLIDE COPY BELOW THIS POINT------------------------------------ Name one guaranteed winning tactic
132. Q & A Thank you! James BirchlerEmail: jbirchler@imvu.comTwitter: @jamesbirchlerTweet this talk! #imvugdc
Editor's Notes
I’ve got some questions for you:How many of you are part of a product team building great stuff for customers? Now…
…does anyone have one product development tactic you use that works consistently to help your team meet its goals and deliver great stuff to customers, every time and for every project? I would like that, because it would be great to know that there is tactic, or even a set of tactics or a process—that can lead my team to success every time.
But I can’t think of even onethat I would count on to work every time, not amidst all the changing conditions of a dynamic product and business. What I would bet my money on is a winning…
…strategy, one you can use to maximize your team’s chances of success over time of delivering great features to your customers.Today I’ll share one of the strategies that we use at IMVU.
I’m going to review a lot of material today, so to make a couple things more memorable, I’ll reference two of my favorite things: pizza and maps.
Today IMVU is asocial entertainment product where our customersuse 3D avatars to meet people, chat, create cool stuff—AKA UGC--, and play games with their friends.
Today IMVU is asocial entertainment product where our customersuse 3D avatars to meet people, chat, create cool stuff—AKA UGC--, and play games with their friends.
But we started as an add-on…
…to products like AOL Instant Messenger, adding 3D avatars to text-based instant messaging. Unfortunately for us, we failed!
It turned out that we built something our customers didn’t want. But we listened to customer feedback, and began changing our product to suit their needs.
We were doing the first parts of Customer Development: Customer Discovery and Customer Validation.Customer Discovery: ensuring the product solves a problem for a group of customersCustomer Validation: Ensuring that group of customers is big enough to build a business
And our product development process involved one big weekly meeting to update each other on project status. Our development cycles were 2 months long.
We were trying to find a recipe for a product people would like enough to buy, and then build a business on top of that. The team was small and well coordinated, and it worked!
After many trials, we found a decent recipe! It wasn’t the best in the world, but it was certainly edible.
And the numbers looked pretty good, too… so we thought we could run with this recipe, and we decided to scale it. We thought we could take lots of this dough, this sauce, and this cheese and just make a lot of it… but we didn’t think about changing the recipe to suit this scaling plan, and
But clearly, if our goal was to scale, we didn’t do it very well.
Something wasn’t working.As it turns out…
What got you here won’t always get you there.
When you take the recipe and try to scale it up, you end up with something mediocre. You can’t just multiply the amounts of ingredients. You have to adjust the ratios in your recipe, often the cooking temperature and time, sometimes the cooking method…
When you take the recipe and try to scale it up, you end up with something mediocre. You can’t just multiply the amounts of ingredients. You have to adjust the ratios in your recipe, often the cooking temperature and time, sometimes the cooking method…So what happened in our case? We had one person in charge of the sauce, one person in charge of the cheese, and another person in charge of the doughEach of those people thought they could manage their part of the product recipe separately and come up with a bigger version of the original pizza. But we didn’t have a single person in charge of how the entire pizza recipe would come together into something that people would really like and want to pay for. AND, we were GROWING!
And the product development process that worked for a small, focused team
…wasn’t working for our larger and fast-growing team.
Here’s a way to visualize what was going on from our customers’ perspective: I don’t know how many of you have used IMVU, but most of you probably know iTunes…Imagine trying to buy a music track, and instead of the simple process you’re used to…
…aweb browser launches, obscures the iTunes UI, and forces you through a web-based purchase process, which even if you complete successfully, doesn’t leave you in a position to listen to the track you just purchased.This is a situation our customers were intimately familiar with …
This is the previous version of the IMVU 3D chat client. You can see we’ve got the ability to have multiple 3D chat’s happening, cool… and we’ve got a buddy list…okay, and wait—what’s that?
An inventory attached to the buddy list? Well that feels sort of “bolted on”, but alright… So let’s say that you’re chatting and you want to buy a snazzy new shirt: first of all, how do you think you would buy something here? Anyone? If you manage to find the “shop catalog” button—bully for you! Now hopefully your friends won’t be too insulted as you leave them, perhaps permanently, and we pop a web browser right over the top of the IMVU chat client UI
Oops. Many of our customers got lost at this point, never to find there way back into our core experience.
We were held prisoner by a couple of things.
Our technology was standing in the way of us being able to respond to our customers—due to accumulated technical debt from our early “discovery” mode product development.
And fixing our UI infrastructure was a project that would require a large, coordinated effort that our existing PROCESS couldn’t support.
Sort of a Catch-22.
Here are some of the other issues and problems:Lack of strong, consistent product ownershipToo much focus on individual business metricsInability to make big feature changes—no one product owner or team had enough resources to make a big change. No coherent full-product visionWe’d outgrown our product development process
It all might have been comic…if it hadn’t been so tragic for our customers and our business.
So we decided to try something new and CRAZY!
LEARN FROM OUR MISTAKES!
We consciously took stock of our situation, and decided to make some big changes based on our experience.Two importantchanges were 1) we hired a one person to be responsible for the entire customer experience, with responsibility and a mandate to make big changes, and2) We updated our product development process.
We decided to usethe same Lean Startup philosophy that grew the company in the early days to improve and scale our development process. This is the Build Measure Learn loop.We figured, if it works for building cars and our first 3d Chat client, there’s no reason it shouldn’t work for building an efficient software product development team as well.
So the plan was to build, measure, and learn as quickly as possible, and incorporate new innovations into our process each sprint.
We ravamped the UI infrastructure that was so rife with technical debt, so we could build new UI quickly and efficiently using HTML and JavaScript.
And the same teams that were mired before become what our product owners now call the most productive teams they’ve ever worked with.
And we did it! We found a great recipe…And our customers loved it.
And the numbers look pretty good, too.
So how did we do it? We made a lot of changes in the company; here are some of the changes to our product development process.
Our product development process is built on a 3-week sprint cycleRemember the build-measure-learn loop? We’ve found that 3 week sprints are ideal for our teams.
Scrum facilitates face to face communication, and the daily standup is an opportunity to re-emphasize our commitments to each other and to the team. We say what we accomplished yesterday, what we are committing to get done today, and whether we are blocked in any way. We also take time for follow-up discussions on any topic people want to bring up.Everyone leaves the meeting knowing the exact status of the projects we’re working on.We do this in 15 minutes or less per day.
Planning meeting…
Artifacts – a shared task board
Artifacts – a burndown chart for tracking progress
Let’s talk about some of the tactics we use successfully at IMVU
Standardize.Shipping containers are all the same size. This is because they stack better, and are easier to manage efficiently.But our teams were all doing something different…
Wefound that when our teams were doing things their own way, they didn’t work together that well. Team workflows were too different; it was hard to swap team members and manage different process flows, and it was just harder for everyone to understand what we were working on, and why.So we started with a standardized Scrum process, and now we mange the ongoing evolution of that process.Then it was… Team members understand processes for any team Easy to swap team members Easy to coordinate schedules Easier to share best practices
Changing and evolving your process, is, by the way, in conflict with most dogmatic or zealous approaches to project management.So we avoid dogma.For example, we decided that locking down the sprint backlog at the start of the sprint wasn’t working for us. Sometimes we need to react quickly to marketing needs or prioritize critical work. Unexpected things happen, and Scrum—or any other methodology--practiced dogmatically, doesn’t accommodate that very well.Given that we’re committed to continuous improvement of our process, we avoid dogma at all costs.
So we call attention to changes in the sprint backlog daily in scrum and decide as team whether to accept the new work into the sprint.
Focused Meeting of Key StakeholdersSolution for a successful planning meetingProduct Owner, QA, Tech Lead, Designer pre-plan togetherReview draft design documents Incorporate different viewpoints and approaches Then revise to align documents
Ground Rules for Planning MeetingsWe want our teams to have a shared understanding of the sprint projects Full team reviews detailed project planning Planning takes 2-6 hours Discussion, disagreement, new ideas, learning Project scope changes Detailed: we dive into the code and project designsFoster engagement during planningNo laptops or cell phonesNo side conversations.Share the keyboard: take turns driving the meetingTake breaks, bring in food and refreshments
Something that deserves special mention is STAKEHOLDER AGREEMENTWe found that time spent to complete tasks was often different than planned, making sprint success difficult to predictSolution: two engineers + technical lead must agree on task durationFosters engagement, discussion, and debate, and the result is a deeper understanding of task requirementsAccomplishes the same engagement as using story points and playing planning poker.
And the doors are locked and all the cold Coke Zero is held outside, until they agree. ;)
We’ve found recently that a good target for team size is about 4 engineers per team.Communication overhead increases quickly as you add people, and since scrum is all about lightweight, face-to-face communication, adding team members can quickly cause unforeseen problems.We’ve found that about 4 engineers is the sweet spot for optimizing our ability to get things done efficiently and with high quality.
However, we learned that the hard way, but in 2 easy steps:We created a great process…
2) We followed our process, and got into a comfortable routine.We gradually increased our team size, and incorporated new practices to accommodate for subtle changes that were happeningTeam made an optimization to reduce interruptions, based on a Best Practice from another team, allowing two team members to only fix broken tests (we use TDD).Other team members were writing feature code more efficiently; fewer interruptions.
Oops.Things got bad slowlyOne group created problems that another group had to solveNo immediate feedback loopWe failed to understand the impact of an underlying infrastructure problem Team too big—happened gradually
Learn from your mistakes (and your successes)Pay attention to what works and what doesn’t Created best practice for team size: max 4 eng Began using story points Objective, high-level measure of velocity Early signal of success/failure, even if team “seems” fine Faster response time
Over time you might develop some ALWAYS’SWhat is an always’s you ask? These are things we do for every project, always.Remind yourselves about these—write them on the whiteboard during your planning meeting!(Planning Assumptions on the whiteboard)
We also write our planning assumptions on the whiteboard.We make our assumptions publicThis Reduce surprises, ensures engagement, helps catch errors.Making these assumptions explicit means it’s harder to forget planned vacations, conferences, and other events that might affect planning. It also sets expectations for how much time each engineer will be contributing to achieving the team goals that sprint.
This is all part of our Planning Technology
This is one of our early scrum task boards.
A later version of our scrum task board:BiggerPainter’s tape5 columns (Added QA + “New”)“New” column: We realized we were in charge of our destiny, and that we wanted to accommodate new work coming into the sprint
In planning, we needed to refer to the old board AND make a new board.Voila: the temporary task board
We spared no expense and found removable artists tape and black foam core…And this board has some *sweet* features:“New” columnProject Follow-up LanePhysical size limits number of storiesEasy to add/remove tasksEasy to meet, collaborate, plan workEasy to move to meeting roomsEasy to buildHard to work with if you are remote!
An online board is helpful with people working remotely from home or other locations
Context Matters: Some of our process works because of the particular context we have at a given time.Context changes! Some of our greatest failures result from following our process. You have to know when to deviate from your process. You have to always remember that you are in control, you are driving.
A map can be a useful guide, but it is not a substitute for paying attention to what is going on. If you follow this map without thinking about it, you might run into problems.Process is like a map.Your process is not a replacement for being engaged and paying attention!
Plan your route! Ensure that you are headed to the right destination. What your process or plan tells you is the right offramp, may not be.Process is not a substitute for engagement.Engage!Be conscious!Expect the unexpected.Change your process in subtle ways that get people to engage…Start using story points, for example…Any change you make will create a problem for the team to solve, and require people to re-engage