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.
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.
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.
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 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 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.
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.
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.
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 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
Presentation from putitout event at Decoded London. Outlines the change to product development process to test ideas early through Lean and UX methods.
GROWtalks - Couples Counseling for Software Development - Joe Stump Sprint.lyDealmaker Media
Joe Stump is a seasoned technical leader and serial entrepreneur who has cofounded three venture-backed startups, was Lead Architect of Digg, and has invested in and advised dozens of companies. He is passionate about development processes, iterative product development, and building scalable web infrastructure.
Couples Counseling for Product DevelopmentJoe Stump
An introduction to Non-Blocking Development and how to get your entire business, from sales to software development, aligned to ship more product more quickly.
Lean UX + UX Strat, from UX Strat conference, September 2013Joshua Seiden
Slides from my talk at UX Strat, 2013. (www.uxstrat.com)
How to use Lean UX methods to execute on business, product, and design strategy.
I presented a slightly altered version a few days later at Fluxible 2013. (http://www.fluxible.ca)
How to Make the Best Product Decisions by XO Group Product ManagerProduct School
Making good decisions is a Product Managers secret weapon. Every day a Product Manager makes macro and micro decisions that enable their teams to design and build. It is uniquely the job because Product Managers tend to have the most context in a company.
From this workshop people learned frameworks of how to make good decisions and examples from how Jennifer Garfield from XO Group has done this at The Knot.
Reverse Chaos Method of Requirements Prioritisation Gena Drahun
Practical method of requirements prioritisation based on the Statistics of Product Success from Chaos Manifesto from Standish Group.
+ As bonus some thoughts and clarification of the definition of Minimum Viable Product and Minimum Viable Feature.
Presentation for UX Camp Amsterdam 2015, 9 September 2015.
Presentation for Agile Denver on September 28, 2009.
Abstract:
Everyone knows Agile is hard to do effectively. So how can it be simple?
It can't be simple, but keeping simple in mind can help avoid a number
of problems which tend to make agile harder! Confused? Then come to this
presentation which is designed to illuminate certain areas of agility
where teams and organizations tend to make things hard on themselves
rather than taking a simple approach.
"Simple Agile" is all about living the common agile phrase "Do the
simplest thing that works." This presentation will explore Simple Agile
planning, meetings, development, and testing along with other tangential
areas. The presentation combines some PowerPoint slides, some audience
participation and some group discussion. Come prepared to participate!
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!
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.
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.
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
The Role and Challenges of a PM in a New Industry by Elliptic PMProduct School
Main takeaways:
- Introduction to cryptocurrencies (from a Product perspective)
- Why are unexplored industries challenging?
- Output VS Outcome
- Agile VS Long term Roadmaps- Real-life challenges & case studies
What does it mean to be a test engineer?Andrii Dzynia
Test engineering is hard, even harder than software development. Being test engineer puts you in a wider context, with no clear boundaries. You have to find those by yourself. This requires courage. Courage to take action, courage to make mistakes. As a test engineer, you do mistakes every day. You do them so often that sometimes you feel you can predict the future. Scientific explanation to this phenomena is patterns recognition. It is an ability of our brain to match the information from a stimulus with information retrieved from memory. Defect prevention is hard. Together with technical skills one have to develop high social awareness. Working on safety nets never was so important, different types of checks on different levels to make sure software is reliable and serves its purpose to the variety of everyday use-cases. We know that life is so complex and sometimes complicated which makes it impossible to predict all possible outcomes and scenarios. But striving for excellence never was so important as nowadays in such an open, transparent and competitive environment.
Goal of my talk will be to show you my everyday job as a test engineer. Not only how to look for defects, but how to prevent them from happening. Not only how to automate tests(noun), but how to build safety nets to minimize end-user impact. Not only how to inform testing status but how to influence quality on company level.
What Is Global Product Development by RING Product ManagerProduct School
Matt England from RING discussed the process of developing electronic products in Asia and getting it to mass production. From identifying capable factories to demystifying working with Asian suppliers, this candid talk gave a behind-the-scenes look at developing, building and shipping a physical product from Asia.
Presentation from putitout event at Decoded London. Outlines the change to product development process to test ideas early through Lean and UX methods.
GROWtalks - Couples Counseling for Software Development - Joe Stump Sprint.lyDealmaker Media
Joe Stump is a seasoned technical leader and serial entrepreneur who has cofounded three venture-backed startups, was Lead Architect of Digg, and has invested in and advised dozens of companies. He is passionate about development processes, iterative product development, and building scalable web infrastructure.
Couples Counseling for Product DevelopmentJoe Stump
An introduction to Non-Blocking Development and how to get your entire business, from sales to software development, aligned to ship more product more quickly.
Lean UX + UX Strat, from UX Strat conference, September 2013Joshua Seiden
Slides from my talk at UX Strat, 2013. (www.uxstrat.com)
How to use Lean UX methods to execute on business, product, and design strategy.
I presented a slightly altered version a few days later at Fluxible 2013. (http://www.fluxible.ca)
How to Make the Best Product Decisions by XO Group Product ManagerProduct School
Making good decisions is a Product Managers secret weapon. Every day a Product Manager makes macro and micro decisions that enable their teams to design and build. It is uniquely the job because Product Managers tend to have the most context in a company.
From this workshop people learned frameworks of how to make good decisions and examples from how Jennifer Garfield from XO Group has done this at The Knot.
Reverse Chaos Method of Requirements Prioritisation Gena Drahun
Practical method of requirements prioritisation based on the Statistics of Product Success from Chaos Manifesto from Standish Group.
+ As bonus some thoughts and clarification of the definition of Minimum Viable Product and Minimum Viable Feature.
Presentation for UX Camp Amsterdam 2015, 9 September 2015.
Presentation for Agile Denver on September 28, 2009.
Abstract:
Everyone knows Agile is hard to do effectively. So how can it be simple?
It can't be simple, but keeping simple in mind can help avoid a number
of problems which tend to make agile harder! Confused? Then come to this
presentation which is designed to illuminate certain areas of agility
where teams and organizations tend to make things hard on themselves
rather than taking a simple approach.
"Simple Agile" is all about living the common agile phrase "Do the
simplest thing that works." This presentation will explore Simple Agile
planning, meetings, development, and testing along with other tangential
areas. The presentation combines some PowerPoint slides, some audience
participation and some group discussion. Come prepared to participate!
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!
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.
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.
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
The Role and Challenges of a PM in a New Industry by Elliptic PMProduct School
Main takeaways:
- Introduction to cryptocurrencies (from a Product perspective)
- Why are unexplored industries challenging?
- Output VS Outcome
- Agile VS Long term Roadmaps- Real-life challenges & case studies
What does it mean to be a test engineer?Andrii Dzynia
Test engineering is hard, even harder than software development. Being test engineer puts you in a wider context, with no clear boundaries. You have to find those by yourself. This requires courage. Courage to take action, courage to make mistakes. As a test engineer, you do mistakes every day. You do them so often that sometimes you feel you can predict the future. Scientific explanation to this phenomena is patterns recognition. It is an ability of our brain to match the information from a stimulus with information retrieved from memory. Defect prevention is hard. Together with technical skills one have to develop high social awareness. Working on safety nets never was so important, different types of checks on different levels to make sure software is reliable and serves its purpose to the variety of everyday use-cases. We know that life is so complex and sometimes complicated which makes it impossible to predict all possible outcomes and scenarios. But striving for excellence never was so important as nowadays in such an open, transparent and competitive environment.
Goal of my talk will be to show you my everyday job as a test engineer. Not only how to look for defects, but how to prevent them from happening. Not only how to automate tests(noun), but how to build safety nets to minimize end-user impact. Not only how to inform testing status but how to influence quality on company level.
What Is Global Product Development by RING Product ManagerProduct School
Matt England from RING discussed the process of developing electronic products in Asia and getting it to mass production. From identifying capable factories to demystifying working with Asian suppliers, this candid talk gave a behind-the-scenes look at developing, building and shipping a physical product from Asia.
Take a look at the spec for our battery shelf edge display
For more info please visit http://crystal-display.com/products/battery-powered-shelf-display/
Or contact us for more information via email on info@crystal-display.com or call +44(0) 1634 327420
Today in the workplace people have always used social learning to connect themselves to the information they need, whether that be in the lunch room, around the coffee machine or at the bar. Enhancing the level of learning within your organization requires outside of the classroom thinking. Here we discuss the variety of tools that can take learning connectivity to the next level.
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
Anti-patterns for not-so-smart processes: Avoiding the BPM and SOA pitfalls. A short presentation to focus your project on success - featuring the "magic progress fairy"
How Software Developers Destroy Business Value.pptxAaron Stannard
Software developers are intended to be massive, highly leverageable value creators for their companies and teams - using their creative and technical talent to build products themselves or mission-critical systems that facilitate the delivery of value inside the business. The blunt truth, however, is that many software developers would screw up tying their own shoes when left to their own devices. There's an abundant corpus of work out there on how managers routinely let down their software developers through insufficient planning, communication, listening, and support. In this talk we're going to explore the inverse - how individual software developers contributing to a project unintentionally sabotage their teams, their companies, their projects, and themselves through: * Immutable technical preferences + biases; * Bad attitudes; * Poor listening; * Inflexible and unproductive learning styles; * Risk aversion; * Incuriosity; * And more! Most importantly, in this talk we're going to try to address how we can help shift developers who want to learn and improve, but are have trouble executing, become the high value contributors they'd like to be.
Climbing out of a Crisis Loop at the BBCRafiq Gemmail
A talk I gave with my friend and mentor Katherine Kirk, on our journey to Scrumban and a leaner workflow at the BBC. See https://www.infoq.com/presentations/bbc-agile-case-study for the full presentation.
Overview and Basics of Project Managing IT Projects from real-world experience at Fortune 1000 companies. Key words include: Scrum, Agile, Waterfall, Requirements, PMI, PMP, PM, tech.
FPlive - Scaling Engineering: Pre and Post AcquisitionForward Partners
Sam Phillips from Shutl gave this talk on July 21st 2015 at FPlive, the startup community speaker event organised by Forward Partners. Sam talked about building Shutl's engineering team and becoming an eBay company.
Managing international software projects interactively using scrumPeter Horsten
Too many projects are not (fully) successful. In many cases this is caused by issues in the management approach. Clients want to know what they get for a fixed budget. But we all know it's almost impossible to fully specify what you need.
An Agile software approach proved to work for us. After implementing Scrum our projects went more smooth and we were more often delivering the right results on time.
It took time to get this working. For developers it was a bit scary and for our clients it meant they really had to trust us. Today we can see our effort pays off. We wouldn't like to go back to waterfall times anymore.
Marty talks about the hard parts of Product Management - People, Process, Product and Culture. For more detail about the talk, see our Meetup page here:
https://www.meetup.com/ProductTank-Auckland/events/248013722/
Want to sharpen your Product Management Skills and network with awesome people from the Auckland Product Management Community? Then join us at ProductTank Auckland:
https://www.meetup.com/ProductTank-Auckland/
IWMW 2004: It Always Takes Longer Than You Think (Even If You Think It Will T...IWMW
Slides used in workshop session B1 on "It Always Takes Longer Than You Think (Even If You Think It Will Take Longer Than You Think)" at the IWMW 2004 event held at the University of Birmingham on 27-29 July 2004.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2004/sessions/walker/
In this advanced business analysis training session, you will learn User Stories from Scenarios. Topics covered in this session are:
• What is a Use Case?
• The Purpose of Use Case Analysis
• Managing the Building of Product
• The Basic Development Loop
• Analysis paralysis – how much is enough
• Conceptual model development
• Style Guide development
• Usability testing during agile increments
For more information, click here: https://www.mindsmapped.com/courses/business-analysis/advanced-business-analyst-training/
Similar to Technical & Product Debt Management (20)
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 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
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
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.
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
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.
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.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
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.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
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/
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
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.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
3. “… A design or construction approach that is expedient in the short
term but that creates a technical context in which the same work will
cost more to do later than it would cost to do now (including
increased cost over time).”
3
Debt
4. Everything You Want to Do “Later” Is DEBT
• Let’s Document Later
• Let’s Test Later
• Let’s Architect Later
• Let’s Refactor Later
4
Debt
8. CEOs Tale
• We were very productive
• We kicked ass
• We became complacent
• I fired them all
• I hired a new team
• They are not productive either
• Must have chosen wrong
• I fired them all
• SAVE ME
8
Common Story
9. CTOs Tale
• We were very productive through debt accumulation
• We kicked ass but burned out
• We slowed down due to increasing debt support
• We got fired
• New team got hired
• It does not know where skeletons are buried
• We got fired as well
• I have Not Seen Organs Like These
9
Common Story
10. Support Cost is a Euphemism for Debt
Support
(15%)
Innovation
(85%)
Support
(50%)
Innovation
(50%)
Support
(85%)
Innovation
(15%)
Year 1
Year 2
Year 3
Support to Innovation Ratio
12. • Time to Market – If taking on debt gets you to market disproportionately
faster
• Time to Contact – If strategic contract is at stake debt might be worth it
• Time to Funding – If funding is at stake debt might be worth it
• Time to Survival – Debt is irrelevant if there is no tomorrow
Leveraging Debt
15. Technical Debt Elements
• Lack of Architectural Blueprint
• Lack of Unit Testing
• Lack of Integration Testing
• Lack of Code Reviews
• Lack of Starter Platform
• Lack of Starter Framework
• Lack of Technical Design
• Lack of Development Recipes
16. How Did We Let It Happen?
One Logical Step at a Time
22. Technical Debt Management
Technology Debt Management and Debt Avoidance
• Build on Top of IaaS/PaaS
• Build on Top of Starter Product/Starter Framework
• Implement Unit/Integration/Functional Testing
• Conduct Code Review
• Implement CI/CD/CD
• Establish Short Sprints (Agile) or No Sprints (Kanban)
• Non-Monolithic Design
24. Featuritis Curve
Number of Features
UserHappiness
Happy User Peak
“I rule!”
“Cool!”
“I’m so glad they added
this.”
“Nice, but I wish I
could do more…”
“Guess I better look
at the manual…”
“Hey, where the f***
did they put that?!”
“Now I can’t even do the ONE
SIMPLE THING I bought this
for…”
“I suck!”
30. Product Feature Attributes
Intelligent Design and Evolutionary Concepts
• Aim For Adjacent Possible
Irreducible Complexity
• Can’t Take Anything Away
• Can’t Be Simpler
Simplest for What It Does
• Simple Path to Intent
32. Feature Payments
Feature Currency
• Confusion “Payment” for Features
What Do They Mean?
• “This Is Confusing”
Ideal Feature
• Minimal Confusion
• Minimal Multiplicative Complexity
34. • Do Not Complicate Things
• Do Not Make Users Think
• Do Not Make Users Work
• Do Not Defy User’s Expectations
• Do Not Confuse Yourself With Users
• Do Not Assume You Know Everything
34
Product Debt Don’ts
37. Product Debt Management and Debt Avoidance
• 30% of the Sprint Should Be Devoted to Feature Removal
• Test Before You Implement
• Collect User Feedback
• Measure and Correlate Churn
• Assess Complexity and Confusion
37
Product Debt Management
40. Debt Mitigation Is Very Hard To Sell
• Cause and effect is not immediately apparent
• ROI is very difficult to quantify
• Definition of done is hard to come up with
• Perpetual projects are not crowd pleasers
• Users are not even aware that backend of apps even
exists. UX/UI in user’s mind is the app itself
40
Debt Mitigation Advice
41. If You Can Help It, Do Not Sell It
• Schedule feature holidays (every 5th release)
• Refactor as you go
• Make debt mitigation as part of the process
• Give estimates considering debt mitigation
• Invite outside experts
If You Must Sell It
• Tell CEO/CTO story
• Use aircraft maintenance strategy
41
Debt Mitigation Advice
Continued