Wastful waste or why everything is so slow in development

•

1 like•1,137 views

I think almost everybody experienced cases when things are moving very slowly in IT companies or teams. You have many people, talented engineers, Agile process and development speed is still below expectations. We try to focus on performance and efficiency last 10 years, improving our practices and tools. But we are still there in terms of speed when they are applied to real life cases. How is it possible? In this talk we will review the concept of waste circles and understand what are the main sources of time waste in development process. This concept would help you to check your processess, focus on right things and achieve much better results in your organization or team.

Technology

Wasteful waste or why
everything is so slow in
development
Mikalai Alimenkou
@xpinjection
http://xpinjection.com

Telegram channel
https://t.me/xpinjection_channel

Disclaimer
This talk is based on
personal experience

Customers always want…
New features ASAP!

It’s impossible to
understand if
performance
limit is reached

Waste Circles: another view on waste
Your performance
Technical waste
Team waste
Process waste
Organizational waste

Stories about organizational waste
Bad coffee
Global meetings and
corporate discussions
Lunch time
Bureaucracy

Typical meeting structure
Get out of work
context
Waiting Useful part
Discussions
and relax
Get into
work
context
15 minutes
30-40 minutes

• Planning (4 hours)
• Grooming (2 hours)
• Daily Scrum (20 minutes)
• Retrospective (1 hour)
• Demo and Sprint Review (2 hours)
Waste % = 12.3/80 ~ 15.5%
Process waste

Stories about team waste
Communication
CI/CD
Additional roles
Conflicts

Stories about technical waste
Technical debt
Code review
Bad tools
Defects

Let’s calculate your performance, bro!
Focus factor = 0.7 [ideal] * (1 –
OrgWaste) * (1 – ProcWaste) *
(1 – TeamWaste) * (1 – TechWaste)
For some large teams in ineffective
organizations actual FF ~ 0.1-0.2 for
ALL TEAM MEMBERS

Summary
• Focus on waste analysis instead of performance tuning
• Start from waste with maximal impact
• Don’t add waste continuously through your process
• Monitor waste level with right metrics
• Adopt focus factor based capacity planning
• Use product increment as the only performance metric

@xpinjection
http://xpinjection.com
mikalai.alimenkou@xpinjection.com

What's hot

Benefits of the process visualization in an organization How to synchronize teams and get all departments at the same page How to start: build a Process Map step-by-step at the Process Visualization workshop (phases, people, timing) Real industry examples: product development, manufacturing, software development I would like to share my experience of holding of the process visualization workshops in various organizations. The purpose of these workshops is to eliminate communication between teams and departments, understand who reports to whom and where dependencies between departments are.

Process visualisation - step-by-step - by Natalie Yadrentseva - Kanban Day 2015

French Kanban User Group

The 7 Deadly Sins Of Almost Being Agile

lazygolfer

Presentation on agile methodology

Ashish Jain, CSM, Prince2 Practitioner

Scrum Software Development Methodology

Suhail Jamaldeen

3. Armine - retrospective and grooming

Arevik Harutyunyan

OPERATION DEBRIEF: The Secret Weapon of High-Performing Ops Teams

Afterburner

Lean Development Overview

dhawalm123

Scrum bangalore 12 march 7 2015 - athresh krishnappa -distributed agile in ...

Scrum Bangalore

Day in the life of product manager

Carlos González de Villaumbrosia

Scrum bangalore 12 march 7 2015 - avinash rao - accelerating scaled agile u...

Scrum Bangalore

Richmond Spin - How To Sell A Traditional Client

OpenSource Connections

Scrum Bangalore 13th meet up 13 june 2015 - how not to run agile programs - a...

Scrum Bangalore

Scrum master's role - top 20 challenges

Viresh Doshi

Introduction To Scrum

vineet

Laurens Bonnema: The Agile Project Management Bootcamp Taster

Lviv Startup Club

Feature teams structure is a well known good-engineering-practice, especially for agile, busniess driven organizations. However, transferring an organization from component to feature teams is always a challange. Most organization actually keep their component driven structure and way of operation. This lecture is intended for those who have already been convinced about the benefits and value of feature teams, but are still hesitant to make the change. In this lecture we shall discuss optional migration paths and share practical considerations and tips to help make the transition effective and worth doing.

Transition to feature teams - Gil Wasserman - Agile Israel 2013

AgileSparks

Planning and Estimation

Madan Upadhyay

Scrum - An introduction

Hoang Nguyen

Agile philosophy

Zaheer Abbas

Agile Retrospective by Manohar Prasad

Manohar Prasad, PgMP®, PMP®, PMI-ACP®, CAL®, ACC®, CSP®

What's hot (20)

Process visualisation - step-by-step - by Natalie Yadrentseva - Kanban Day 2015

The 7 Deadly Sins Of Almost Being Agile

Presentation on agile methodology

Scrum Software Development Methodology

3. Armine - retrospective and grooming

OPERATION DEBRIEF: The Secret Weapon of High-Performing Ops Teams

Lean Development Overview

Scrum bangalore 12 march 7 2015 - athresh krishnappa -distributed agile in ...

Day in the life of product manager

Scrum bangalore 12 march 7 2015 - avinash rao - accelerating scaled agile u...

Richmond Spin - How To Sell A Traditional Client

Scrum Bangalore 13th meet up 13 june 2015 - how not to run agile programs - a...

Scrum master's role - top 20 challenges

Introduction To Scrum

Laurens Bonnema: The Agile Project Management Bootcamp Taster

Transition to feature teams - Gil Wasserman - Agile Israel 2013

Planning and Estimation

Scrum - An introduction

Agile philosophy

Agile Retrospective by Manohar Prasad

Similar to Wastful waste or why everything is so slow in development

Agile Pmi 102108 Final

bmcglin

The Toyota Way, also known as Lean, was born from hardship and survival. It is an approach that does not rely on the accidental fortunate circumstance of being in a positive business climate. The system that propelled Toyota to the top of the global automotive industry is designed to succeed in both good times and bad. Lean thinking fundamentally changes the engagement model between IT and the business, challenging traditional relationships with staff,customers and partners. This session, presented by a partnership between ThoughtWorks and KM&T, explains the Lean approach to challenges, continuous improvement, productivity, and quality, and how these principles can help you deliver high-value,high-quality software solutions to reduce operational costs, increase profitability, and survive. With presenters bringing deep expertise from Toyota, Lean and Agile principles, learn how to: -Identify and eliminate non-value adding work and cost (i.e., waste) -Build quality into processes to remove unnecessary rework -Apply Just-in-Time (JIT) principles to software delivery -Build processes that optimise use of resources and productivity for the entire end-to-end value stream -Engage everyone to continuously improve your team and practices -Understand the differences between repetitive processes, product development and software development Join us to discover how to do more with less. » » » » » » BRISBANE Tuesday 17 March, 2009 8am –- 9.30am Hilton 190 Elizabeth Street, Brisbane SYDNEY Tuesday 24 March, 2009 8am –- 9.30am Hilton 488 George Street, Sydney MELBOURNE Tuesday 31 March, 2009 8am –- 9.30am Marriott Cnr Exhibition & Lonsdale Streets, Melbourne PERTH Tuesday 7 April, 2009 8am –- 9.30am Hilton 14 Mill Street, Perth A light buffet breakfast will be provided * *

Lean Times Require Lean Thinking

Thoughtworks

Lean Times Require Lean Thinking

ThoughtWorks Studios

Lean Times Require Lean Thinking

Thoughtworks

Lean times require lean thinking

Catchi

value stream mapping workshop

Proyectalis / Improvement21

Slides 2015 for contact 7

YourhighnessJordaan

Project Management different concepts

Dvir Zohar

Agile for Business

DigitalCatapultDevelopmentPractices

People factor as failure reason of Agile adoption

Mikalai Alimenkou

People Factor As Failure Reason Of Agile Adoption

Agileee

Lean & kaizen

Jothilingam Durai

During 15 years of my software development career, I was a victim of numerous myths and fads of the IT industry. "We must have Scrum", "Rewrite everything", Hype-Driven Development, 100% test coverage - just to name a few. You'll learn where do these myths come from, why they're wrong and what are the real-world, battle-tested alternatives. You can skyrocket your career just by focusing on the right things!

Software development myths that block your career

Piotr Horzycki

Choosing the right agile approach for your organization

InCycle Software

Agile intro stldodn2009

Brian Blanchard

Solving Refining & Petrochemicals Workforce Development Challenges with Perfo...

GSE Systems, Inc.

Feb Apln OC Shawna C

Conscires Agile Practices

CAI - Agile Scrum Development Presentation

deyoepw

Lean Workshop.pptx

shivammishra544062

1603960041059_20 Six Sigma Good Tools.pptx

Mimmaafrin1

Similar to Wastful waste or why everything is so slow in development (20)

Agile Pmi 102108 Final

Lean Times Require Lean Thinking

Lean times require lean thinking

value stream mapping workshop

Slides 2015 for contact 7

Project Management different concepts

Agile for Business

People factor as failure reason of Agile adoption

People Factor As Failure Reason Of Agile Adoption

Lean & kaizen

Software development myths that block your career

Choosing the right agile approach for your organization

Agile intro stldodn2009

Solving Refining & Petrochemicals Workforce Development Challenges with Perfo...

Feb Apln OC Shawna C

CAI - Agile Scrum Development Presentation

Lean Workshop.pptx

1603960041059_20 Six Sigma Good Tools.pptx

More from Mikalai Alimenkou

Люди в мире Agile используют Story Points - для Agile коучей и тренеров это самый простой способ объяснить, как следует проводить оценку и планирование в «новом мире». Но тогда эта простая концепция нарушает реальные практические кейсы. В настоящее время команды состоят из очень специализированных людей, работающих над бэкендом, фронтэндом, тестировании, инфраструктуре и прочим. Для них почти невозможно иметь общий уровень сложности. Это только одна из проблем, которые мы собираемся осветить в этом докладе. Чтобы оставаться конструктивным, а не просто старомодным парнем из XP, Николай поделится своим опытом с более точной и прагматичной техникой оценки/планирования - планированием на основе возможностей.

Rise and fall of Story Points. Capacity based planning from the trenches.

Mikalai Alimenkou

We have spent many years testing our applications and systems manually and with test automation tools. During this time many bug root causes have been classified and could be detected automatically with special static analysis tools. Most of them could be applied at the early stages of development even before code is integrated into the main development branch. In this talk, I will go through available solutions and demonstrate what kinds of issues may be detected automatically reducing the time and effort of traditional testing.

Static analysis tools as the best friend of QA

Mikalai Alimenkou

In this talk, we will go through the design process of modern CI/CD for the microservices-based system with Kubernetes support. We will discuss how to verify consistency between microservices, apply different levels of quality gates and promote artifacts between environments. Thanks to Kubernetes we will review different approaches of environment resources optimization for development needs during CI/CD cycles.

Modern CI/CD in the microservices world with Kubernetes

Mikalai Alimenkou

Most of people nowadays think microservices architecture is a great way to build any system. They visit conference talks, read books and review tutorials, where ‘hello world’ applications are built just in several minutes using microservices approach. But the reality is not so wonderful and one of the biggest pain is hidden inside distributed business transactions. In monolith application this topic is almost completely covered with DB level transactions. In distributed world you have to face many issues trying to implement reliable and consistent business logic. In this talk we will review different types of problems related to distributed business transactions, popular SAGA pattern, frameworks and techniques to simplify your life without compromising quality of the system.

Saga about distributed business transactions in microservices world

Mikalai Alimenkou

Effectiveness tips from Kubernetes trenches by Captain Obvious

Mikalai Alimenkou

For a long time DB related testing in Java world has been a real pain and most developers tried to reduce number of such tests as much as possible. With good in-memory database implementations like H2, schema migration solutions like Liquibase or Flyway, containerization with libraries like TestContainers, database management is now much simpler. But test data management is still a pain. Some developers use SQL dumps, others insert data via JPA/JDBC or rely on prepared data sets. Good old DBUnit may be a good option, but it is not so developer friendly and not adopted well for modern annotations driven development style. Database Rider closes the gap between modern Java development environment and DBUnit, bringing DBUnit closer to your JUnit tests, so database testing will feel like a breeze. In addition to flexible data sets management this library provides other useful features: programmatic data sets definition, leak hunting, data sets export, constraints management, etc. As contributor and loyal user for many years, I would like to share my experience with Database Rider and demonstrate how to make database testing a fun again!

Ride the database in JUnit tests with Database Rider

Mikalai Alimenkou

Nowadays traditional layered monolithic architecture in Java world is not so popular as 5-10 years ago. I remember how we wrote tons of code for each layer repeating almost the same parts for every application. Add unit and integration testing to understand how much time and efforts has been spent on repeatable work. All cool ideas around DDD (domain driven design) and Hexagonal Architecture was just a nice theory because reality hasn’t allow us to implement it easily. Even Dependency Injection with Spring framework was completely focused on traditional layered approach, not even talking about JavaEE platform. Today we have Spring Boot ecosystem covering most of our needs for integration with almost all possible technologies and microservices architectural trend, enabling completely new approach to build Java applications around domain model. It is so natural to build Java domain-oriented services and connect them with external world using ports and adapters, that Hexagonal Architecture is almost enabled by default. You just need to switch your way of thinking…

Hexagonal architecture with Spring Boot

Mikalai Alimenkou

DevOps become a buzzword in a last few years. Several companies, development and product teams have achieved quite impressive results in this area making cultural changes, transforming their processes and practices, introducing new roles, tools and techniques. Do you think is achievable for you team or it’s still a bunch of drama? There is no common approach for measuring achievements and understanding how much DevOps’ich the current team/company is. In this talk I will provide attendees with basic checklist to start with and some reliable tools/techniques to monitor progress of “DevOps transformation”.

DevOps checklist or how to understand where is your team in DevOps landscape ...

Mikalai Alimenkou

DevOps is a hot topic during last several years. Some companies, teams and products have achieved quite impressive results in this area making cultural changes, transforming their processes and practices, introducing new roles, tools and techniques. At the same time there is no common approach for measuring achievements and understanding “how DevOps” the current team/company is. In this talk I will provide attendees with basic checklist to start with and some reliable tools/techniques to monitor progress of “DevOps transformation”.

DevOps checklist or how to understand where is your team in DevOps landscape

Mikalai Alimenkou

Почти год мы в Whirl Software разрабатываем систему Медкарта в масштабе целой страны. За это время мы столкнулись с множеством интересных сложностей и проблем, часть из которых успешно победили, а для некоторых хорошего решения до сих пор не найдено. В этом докладе мы поделимся накопленным практическим опытом и некоторыми техническими решениями, которые могут быть полезны в рамках разработки электронных медицинских систем.

Практические трудности в разработке Медкарты для целой страны

Mikalai Alimenkou

Hexagonal architecture with Spring Boot [EPAM Java online conference]

Mikalai Alimenkou

Almost any application or software system manages data. It is hard to imagine test automation that is not affected by this fact. There are many differenct approaches how to prepare system under test, providing predefined test data: use application UI, invoke API methods, run business logic directly, access DB from test scenarios, etc. In this talk we will review most of existing approaches, starting from the easiest and the most popular ones and finishing with really tricky ways to manage your test data for large distributed systems. There is no ideal solution for every case or silver bullet, but I hope your toolset will become wider after visiting this talk.

Bro, manage test data like a pro! [QA Fest 2018]

Mikalai Alimenkou

Вот уже более 10 лет Agile движение шагает по Украине и стучится практически в каждую компанию. Но приносят ли новые процессы, принципы и практики реальную практическую пользу? Получается ли изменить к лучшему команды, проекты, компании? Я в роли консультанта за эти 10 лет поработал с более чем 100 компаниями, поэтому повидал много хорошего и плохого. В данном докладе хочется пробежаться по основным проблемам, сложностям и анти-паттернам в переходе отечественных компаний на "Agile рельсы". Мы рассмотрим какие практики не очень хорошо приживаются, от чего страдает большинство команд, какие основные препятствия встречают на своем пути и как умудряются их обходить. Я надеюсь, доклад поможет зародиться множеству интересных дискуссий.

Agile antipatterns: review after 10 years of practice

Mikalai Alimenkou

Hexagonal architecture with Spring Boot

Mikalai Alimenkou

Bro, manage test data like a pro!

Mikalai Alimenkou

Тестировщики часто говорят о противостоянии и конфликтах с разработчиками. Но ведь есть команды, где все живут в мире и согласии. Видимо что-то тут не так? Я хочу поговорить о том, как тестировщиков видят сами разработчики. В докладе будет проведена забавная классификация. Кроме известного всем тестировщика-обезьянки будут представлены тестировщик-муха, тестировщик-нацист, тестировщик-панда и многие другие герои. Высможете лишний раз задуматься над тем, как вас видят со стороны и, возможно, изменить ситуацию к лучшему. Доклад будет также полезен менеджерам проектов и лидерам команд. Вы сможете быстрее распознавать те или иные шаблоны поведения тестировщикови принимать меры по повышению уровня командной работы. Приходите, будет интересно!

Бытовая классификация тестировщиков с точки зрения разработчика

Mikalai Alimenkou

Usually it is hard to analyze personal effectiveness and detect wastes in development process because developer’s work decomposition is not transparent and available for analysis. As a good sample of ineffective process imagine developer, who spends 1 day on task implementation and then reimplements it several times according to code review notes during next 2 days. Or another developer, who is waiting for code review during 2 days, switching context to other tasks, finally gets notes and switches back to initial task, trying to refresh all details in his head. And so on and so forth… Code review tool usage helps to aggregate lots of useful information about any code change at any stage (static analysis, code review, rework, acceptance, integration into main branch). In this talk I’m going to demontrate how this information could be used for detailed analysis of development effectiveness and wastes detection. Based on mentioned analysis you could implement many improvements for your development process and then measure their success.

Code Review tool for personal effectiveness and waste analysis

Mikalai Alimenkou

During last several years DevOps became strong buzzword used almost in every project, team and company. But almost everywhere it is used in very funny and strange context. For example, existing ops guys are renamed to DevOps just to sell them to the client for more money. Or DevOps is used as new job title for some magically powerful person who is able to operate cloud environment and modern infrastructure related tools, leading team of old school ops and participating in management meetings. In this talk I’m going to review all different anti-patterns and bad practices in DevOps landscape using stories from my personal experience as Delivery Manager and independent consultant.

Funny stories and anti-patterns from DevOps landscape

Mikalai Alimenkou

With Agile adoption many things have changed in quality assurance and tester role. Ourdays the whole team is responsible for product quality. But not so many people understand how such high level approaches work in practice, how developer interacts with tester, what stages each task passes on the way from requirements specification to customer acceptance, who is doing what at each stage. I have met only few teams, where developer and tester work closely together on a daily basis. Some projects try to same money on developer's time, others try to have independent testing team without influence from developers side. Developers also don't understad how tester could help them in practice. But this pair is able to significantly improve product quality and avoid many common issues. In this talk we will cover motivation behind pair work of develoeper and tester, concrete practices and approaches at different stages, and advantages that both sides could achieve from such work style.

Developer + tester = quality++

Mikalai Alimenkou

Nowadays IDE are much more intelligent than 10 years ago when they played mainly code editor functions. At the same time number of good practices and techniques is growing from day to day and most developers don’t have time to learn them with the same pace. So it could be a good idea to use IDE as continuous learning tool. In this talk we will cover following areas of developer efficiency: automated refactorings, live templates, useful suggestions, code standards, code navigation, code generation… I hope after this talk your daily job will become much more effective.

Continuous improvements of developer efficiency with modern IDE

Mikalai Alimenkou

More from Mikalai Alimenkou (20)

Rise and fall of Story Points. Capacity based planning from the trenches.

Static analysis tools as the best friend of QA

Modern CI/CD in the microservices world with Kubernetes

Saga about distributed business transactions in microservices world

Effectiveness tips from Kubernetes trenches by Captain Obvious

Ride the database in JUnit tests with Database Rider

Hexagonal architecture with Spring Boot

DevOps checklist or how to understand where is your team in DevOps landscape ...

DevOps checklist or how to understand where is your team in DevOps landscape

Практические трудности в разработке Медкарты для целой страны

Hexagonal architecture with Spring Boot [EPAM Java online conference]

Bro, manage test data like a pro! [QA Fest 2018]

Agile antipatterns: review after 10 years of practice

Hexagonal architecture with Spring Boot

Bro, manage test data like a pro!

Бытовая классификация тестировщиков с точки зрения разработчика

Code Review tool for personal effectiveness and waste analysis

Funny stories and anti-patterns from DevOps landscape

Developer + tester = quality++

Continuous improvements of developer efficiency with modern IDE

Recently uploaded

Automating Google Workspace (GWS) & more with Apps Script

wesley chun

Finology Group – Insurtech Innovation Award 2024

The Digital Insurer

Advantages of Hiring UIUX Design Service Providers for Your Business

Pixlogix Infotech

Tech Trends Report 2024 Future Today Institute.pdf

hans926745

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

Data Cloud, More than a CDP by Matt Robison

Anna Loughnan Colquhoun

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

Scaling API-first – The story of a global engineering organization Ian Reasor, Senior Computer Scientist - Adobe Radu Cotescu, Senior Computer Scientist - Adobe Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

apidays

Building Digital Trust in a Digital Economy Veronica Tan, Director - Cyber Security Agency of Singapore Apidays Singapore 2024: Connecting Customers, Business and Technology (April 17 & 18, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

apidays

[2024]Digital Global Overview Report 2024 Meltwater.pdf

hans926745

A Domino Admins Adventures (Engage 2024)

Gabriella Davis

Handwritten Text Recognition for manuscripts and early printed texts

Maria Levchenko

Imagine a world where information flows as swiftly as thought itself, making decision-making as fluid as the data driving it. Every moment is critical, and the right tools can significantly boost your organization’s performance. The power of real-time data automation through FME can turn this vision into reality. Aimed at professionals eager to leverage real-time data for enhanced decision-making and efficiency, this webinar will cover the essentials of real-time data and its significance. We’ll explore: FME’s role in real-time event processing, from data intake and analysis to transformation and reporting An overview of leveraging streams vs. automations FME’s impact across various industries highlighted by real-life case studies Live demonstrations on setting up FME workflows for real-time data Practical advice on getting started, best practices, and tips for effective implementation Join us to enhance your skills in real-time data automation with FME, and take your operational capabilities to the next level.

From Event to Action: Accelerate Your Decision Making with Real-Time Automation

Safe Software

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

Workshop - Best of Both Worlds_ Combine KG and Vector search for enhanced R...

Neo4j

Discord is a free app offering voice, video, and text chat functionalities, primarily catering to the gaming community. It serves as a hub for users to create and join servers tailored to their interests. Discord’s ecosystem comprises servers, each functioning as a distinct online community with its own channels dedicated to specific topics or activities. Users can engage in text-based discussions, voice calls, or video chats within these channels. Understanding Discord Servers Discord servers are virtual spaces where users congregate to interact, share content, and build communities. Servers may revolve around gaming, hobbies, interests, or fandoms, providing a platform for like-minded individuals to connect. Communication Features Discord offers a range of communication tools, including text channels for messaging, voice channels for real-time audio conversations, and video channels for face-to-face interactions. These features facilitate seamless communication and collaboration. What Does NSFW Mean? The acronym NSFW stands for “Not Safe For Work,” indicating content that may be inappropriate for professional or public settings. NSFW Content NSFW content encompasses material that is sexually explicit, violent, or otherwise graphic in nature. It often includes nudity, profanity, or depictions of sensitive topics.

Understanding Discord NSFW Servers A Guide for Responsible Users.pdf

UK Journal

What is a good lead in your organisation? Which leads are priority? What happens to leads? When sales and marketing give different answers to these questions, or perhaps aren't sure of the answers at all, frustrations build and opportunities are left on the table. Join us for an illuminating session with Cian McLoughlin, HubSpot Principal Customer Success Manager, as we look at that crucial piece of the customer journey in which leads are transferred from marketing to sales.

04-2024-HHUG-Sales-and-Marketing-Alignment.pptx

HampshireHUG

Created by Mozilla Research in 2012 and now part of Linux Foundation Europe, the Servo project is an experimental rendering engine written in Rust. It combines memory safety and concurrency to create an independent, modular, and embeddable rendering engine that adheres to web standards. Stewardship of Servo moved from Mozilla Research to the Linux Foundation in 2020, where its mission remains unchanged. After some slow years, in 2023 there has been renewed activity on the project, with a roadmap now focused on improving the engine’s CSS 2 conformance, exploring Android support, and making Servo a practical embeddable rendering engine. In this presentation, Rakhi Sharma reviews the status of the project, our recent developments in 2023, our collaboration with Tauri to make Servo an easy-to-use embeddable rendering engine, and our plans for the future to make Servo an alternative web rendering engine for the embedded devices industry. (c) Embedded Open Source Summit 2024 April 16-18, 2024 Seattle, Washington (US) https://events.linuxfoundation.org/embedded-open-source-summit/ https://ossna2024.sched.com/event/1aBNF/a-year-of-servo-reboot-where-are-we-now-rakhi-sharma-igalia

A Year of the Servo Reboot: Where Are We Now?

Igalia

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

Abhishek Deb(1), Mr Abdul Kalam(2) M. Des (UX) , School of Design, DIT University , Dehradun. This paper explores the future potential of AI-enabled smartphone processors, aiming to investigate the advancements, capabilities, and implications of integrating artificial intelligence (AI) into smartphone technology. The research study goals consist of evaluating the development of AI in mobile phone processors, analyzing the existing state as well as abilities of AI-enabled cpus determining future patterns as well as chances together with reviewing obstacles as well as factors to consider for more growth.

Exploring the Future Potential of AI-Enabled Smartphone Processors

debabhi2

Recently uploaded (20)

Automating Google Workspace (GWS) & more with Apps Script

Finology Group – Insurtech Innovation Award 2024

Advantages of Hiring UIUX Design Service Providers for Your Business

Tech Trends Report 2024 Future Today Institute.pdf

Strategies for Landing an Oracle DBA Job as a Fresher

Data Cloud, More than a CDP by Matt Robison

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

[2024]Digital Global Overview Report 2024 Meltwater.pdf

A Domino Admins Adventures (Engage 2024)

Handwritten Text Recognition for manuscripts and early printed texts

From Event to Action: Accelerate Your Decision Making with Real-Time Automation

AWS Community Day CPH - Three problems of Terraform

Workshop - Best of Both Worlds_ Combine KG and Vector search for enhanced R...

Understanding Discord NSFW Servers A Guide for Responsible Users.pdf

04-2024-HHUG-Sales-and-Marketing-Alignment.pptx

A Year of the Servo Reboot: Where Are We Now?

How to Troubleshoot Apps for the Modern Connected Worker

Exploring the Future Potential of AI-Enabled Smartphone Processors

Wastful waste or why everything is so slow in development

1. Wasteful waste or why everything is so slow in development Mikalai Alimenkou @xpinjection http://xpinjection.com

3. Telegram channel https://t.me/xpinjection_channel

4. Disclaimer This talk is based on personal experience

5. What is our performance?

6. Let’s tune our Agile process!

8. No good metrics for performance

9. Customers always want… New features ASAP!

10. It’s impossible to understand if performance limit is reached

11. Big team is not always effective

12. Top performance mode

13. Developers have different focus factor

14.

15. Waste Circles: another view on waste Your performance Technical waste Team waste Process waste Organizational waste

16. Stories about organizational waste Bad coffee Global meetings and corporate discussions Lunch time Bureaucracy

17. Typical meeting structure Get out of work context Waiting Useful part Discussions and relax Get into work context 15 minutes 30-40 minutes

18. • Planning (4 hours) • Grooming (2 hours) • Daily Scrum (20 minutes) • Retrospective (1 hour) • Demo and Sprint Review (2 hours) Waste % = 12.3/80 ~ 15.5% Process waste

19. Stories about team waste Communication CI/CD Additional roles Conflicts

20. Stories about technical waste Technical debt Code review Bad tools Defects

21. Let’s calculate your performance, bro! Focus factor = 0.7 [ideal] * (1 – OrgWaste) * (1 – ProcWaste) * (1 – TeamWaste) * (1 – TechWaste) For some large teams in ineffective organizations actual FF ~ 0.1-0.2 for ALL TEAM MEMBERS

22.

23. Summary • Focus on waste analysis instead of performance tuning • Start from waste with maximal impact • Don’t add waste continuously through your process • Monitor waste level with right metrics • Adopt focus factor based capacity planning • Use product increment as the only performance metric

24. @xpinjection http://xpinjection.com mikalai.alimenkou@xpinjection.com

Wastful waste or why everything is so slow in development

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Wastful waste or why everything is so slow in development

Similar to Wastful waste or why everything is so slow in development (20)

More from Mikalai Alimenkou

More from Mikalai Alimenkou (20)

Recently uploaded

Recently uploaded (20)

Wastful waste or why everything is so slow in development