This presentation is a continuation of a "What To Do Once You Have an Idea". It explores a process of defining and building an MVP. It emphasizes building an MVP in a sustainable way while avoiding taking on unnecessary Product, Technical, Infrastructure and Process Debt. It also looks at the options of utilizing tools for effective Debt management.
Are you ready to build an MVP? Where do you start? How do you know what features to build? How do you know how many people you need to build it? How do you know that they are building a right thing in a right way? This presentation and conversation will explore strategies for assembling effective teams for building and deploying an MVP while incurring minimal Product and Technical Debt. We will also discuss implementing an effective process to make sure that your MVP will be built on time and on target.
A Minimum Viable Product (MVP) is doing the smallest possible thing in order to learn. You'll make the least amount of effort to get the maximum amount of validated customer learning. The road to launching a web or mobile application usually starts with the creation of a minimum viable product (MVP).
A MVP is more than a prototype but less than a fully-featured app and can help you engage a particular audience, such as potential investors, strategic partners, hires, or test users.
Determining what features should be included in or excluded from your MVP is a critical task with major ramifications.
A Minimum Viable Product (MVP) is doing the smallest possible thing in order to learn. You'll make the least amount of effort to get the maximum amount of validated customer learning. The road to launching a web or mobile application usually starts with the creation of a minimum viable product (MVP).
A MVP is more than a prototype but less than a fully-featured app and can help you engage a particular audience, such as potential investors, strategic partners, hires, or test users.
Determining what features should be included in or excluded from your MVP is a critical task with major ramifications.
Are you ready to build an MVP? Where do you start? How do you know what features to build? How do you know how many people you need to build it? How do you know that they are building a right thing in a right way? This presentation and conversation will explore strategies for assembling effective teams for building and deploying an MVP while incurring minimal Product and Technical Debt. We will also discuss implementing an effective process to make sure that your MVP will be built on time and on target.
A Minimum Testable Product (MTP) is doing the smallest possible thing in order to learn and test. You'll make the least amount of effort to get the maximum amount of validated customer learning. The road to launching a web or mobile application usually starts with the creation of a minimum viable product (MTP).
A MTP is more than a prototype but less than a fully-featured app and can help you engage a particular audience, such as potential investors, strategic partners, hires, or test users.
Determining what features should be included in or excluded from your MTP is a critical task with major ramifications.
This presentation explores new ways of looking at failure in Startups. Specifically concept of "unfail" or "unfailure" is presented and explained. Lean Startup elements are connected with a failure scenarios and lessons learned
Are you ready to build an MVP? Where do you start? How do you know what features to build? How do you know how many people you need to build it? How do you know that they are building a right thing in a right way? This presentation and conversation will explore strategies for assembling effective teams for building and deploying an MVP while incurring minimal Product and Technical Debt. We will also discuss implementing an effective process to make sure that your MVP will be built on time and on target.
A Minimum Viable Product (MVP) is doing the smallest possible thing in order to learn. You'll make the least amount of effort to get the maximum amount of validated customer learning. The road to launching a web or mobile application usually starts with the creation of a minimum viable product (MVP).
A MVP is more than a prototype but less than a fully-featured app and can help you engage a particular audience, such as potential investors, strategic partners, hires, or test users.
Determining what features should be included in or excluded from your MVP is a critical task with major ramifications.
A Minimum Viable Product (MVP) is doing the smallest possible thing in order to learn. You'll make the least amount of effort to get the maximum amount of validated customer learning. The road to launching a web or mobile application usually starts with the creation of a minimum viable product (MVP).
A MVP is more than a prototype but less than a fully-featured app and can help you engage a particular audience, such as potential investors, strategic partners, hires, or test users.
Determining what features should be included in or excluded from your MVP is a critical task with major ramifications.
Are you ready to build an MVP? Where do you start? How do you know what features to build? How do you know how many people you need to build it? How do you know that they are building a right thing in a right way? This presentation and conversation will explore strategies for assembling effective teams for building and deploying an MVP while incurring minimal Product and Technical Debt. We will also discuss implementing an effective process to make sure that your MVP will be built on time and on target.
A Minimum Testable Product (MTP) is doing the smallest possible thing in order to learn and test. You'll make the least amount of effort to get the maximum amount of validated customer learning. The road to launching a web or mobile application usually starts with the creation of a minimum viable product (MTP).
A MTP is more than a prototype but less than a fully-featured app and can help you engage a particular audience, such as potential investors, strategic partners, hires, or test users.
Determining what features should be included in or excluded from your MTP is a critical task with major ramifications.
This presentation explores new ways of looking at failure in Startups. Specifically concept of "unfail" or "unfailure" is presented and explained. Lean Startup elements are connected with a failure scenarios and lessons learned
This presentation explores ways to effectively market MVP.
It explores various Marketing Mix concepts applied across traditional and digital marketing channels. Significant
2. Testing Your MVP
3. Design of Experiments
4. Marketing Your MVP
5. PPC Funnel
6. Usability Testing
7. Usability Study
Erste Bank — How to Cut off Development Times & Get Feedback From Real Users,...Agile Austria Conference
The talk will be showing through examples how to get immediate feedback from real users while skipping the development period and use Design Sprints and prototyping for it. It shows the benefits of getting user experience first and how to incorporate this in real products development life while living the Scrum cycles.
The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at GV, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more—packaged into a battle-tested process that any team can use.
This talk is about understanding the team dynamics at play on a Design Sprint. It briefly explains what is a Sprint, when to do one and who should be in it, as well as its structure. Then, it explains what makes it so successful, by understanding the mechanics that make it work.
I gave this talk at a local meetup, called Braga.Product. I hope to have the video of this talk available soon.
Using a Design Sprint to Accelerate Innovation - Agile AustraliaRob Scherer
Last year, we worked on a project where we trialled the design sprint process created by Google Ventures.
We’d identified an opportunity. We had a segment of the market that we weren’t serving particularly well and when we had a look around, it seemed that nobody else was either. The area was ripe for disruption and we believed that if we didn't disrupt ourselves, somebody else would.
This talk covers:
1. what a design sprint is
2. some of the modifications we made to the Google Ventures process
3. a few practical tips that might help if you're running your own sprints
Discover more to learn detail with google design sprint, great tools to maximize and validate your idea with lack of creativity and enhancing collaboration.
Should you follow what others are doing ,just becuase it works for them?
Instead ,choose from Innovative models and Practices best suited to your business model.
#innovation #gartner #leanstartup #designthinking #agileleadership #leadershipexcellence #innovationstrategy #innovationleadership
Infographic: How do you know if a Design Sprint is right for you?Fresh Tilled Soil
The most common goal of a Design Sprint is to assess an opportunity and reduce the risk of failure. That sounds great in the abstract, but what does this really mean in practice? When and for what challenges one use a Design Sprint? This infographic walks you through a process to determine if a Design Sprint is appropriate for your organization or challenge.
New York Bestseller Jake Knapp’s book, Sprint, explores how companies and teams can replicate Google’s sprint process to solve a problem within five days.
So how does a design sprint actually work, and how can you use a sprint to devise effective solutions in such a short period of time?
Enhance your productivity through design sprints, you’ll learn:
- What is a Design Sprint
- Design sprint case studies and success stories
- How you can run a design sprint effectively
Kickstart Your Product with a Design Sprint by thestartupfactory.techProduct School
In a fluid and fast-paced world of Product, Product Management and building Product Roadmaps, even the most skilled of teams can struggle with a specific proposition, have misaligned priorities or simply get stuck from time to time. That's where the Design Sprint comes in – a process born at Google Ventures. This presentation unravels how a Design Sprint can get you and your team back on track in just 5 days. Not only that, but get a sneak peek into Design Sprint 2.0: now 20% faster than the original!
The Design Sprints are a 2-5 days process for answering critical business questions through design, prototyping, and testing ideas with customers.
In this keynote I present you the Google Venture Design Sprints Methodology.
Implementing Dual-Track Agile :: Lessons from the trenches @ITSpring.by May 2019Pedro Teixeira
Evermore people are talking about Discovery and Hypothesis-driven approaches. But where do you start? What do they really mean?
Pedro will share with us how he moved away from a 2-year delivery roadmap by enabling his Engineering teams to do a Dual Track Agile. A real case-study!
Key Learning Points:
- Understand what Dual Track Agile is
- Learn why Pedro and his team decided to use it at OutSystems
- Know what was the strategy in place for the Change Management
- Understand their failures and what they have learned with it
- Identify some Common Pitfalls
- Understand the importance of cadence for alignment and trust
- Understand the importance of building (truly) autonomous teams
A design sprint is a five-phase framework that helps answer critical business questions through rapid prototyping and user testing. Sprints let your team reach clearly defined goals and deliverables and gain key learnings, quickly. The process helps spark innovation, encourage user-centered thinking, align your team under a shared vision, and get you to product launch faster.
In this talk, Suze explores a case study from her recent work in a London agency, where, working for a large retail client, the programme of work moved from a project-based delivery model incorporating Scrum to a more product-based model. Drawing on aspects of Kanban, Design Thinking and Lean Startup, and implementing a dual-track agile approach, the team is now ‘thinking more product’.
Suze will delve into how the organisation has shifted to this model and how it coped with the change. She will talk through some of the difficulties that she experienced along the way and how these issues were mitigated, and provide take away techniques to help in your organisations.
More details:
https://confengine.com/agile-india-2019/proposal/8036/thinking-more-product-moving-from-scrum-to-a-dual-track-agile-approach
Conference link: https://2019.agileindia.org
I was talking at a GDG event on Design Sprint about how we can reduce the lead time on developing new ideas and products and build prototypes, test and validate.
Are you ready to build an MVP? Where do you start? How do you know what features to build? How do you know how many people you need to build it? How do you know that they are building a right thing in a right way? This presentation and conversation will explore strategies for assembling effective teams for building and deploying an MVP while incurring minimal Product and Technical Debt. We will also discuss implementing an effective process to make sure that your MVP will be built on time and on target.
As your business grows, it becomes necessary to expand the teams within your organization to maintain productivity at an optimal level.
Business and Technology team growth are not interdependent. As software products need regular revision and improvements to benefit your business and boost company scales, technology team scaling is inevitable to boost the growth and development of your business. However, it is critical to pick the right time, model and organizational structure to start scaling your product and technical teams, so as not to fail this process overall.
Technology Team Structure and Organizational Process
Technology Teams Separation of Concerns
Technology Team Budget and Scaling Models
Appropriate Technology Team Separation, Reporting and Relative Headcount
Technology and Business Team Engagement and Collaboration
This presentation explores ways to effectively market MVP.
It explores various Marketing Mix concepts applied across traditional and digital marketing channels. Significant
2. Testing Your MVP
3. Design of Experiments
4. Marketing Your MVP
5. PPC Funnel
6. Usability Testing
7. Usability Study
Erste Bank — How to Cut off Development Times & Get Feedback From Real Users,...Agile Austria Conference
The talk will be showing through examples how to get immediate feedback from real users while skipping the development period and use Design Sprints and prototyping for it. It shows the benefits of getting user experience first and how to incorporate this in real products development life while living the Scrum cycles.
The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at GV, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more—packaged into a battle-tested process that any team can use.
This talk is about understanding the team dynamics at play on a Design Sprint. It briefly explains what is a Sprint, when to do one and who should be in it, as well as its structure. Then, it explains what makes it so successful, by understanding the mechanics that make it work.
I gave this talk at a local meetup, called Braga.Product. I hope to have the video of this talk available soon.
Using a Design Sprint to Accelerate Innovation - Agile AustraliaRob Scherer
Last year, we worked on a project where we trialled the design sprint process created by Google Ventures.
We’d identified an opportunity. We had a segment of the market that we weren’t serving particularly well and when we had a look around, it seemed that nobody else was either. The area was ripe for disruption and we believed that if we didn't disrupt ourselves, somebody else would.
This talk covers:
1. what a design sprint is
2. some of the modifications we made to the Google Ventures process
3. a few practical tips that might help if you're running your own sprints
Discover more to learn detail with google design sprint, great tools to maximize and validate your idea with lack of creativity and enhancing collaboration.
Should you follow what others are doing ,just becuase it works for them?
Instead ,choose from Innovative models and Practices best suited to your business model.
#innovation #gartner #leanstartup #designthinking #agileleadership #leadershipexcellence #innovationstrategy #innovationleadership
Infographic: How do you know if a Design Sprint is right for you?Fresh Tilled Soil
The most common goal of a Design Sprint is to assess an opportunity and reduce the risk of failure. That sounds great in the abstract, but what does this really mean in practice? When and for what challenges one use a Design Sprint? This infographic walks you through a process to determine if a Design Sprint is appropriate for your organization or challenge.
New York Bestseller Jake Knapp’s book, Sprint, explores how companies and teams can replicate Google’s sprint process to solve a problem within five days.
So how does a design sprint actually work, and how can you use a sprint to devise effective solutions in such a short period of time?
Enhance your productivity through design sprints, you’ll learn:
- What is a Design Sprint
- Design sprint case studies and success stories
- How you can run a design sprint effectively
Kickstart Your Product with a Design Sprint by thestartupfactory.techProduct School
In a fluid and fast-paced world of Product, Product Management and building Product Roadmaps, even the most skilled of teams can struggle with a specific proposition, have misaligned priorities or simply get stuck from time to time. That's where the Design Sprint comes in – a process born at Google Ventures. This presentation unravels how a Design Sprint can get you and your team back on track in just 5 days. Not only that, but get a sneak peek into Design Sprint 2.0: now 20% faster than the original!
The Design Sprints are a 2-5 days process for answering critical business questions through design, prototyping, and testing ideas with customers.
In this keynote I present you the Google Venture Design Sprints Methodology.
Implementing Dual-Track Agile :: Lessons from the trenches @ITSpring.by May 2019Pedro Teixeira
Evermore people are talking about Discovery and Hypothesis-driven approaches. But where do you start? What do they really mean?
Pedro will share with us how he moved away from a 2-year delivery roadmap by enabling his Engineering teams to do a Dual Track Agile. A real case-study!
Key Learning Points:
- Understand what Dual Track Agile is
- Learn why Pedro and his team decided to use it at OutSystems
- Know what was the strategy in place for the Change Management
- Understand their failures and what they have learned with it
- Identify some Common Pitfalls
- Understand the importance of cadence for alignment and trust
- Understand the importance of building (truly) autonomous teams
A design sprint is a five-phase framework that helps answer critical business questions through rapid prototyping and user testing. Sprints let your team reach clearly defined goals and deliverables and gain key learnings, quickly. The process helps spark innovation, encourage user-centered thinking, align your team under a shared vision, and get you to product launch faster.
In this talk, Suze explores a case study from her recent work in a London agency, where, working for a large retail client, the programme of work moved from a project-based delivery model incorporating Scrum to a more product-based model. Drawing on aspects of Kanban, Design Thinking and Lean Startup, and implementing a dual-track agile approach, the team is now ‘thinking more product’.
Suze will delve into how the organisation has shifted to this model and how it coped with the change. She will talk through some of the difficulties that she experienced along the way and how these issues were mitigated, and provide take away techniques to help in your organisations.
More details:
https://confengine.com/agile-india-2019/proposal/8036/thinking-more-product-moving-from-scrum-to-a-dual-track-agile-approach
Conference link: https://2019.agileindia.org
I was talking at a GDG event on Design Sprint about how we can reduce the lead time on developing new ideas and products and build prototypes, test and validate.
Are you ready to build an MVP? Where do you start? How do you know what features to build? How do you know how many people you need to build it? How do you know that they are building a right thing in a right way? This presentation and conversation will explore strategies for assembling effective teams for building and deploying an MVP while incurring minimal Product and Technical Debt. We will also discuss implementing an effective process to make sure that your MVP will be built on time and on target.
As your business grows, it becomes necessary to expand the teams within your organization to maintain productivity at an optimal level.
Business and Technology team growth are not interdependent. As software products need regular revision and improvements to benefit your business and boost company scales, technology team scaling is inevitable to boost the growth and development of your business. However, it is critical to pick the right time, model and organizational structure to start scaling your product and technical teams, so as not to fail this process overall.
Technology Team Structure and Organizational Process
Technology Teams Separation of Concerns
Technology Team Budget and Scaling Models
Appropriate Technology Team Separation, Reporting and Relative Headcount
Technology and Business Team Engagement and Collaboration
This is a flash report of Agile2018 by The HIRO!LINE Corporation
This is a flash report of Agile2018 by The HIRO!
「Agile2018」の参加レポート(速報版)です。
Agile2018
https://www.agilealliance.org/agile2018/
Please feel and enjoy atmosphere of the latest Agile :)
agile, agile2018, linedev
Keynote Evento TestingUY 2018 - The Art of Excellence Adding value as an IT p...TestingUy
Expositor: Derk-Jan De Grood
Resumen: In order to distinguish themselves and meet customer expectations organizations need to embrace change. In his keynote Derk-Jan de Grood will explain how Continuous Delivery, DevOps and Scaling Agile aim to effectively react to disruptive innovations, but introduce new challenges. Organization have a need for Visionary’s, Explorers and Experts to make the transition. Develop yourself and your team in order to keep adding value and embrace the new opportunities that arise.
Slides from a product management training workshop with our partners at the Department of the Interior's Office of Natural Resources Revenue as a part of work together on revenuedata.doi.gov
Building a successful DevOps solution requires a holistic view of your development ecosystem plus solid technology that can support your organization today and in the future. Learn how to start defining your own successful DevOps solution and how to position Helix to be at the center of it all.
[QE 2018] Paul Gerrard – Automating Assurance: Tools, Collaboration and DevOpsFuture Processing
The Digital Transformation is real. It is having a profound effect on how business is done and the nature of the systems required to deliver productive customer experiences and consequent business benefits. The demand for flexible and rapid delivery of software and systems is there. Software development teams can deliver if they adopt the disciplines of Continuous Delivery, DevOps and in-production experimentation. The barrier to achieving success in the software delivery process is likely to be the inability of testers to align testing and automated testing in particular to the development processes. Our track record in test automation is not good enough. In order to succeed a new way of thinking about testing is required, and the New Model of Testing offers a way of identifying the elements of the test process that must be ‘shifted left’. This does not necessarily mean testers move, but rather that the thinking processes must move.
During this lecture, Paul has shown that it is possible that users, BAs, and developers take some responsibility in this area. The New Model applies to all testing, whether performed in development, integration, system or user testing, by people or tools.
this slides go with the webinar linked below. In it we discuss some of the things you need to consider and methods to use when looking into upgrading your systems.
https://youtu.be/TK8F-oLXZTw
Purpose Before Action: Why You Need a Design Language Systemcreckling
Abstract: Ask two designers to design the same user interface and you will likely end up with two very different designs and interactions on the page. Ask two developers to implement that page and you will end up with different code, too! And that, in a nutshell, is why you need a system.
Have you ever wondered what it takes to build your own design language system? It sounds intimidating, but it's not!
Link: https://uxpabostonconference2018.sched.com/event/E2NS/purpose-before-action-why-you-need-a-design-language-system
Agile and CMMI: Yes, They Can Work TogetherTechWell
There is a common misconception that agile and CMMI cannot work together. CMMI is viewed as a documentation heavy, slow, process-driven model—the polar opposite of agile principles. The cost of documentation for an appraisal is viewed as another drawback. Join Ed Weller to see why a large organization chose to use the practices in the CMMI to complement agile, and a formal appraisal to improve and evaluate their performance. When mixing approaches that seem contradictory, the first step is to understand the benefits, drawbacks, and cost of each approach and then identify complementary additions. This includes myth busting the misperceptions about both agile and CMMI. The second step, using a formal CMMI appraisal to evaluate organizational performance, requires an understanding of the CMMI model that goes beyond a “checklist approach” requiring extensive documentation. Using lean principles, the appraisal team minimized “appraisal documentation” by using the day-to-day team output. Ed shows that agile and CMMI can be complementary due to executive leadership, lean implementation, and organization training, as demonstrated by a formal appraisal and business results.
Debunking Four Myths of Agile Development WebcastCompuware
Based on lessons learned at Compuware, many of the myths that are keeping companies from experiencing the transformational benefits of using Agile on the mainframe are dispelled during this presentation. The webcast aims to equip you with the knowledge you need to begin your organization’s journey to Agile.
As companies evolve to adopt, integrate and leverage software as the defining element of their success in the 21st century, a rash of processes and methodologies are vying for their product teams' attention. This Session will give you guidelines on how to start an innovative business lean and fast by using design thinking, lean and agile approaches and how to build high-performing digital product teams. The session will finish with discussing Lean Agile meets Design Thinking to give a meaningful conclusion.
Using Lean Thinking to Increase the Value of AgileExcella
“Agile doesn’t have a brain.” This quote from Bill Scott, VP, Business Engineering and Product Development at PayPal, is provocative for sure, but it spotlights the notion that in most organizations Agile is primarily applied as a downstream engineering approach that isn’t inherently concerned with optimizing product design and user experience, the determinants of value to the customer. The learning cycles that form the basis of Scrum are focused on verification and validation of user needs as they are already identified in the backlog’s user stories, but provide little guidance on how to translate organizational goals and customer needs into the backlog’s content and relative priorities in the first place. As a result, the danger persists that Agile teams end up very efficiently building products that implement an incomplete and subjective perception of customers’ wants and needs.
This presentation explores how Lean thinking can expand the “inspect and adapt” cycles of Agile development beyond implementation and help to systematically determine which features and design choices really provide the greatest customer value. After a brief introduction to Lean concepts, the presentation discusses how Lean approaches product development as a series of hypotheses about customers’ value perception and builds on Agile’s rapid iterative delivery of working software to test these assumptions. Finally, it highlights ways to derive testable assumptions from organizational goals, such as the Lean UX Hypothesis Statement template and Gojko Adzic’s Impact Mapping.
Design Studios are a popular method for getting product teams together to focus on design. Design Studios are more than just getting people together to sketch and critique. In this workshop, Brian Sullivan, author of The Design Studio Method: Creative Problem Solving with UX Sketching, will share his secrets to planning, running, and leading successful Design Studios
In this workshop, you will learn:
Ways to creative and evaluate sketches quickly
See different tools to get you started
The 9 Steps of a Design Studio
Stories of success and failure in Design Studio
How to deal with difficult people/strong personalities
We will have plenty of time for your burning questions, too.
This talk will offer tactics for you and your team to advance the role of UX in your organization. Good UX is good business. It is not optional for achieving better outcomes. So why do mature enterprises and fledgling startups alike keep minimizing or neglecting it? We will cover case studies, statistical evidence, and anecdotal experiences that show how UX helps the business go fast forever. Finally, by the end of this talk you will be able to craft a concise business argument that WILL make UX a non-negotiable for your organization.
Ben Walters - Creating Customer Value With Agile Testing - EuroSTAR 2011TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Creating Customer Value With Agile Testing by Ben Walters. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
So Now You’re a UiPath Developer – What’s Next?” What Role do You Play as Dev...DianaGray10
As a UiPath Developer, what are the important tasks you should consider to be part of your job requirements? Join this session to find out more and ask questions from experienced experts. Topics include:
Where's your starting point?
Are you using a broad use case or a detailed PDD?
Are you involved in the Definition/Brainstorming?
Are you building and deploying or are you building and sending?
Are you in charge of maintaining? What should the maintenance-to-build ratio be?
What's your interaction with the C-Suite? What are the KPI requirements?
Speakers:
Chris Bolin, Senior RPA Engineer @ Gamestop and 2X UiPath MVP
Mason Turvey, Intelligent Automation Lead, Academy Bank and UiPath MVP
[DSC Croatia 22] How we create and leverage data services in GitLab - Radovan...DataScienceConferenc1
Providing a walkthrough over the process of creating, improving, and scaling the Data product using a modern DevOps stack. Exposing details of the use case how we embrace the open-source philosophy to help us provide faster time to market. Will discuss how to use the advantage of the internal product to make us more agile in the daily job of creating great data products.
This presentation is designed to explain the differences between Startup and Corporate career choices for Engineering and Computer Science graduates.
It explores interviewing process and offer negotiations
Technical Debt is a gap between Computer Science and Software Engineering. Common understanding of causes for the Technical Debt is centered on the careless software development choices for the sake of speed and expediency. However Technical Debt usually goes beyond just Technology. This presentation covers the origins of Technical and Product Debt, how to manage it and mitigate it
Startup Failure Is Not What You Think It Is (Startup Week)Sergey Sundukovskiy
This presentation explores new ways of looking at failure in Startups. Specifically concept of "unfail" or "unfailure" is presented and explained. Lean Startup elements are connected with a failure scenarios and lessons learned
Capturing and reporting on data provides critical insights that ultimately drive the business. However, the myriad of data points, tools and technology and stages of business make choosing an approach for analytics a complex question. In this talk, Sergey will use a primary case study and other examples of SaaS companies to:
Explore how you can collect and analyze key metrics such as Customer Acquisition Cost (CAC), Lifetime Value (LTV), Churn, Monthly Recurring Revenue (MRR), Average Sales Price (ASP).
Consider different technical approaches to capturing, integrating data, reporting including various types of tools and internal data
Examine a framework for selecting your own stack from project inception, through evaluation process and eventual implementation and discuss how we evaluated what to use in this particular case and why
Consider how these choices likely will vary based on stage of the business
Discuss approaches to more complex issues like cross device and attribution
Pitching is a key skill of every successful entrepreneur. How do you communicate your business clearly to employees, customers, and investors? How to put together a pitch deck? What are some common pitching mistakes that make you look inexperienced? What is the best way to pitch your business?
Capturing and reporting on data provides critical insights that ultimately drive the business. However, the myriad of data points, tools and technology and stages of business make choosing an approach for analytics a complex question. In this talk, Sergey will use a primary case study and other examples of SaaS companies to:
Explore how you can collect and analyze key metrics such as Customer Acquisition Cost (CAC), Lifetime Value (LTV), Churn, Monthly Recurring Revenue (MRR), Average Sales Price (ASP).
Consider different technical approaches to capturing, integrating data, reporting including various types of tools and internal data
Examine a framework for selecting your own stack from project inception, through evaluation process and eventual implementation and discuss how we evaluated what to use in this particular case and why
Consider how these choices likely will vary based on stage of the business
Discuss approaches to more complex issues like cross device and attribution
This presentation explores new ways of looking at failure in Startups. Specifically concept of "unfail" or "unfailure" is presented and explained. Lean Startup elements are connected with a failure scenarios and lessons learned
This presentation explores ways to effectively market MVP.
It explores various Marketing Mix concepts applied across traditional and digital marketing channels. Significant
2. Testing Your MVP
3. Design of Experiments
4. Marketing Your MVP
5. PPC Funnel
6. Usability Testing
7. Usability Study
This presentation covers video platform choices. It also looks at build it yourself options. Additional topics include video content screening and social distribution options.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
6. Defining MVP
6
Eric Ries defines MVP as “…that version of a new product
which allows a team to collect the maximum amount of
validated learning about customers with the least effort.”
Minimal
Product nobody
wants to use
Viable
Product built
by companies
that have no
financial limitations
MVP
9. MVP vs. Prototype
MVP
Test Product Viability
Test Assumptions
Test the Market
Test Product Usability
Get User Feedback
Prototype
Demonstrate the Concept
Convince Others That You Are Serious
Get Seed Money
9
13. Ideal MVP
Mini-Me is an Ideal MVP
Core Functionality
Identical “DNA”
Same Major Features
Same Major Functionality
Same Usability
Not Up To Scale
Not As Pretty
13
15. MVP Attributes
Intelligent Design Concepts
Irreducible Complexity
Can’t Take Anything Away
Can’t Be Simpler
Most Efficient For What It Does
Most Efficient Wins
Most Efficient Survives
Path to Intent
Most Straightforward Path to Intent
15
18. Debt
Everything you want to do “Later” is DEBT
Let’s Document Later
Let’s Test Later
Let’s Architect Later
Let’s Refactor Later
Debt Misconceptions
All Debt is Bad
No Debt is Great
Taking on Debt Gets You There Faster
18
25. Support to Innovation Ratio
You Are in the Support Business
25
Support
(15%)
Innovation
(85%)
Support
(50%)
Innovation
(50%)
Support
(85%)
Innovation
(15%)
Year 1
Year 2
Year 3
26. Technical Debt Elements
Technical Debt Elements
Lack of Architectural Blueprint
Lack of Unit Testing
Lack of Integration Testing
Lack of Code Reviews
Lack of Starting Platform
Lack of Starting Framework
Lack of Technical Design
Lack of Development Recipes
26
33. Infrastructure Debt Elements
Infrastructure Debt Elements
No Utilizing IaaS/Pass
Lack of Monitoring
Lack of Redundancy
Lack of Disaster Recovery
Lack of Environment Separation
Dev Ops Debt Elements
Lack of Deployment Framework
Lack of Continuous Integration
Lack of Effective Source Control
33
37. Process Complication
Do Not Make It Complicated
Complicated = Bad
Complicated = Unsustainable
Complicated = Not Followed
Complicated = Edge Case Centric
Complicated ! = Useful
Complicated = Unintended Consequences
37
39. Planned vs. Agile
Planned Process
Exhaustive Planning (plan until you are exhausted)
Prescriptive
Document Centric
Agile Process
Iterative Planning
Non-prescriptive
Practice Centric
39
50. Private Beta
We Are Watching You
Hover Areas
Attention Areas
Click Areas
Used Featured
We Are Measuring You
Visit Duration
Hover Time
Return Frequency
50