Lean the principles
•
0 likes•593 views
Lean principles evolved from scientific management theories that viewed workers as lazy and lacking initiative. Deming introduced a humanistic approach in the 1940s, respecting workers and valuing continuous improvement. Lean principles focus on eliminating waste, respecting people, and continuous improvement through principles like seeing problems visually, limiting work-in-progress, and making processes policies explicit. Methods like Toyota Kata, kanban, and classes of service aim to improve flow and respect people.
Report
Share
Report
Share
Download to read offline
Recommended
Ive open day 11.12
The document discusses innovation and creative thinking. It defines innovation as the creation and implementation of new and better ideas, processes, or products. The document outlines different types of innovation and discusses how creativity and innovation are related but distinct concepts. It also provides tips for overcoming conceptual blocks and encourages exploring different choices, directions, and perspectives to achieve true innovation.
Lean vs design thinking
The document discusses design thinking and lean thinking approaches. Design thinking focuses on empathizing with users to identify problems, ideating solutions, prototyping, and testing. It is intuitive and aims to solve problems for humans. Lean thinking sees startups as experiments to build and test business models. It is more analytical and aims to create sustainable businesses that serve customers. Both approaches emphasize learning quickly from prototypes and users, but differ in their goals and focus.
Linchpin
This document summarizes key points from a book about becoming an indispensable employee or "linchpin". It discusses how average workers are easily replaced and underpaid, while linchpins bring unique value that is difficult to replace. It encourages readers to think differently and use their creativity to solve problems rather than just following instructions. It also addresses the mental resistance people have to standing out and challenges assumptions about jobs and career success.
AIMIA December 2012 Future of Digital
Eaon Pritchard shares thoughts on various topics related to behavioral science and digital marketing. He discusses how technology often enables new genres like house music. Pritchard also critiques assumptions in economics that humans are rational and isolated, noting we rely on heuristics and are influenced by others. He reflects on behavioral phenomena like anchoring bias and how even "big data" requires human interpretation that can introduce biases. Throughout, Pritchard advocates considering human behavior and psychology over technological determinism.
What does time travel have to do with being an inventor
Talks about how 3 ideas of relating to parallel adjacent problem areas, key questions to ask for inventing and how to dream boubdlessly to be an inventor.
Technology.
The document outlines the advantages and disadvantages of technology. Some of the key advantages mentioned are that technology makes work easier and faster, saves time, and improves communication by reducing distances. However, some of the disadvantages discussed are that people may become too reliant on technology and lazy, it can be costly, and there is potential for cheating or learning inaccurate information.
Inclusive tech, (how) is that possible?
This document discusses inclusive technology and how to make technology benefit everyone. It begins by asking if inclusive tech is possible and defines inclusive tech as technology that benefits all people. It then provides examples of where technology has not been inclusive, such as voice recognition software being more likely to recognize male voices. The document discusses how biological factors and binary thinking can lead to bias in technology. It advocates considering diversity in data collection and design, being transparent about algorithms, and involving diverse groups in the design process. The overall message is that while technology can help humanity, we must ensure it is developed and applied in a sustainable and inclusive way.
Apache flink
Diego Pacheco is the principal software architect at Apache Flink, an open-source streaming dataflow engine for distributed computations over data streams. Flink supports both batch and stream processing with high throughput and low latency using Scala, Java, and Python. It provides capabilities for data distribution, communication, fault tolerance, and machine learning and graph processing using Gelly.
Recommended
Ive open day 11.12
The document discusses innovation and creative thinking. It defines innovation as the creation and implementation of new and better ideas, processes, or products. The document outlines different types of innovation and discusses how creativity and innovation are related but distinct concepts. It also provides tips for overcoming conceptual blocks and encourages exploring different choices, directions, and perspectives to achieve true innovation.
Lean vs design thinking
The document discusses design thinking and lean thinking approaches. Design thinking focuses on empathizing with users to identify problems, ideating solutions, prototyping, and testing. It is intuitive and aims to solve problems for humans. Lean thinking sees startups as experiments to build and test business models. It is more analytical and aims to create sustainable businesses that serve customers. Both approaches emphasize learning quickly from prototypes and users, but differ in their goals and focus.
Linchpin
This document summarizes key points from a book about becoming an indispensable employee or "linchpin". It discusses how average workers are easily replaced and underpaid, while linchpins bring unique value that is difficult to replace. It encourages readers to think differently and use their creativity to solve problems rather than just following instructions. It also addresses the mental resistance people have to standing out and challenges assumptions about jobs and career success.
AIMIA December 2012 Future of Digital
Eaon Pritchard shares thoughts on various topics related to behavioral science and digital marketing. He discusses how technology often enables new genres like house music. Pritchard also critiques assumptions in economics that humans are rational and isolated, noting we rely on heuristics and are influenced by others. He reflects on behavioral phenomena like anchoring bias and how even "big data" requires human interpretation that can introduce biases. Throughout, Pritchard advocates considering human behavior and psychology over technological determinism.
What does time travel have to do with being an inventor
Talks about how 3 ideas of relating to parallel adjacent problem areas, key questions to ask for inventing and how to dream boubdlessly to be an inventor.
Technology.
The document outlines the advantages and disadvantages of technology. Some of the key advantages mentioned are that technology makes work easier and faster, saves time, and improves communication by reducing distances. However, some of the disadvantages discussed are that people may become too reliant on technology and lazy, it can be costly, and there is potential for cheating or learning inaccurate information.
Inclusive tech, (how) is that possible?
This document discusses inclusive technology and how to make technology benefit everyone. It begins by asking if inclusive tech is possible and defines inclusive tech as technology that benefits all people. It then provides examples of where technology has not been inclusive, such as voice recognition software being more likely to recognize male voices. The document discusses how biological factors and binary thinking can lead to bias in technology. It advocates considering diversity in data collection and design, being transparent about algorithms, and involving diverse groups in the design process. The overall message is that while technology can help humanity, we must ensure it is developed and applied in a sustainable and inclusive way.
Apache flink
Diego Pacheco is the principal software architect at Apache Flink, an open-source streaming dataflow engine for distributed computations over data streams. Flink supports both batch and stream processing with high throughput and low latency using Scala, Java, and Python. It provides capabilities for data distribution, communication, fault tolerance, and machine learning and graph processing using Gelly.
ML and R
Machine learning (ML) is a type of artificial intelligence based on computational learning theory and algorithms that allow systems to learn from data and make predictions without being explicitly programmed. ML uses features to quantitatively describe items in samples of data like images or files to create feature vectors, and it relies on training sets of data to discover predictive relationships and evolve models. Popular tools for ML include R and Python's Scikit-Learn.
Agile tem que morrer? Já morreu? Hacker way? BS ou mais do mesmo?
The document discusses whether Agile needs to die or has already died. It covers the evolution of software development approaches from Waterfall to newer methods like Scrum, XP, Kanban, and DevOps. It argues that principles are more important than practices and that Agile needs to adapt to new economic and technological realities like mobile, startups, and complexity of modern software.
Apache mesos
Apache Mesos abstracts compute resources like CPU, memory, and storage from physical or virtual machines, enabling distributed systems to easily build and run applications in a fault-tolerant and elastic way. It provides scalability to 10,000s of nodes, fault tolerance through replicated masters and slaves using ZooKeeper, support for Docker containers, isolation between tasks using Linux containers, and scheduling of multiple resources like memory, CPU, disk and ports. It also includes Java, Python and C++ APIs and a web UI to view cluster state.
Spring Capitulo 05
The document discusses various Spring framework features including sending emails, scheduling tasks, intercepting methods with AOP, testing contexts with JUnit, and exposing services via RMI. It provides code examples of configuring and using these features, such as sending emails with attachments, scheduling a task to run periodically, and adding logging aspects using AOP.
Agile culture & Mindsets
The document discusses agile culture and mindsets in software development. It emphasizes the importance of changing myths and taboos through adopting new metaphors like seeing software development as a music studio, painting atelier, or craft. It stresses inspecting and adapting frequently through small teams, retrospectives, test-driven development, simple design, and pair programming to build quality software and promote learning. The presentation aims to promote agile values and practices for developing effective culture.
EXTRA: Workshop SOA, Microservices e Devops - Discoverability + Ui Arch
This document discusses a workshop on SOA, microservices, and DevOps. It mentions various service discovery tools like Consul, Eureka, and Synapse. It also discusses UI architecture patterns such as MVC and Angular, as well as approaches to on-demand UI content and links between components. The document concludes by thanking participants.
Avout
This document discusses current concurrency models including actors, STM, and distributed locks. It provides examples of using the Avout library in Clojure to demonstrate an actor-based concurrency model. The Avout library supports lightweight threads, asynchronous message passing between actors without shared data, and ACID transactions for STM. It also supports atoms, refs, swap, alter and commute for shared mutable state. Distributed locks are also mentioned. The document provides instructions for setting up a new Clojure project with the Avout dependency and running a sample program that increments a counter with multiple actor calls.
Docker
Docker provides a technology suite that enables development and operations teams to build, ship, and run distributed applications using containers. It includes features like Dockerfiles to build container images, a registry to store images, Compose files to define multi-container apps, and clustering tools to scale deployments across infrastructure. The document discusses Docker concepts, internals, testing, clustering, and how it integrates with container platforms from AWS and Google Cloud.
Contracts and models
The document discusses and compares four different software development contract models: fixed price/scope, pack of hours, time and materials, and risk & reward. Fixed price/scope contracts provide visibility into costs but can sacrifice quality by limiting testing and changes. Pack of hours contracts provide more flexibility than fixed price but can lead to scope creep. Time and materials contracts offer the most flexibility but provide no guarantees around delivery. Risk & reward contracts incentivize vendors through bonuses for successful delivery while sharing risks between the vendor and customer.
Knox
Knox is an Apache project that provides a single point of secure access for multiple Hadoop clusters and services. It uses standard security protocols to enable secure access to HDFS from web and mobile applications without requiring authentication on each service individually. Knox supports common Hadoop services like HDFS, YARN, Hive, and HBase and allows them to be accessed securely via a single URL.
Vert.x
Vert.x is an event-driven framework that uses an event loop and asynchronous APIs to handle HTTP requests, websockets, and other protocols. It uses single-threaded "verticles" that communicate through a centralized event bus to avoid race conditions. The event bus supports point-to-point, publish-subscribe, and request-response messaging patterns and integrates with modules for databases, messaging, and other services. Applications are packaged and deployed as self-contained JAR files.
Spring Capitulo 01
O documento apresenta uma introdução ao framework Spring, destacando conceitos como Injeção de Dependência e modularidade. Também lista alguns módulos do Spring como Spring Web Flow e Spring Web Services, e indica o site oficial para download da última versão do framework.
Twitter Bootstrap
Bootstrap is a front-end framework created by Twitter that provides responsive CSS and HTML for developing responsive and mobile-first projects. It contains various pre-built components like buttons, navigation, dropdowns, modals, and more that can help build the structure and interface of a website or web application quickly using HTML, CSS and JavaScript. The framework is open source and free to use.
Apache Kafka
Apache Kafka is a high-throughput distributed messaging system that allows for both streaming and offline log processing. It uses Apache Zookeeper for coordination and supports activity stream processing and real-time pub/sub messaging. Kafka bridges the gaps between pure offline log processing and traditional messaging systems by providing features like batching, transactions, persistence, and support for multiple consumers.
Cassandra
This document provides an overview of Apache Cassandra, an open source, distributed, wide column store NoSQL database. It discusses key features like scalability, high availability, fault tolerance, and replication across datacenters. Cassandra can handle 1 million writes per second and has been battle tested by many large companies. The document also covers topics like consistency models, data partitioning, replication strategies, indexing, storage, and the Java driver.
Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The G...
The document discusses new approaches for building software systems, including microservices, cloud native architectures, and Site Reliability Engineering (SRE) and chaos engineering. It notes that microservices, cloud platforms, and DevOps have established new best practices for software development. Namely, it emphasizes designing systems for failure and testing systems using chaos engineering approaches to improve reliability.
Cloud-Native DevOps Engineering
The document discusses cloud native devops engineering. It introduces Diego Pacheco and his background. It then discusses key concepts for cloud native solutions like being designed and built for the cloud, horizontal scaling, elasticity, failure handling, anti-fragility, and automation. It also discusses public and private clouds, containers, costs versus lock-in, and specialized versus general services. The document advocates for automation beyond deployment, including data store operations, stress testing, chaos testing, telemetry, and canary testing. It provides examples of automation tools for data stores, telemetry, and canary testing. It also discusses challenges like infrastructure baking, testing distributed systems, and balancing stability versus speed of delivery.
Microservices reativos usando a stack do Netflix na AWS
This document discusses using Netflix's microservices stack on AWS. It describes Netflix's architecture of using hundreds of microservices across multiple regions to handle billions of requests per day. It outlines the principles of Netflix's stack including stateless services, auto-scaling, no single points of failure, and designing for failures. Key technologies in Netflix's open source stack are explained like Eureka for service discovery, Ribbon for load balancing, Hystrix for latency and fault tolerance, RxJava for reactive programming, and Dynomite for distributed caching. Chaos engineering practices like fault injection testing are also covered.
A volta dos que não foram (recap de lean, agile, xp, kanban)
This document discusses different approaches to software development processes including agile, lean, and scientific management. It advocates focusing on learning and empowering people rather than optimizing parts in isolation. Quotes are provided from Thomas Jefferson and W. Edwards Deming about respecting people and trusting their intrinsic motivation rather than strict control. Kanban is mentioned as being 80% about people. The document encourages professionals to do their part with pride and not rely on tools alone but continuously improve processes through experience. It acknowledges there is still more to learn beyond what current methods cover.
Coaching & desenvolvimento de times
The document provides guidance and tools for coaching and developing teams, outlining frameworks for agile coaching, techniques for facilitating retrospectives and improvements, and strategies for helping individuals and teams overcome challenges through focused development. Key elements discussed include visualization tools, limiting work-in-progress, managing flow, and improving collaboratively using the scientific method.
Managing your tech career
This document summarizes a talk on managing your tech career and tracking your tech skills. The talk covered finding your path in the industry, building your personal brand, evolving your mindset, and tracking emerging technologies. It discussed understanding the different roles and paths available, developing your career narrative, maintaining an online presence, participating in communities, and dealing with imposter syndrome. The talk emphasized the importance of continuous learning, building a technology radar to track new tools and platforms, and appreciating how your skills fit within the broader tech ecosystem.
Management Control System at Toyota
The presentation is about Management Control System at Toyota. The presentation briefly covers the various techniques developed by Toyota with reference to the "Toyota House Diagram".
More Related Content
Viewers also liked
ML and R
Machine learning (ML) is a type of artificial intelligence based on computational learning theory and algorithms that allow systems to learn from data and make predictions without being explicitly programmed. ML uses features to quantitatively describe items in samples of data like images or files to create feature vectors, and it relies on training sets of data to discover predictive relationships and evolve models. Popular tools for ML include R and Python's Scikit-Learn.
Agile tem que morrer? Já morreu? Hacker way? BS ou mais do mesmo?
The document discusses whether Agile needs to die or has already died. It covers the evolution of software development approaches from Waterfall to newer methods like Scrum, XP, Kanban, and DevOps. It argues that principles are more important than practices and that Agile needs to adapt to new economic and technological realities like mobile, startups, and complexity of modern software.
Apache mesos
Apache Mesos abstracts compute resources like CPU, memory, and storage from physical or virtual machines, enabling distributed systems to easily build and run applications in a fault-tolerant and elastic way. It provides scalability to 10,000s of nodes, fault tolerance through replicated masters and slaves using ZooKeeper, support for Docker containers, isolation between tasks using Linux containers, and scheduling of multiple resources like memory, CPU, disk and ports. It also includes Java, Python and C++ APIs and a web UI to view cluster state.
Spring Capitulo 05
The document discusses various Spring framework features including sending emails, scheduling tasks, intercepting methods with AOP, testing contexts with JUnit, and exposing services via RMI. It provides code examples of configuring and using these features, such as sending emails with attachments, scheduling a task to run periodically, and adding logging aspects using AOP.
Agile culture & Mindsets
The document discusses agile culture and mindsets in software development. It emphasizes the importance of changing myths and taboos through adopting new metaphors like seeing software development as a music studio, painting atelier, or craft. It stresses inspecting and adapting frequently through small teams, retrospectives, test-driven development, simple design, and pair programming to build quality software and promote learning. The presentation aims to promote agile values and practices for developing effective culture.
EXTRA: Workshop SOA, Microservices e Devops - Discoverability + Ui Arch
This document discusses a workshop on SOA, microservices, and DevOps. It mentions various service discovery tools like Consul, Eureka, and Synapse. It also discusses UI architecture patterns such as MVC and Angular, as well as approaches to on-demand UI content and links between components. The document concludes by thanking participants.
Avout
This document discusses current concurrency models including actors, STM, and distributed locks. It provides examples of using the Avout library in Clojure to demonstrate an actor-based concurrency model. The Avout library supports lightweight threads, asynchronous message passing between actors without shared data, and ACID transactions for STM. It also supports atoms, refs, swap, alter and commute for shared mutable state. Distributed locks are also mentioned. The document provides instructions for setting up a new Clojure project with the Avout dependency and running a sample program that increments a counter with multiple actor calls.
Docker
Docker provides a technology suite that enables development and operations teams to build, ship, and run distributed applications using containers. It includes features like Dockerfiles to build container images, a registry to store images, Compose files to define multi-container apps, and clustering tools to scale deployments across infrastructure. The document discusses Docker concepts, internals, testing, clustering, and how it integrates with container platforms from AWS and Google Cloud.
Contracts and models
The document discusses and compares four different software development contract models: fixed price/scope, pack of hours, time and materials, and risk & reward. Fixed price/scope contracts provide visibility into costs but can sacrifice quality by limiting testing and changes. Pack of hours contracts provide more flexibility than fixed price but can lead to scope creep. Time and materials contracts offer the most flexibility but provide no guarantees around delivery. Risk & reward contracts incentivize vendors through bonuses for successful delivery while sharing risks between the vendor and customer.
Knox
Knox is an Apache project that provides a single point of secure access for multiple Hadoop clusters and services. It uses standard security protocols to enable secure access to HDFS from web and mobile applications without requiring authentication on each service individually. Knox supports common Hadoop services like HDFS, YARN, Hive, and HBase and allows them to be accessed securely via a single URL.
Vert.x
Vert.x is an event-driven framework that uses an event loop and asynchronous APIs to handle HTTP requests, websockets, and other protocols. It uses single-threaded "verticles" that communicate through a centralized event bus to avoid race conditions. The event bus supports point-to-point, publish-subscribe, and request-response messaging patterns and integrates with modules for databases, messaging, and other services. Applications are packaged and deployed as self-contained JAR files.
Spring Capitulo 01
O documento apresenta uma introdução ao framework Spring, destacando conceitos como Injeção de Dependência e modularidade. Também lista alguns módulos do Spring como Spring Web Flow e Spring Web Services, e indica o site oficial para download da última versão do framework.
Twitter Bootstrap
Bootstrap is a front-end framework created by Twitter that provides responsive CSS and HTML for developing responsive and mobile-first projects. It contains various pre-built components like buttons, navigation, dropdowns, modals, and more that can help build the structure and interface of a website or web application quickly using HTML, CSS and JavaScript. The framework is open source and free to use.
Apache Kafka
Apache Kafka is a high-throughput distributed messaging system that allows for both streaming and offline log processing. It uses Apache Zookeeper for coordination and supports activity stream processing and real-time pub/sub messaging. Kafka bridges the gaps between pure offline log processing and traditional messaging systems by providing features like batching, transactions, persistence, and support for multiple consumers.
Cassandra
This document provides an overview of Apache Cassandra, an open source, distributed, wide column store NoSQL database. It discusses key features like scalability, high availability, fault tolerance, and replication across datacenters. Cassandra can handle 1 million writes per second and has been battle tested by many large companies. The document also covers topics like consistency models, data partitioning, replication strategies, indexing, storage, and the Java driver.
Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The G...
The document discusses new approaches for building software systems, including microservices, cloud native architectures, and Site Reliability Engineering (SRE) and chaos engineering. It notes that microservices, cloud platforms, and DevOps have established new best practices for software development. Namely, it emphasizes designing systems for failure and testing systems using chaos engineering approaches to improve reliability.
Cloud-Native DevOps Engineering
The document discusses cloud native devops engineering. It introduces Diego Pacheco and his background. It then discusses key concepts for cloud native solutions like being designed and built for the cloud, horizontal scaling, elasticity, failure handling, anti-fragility, and automation. It also discusses public and private clouds, containers, costs versus lock-in, and specialized versus general services. The document advocates for automation beyond deployment, including data store operations, stress testing, chaos testing, telemetry, and canary testing. It provides examples of automation tools for data stores, telemetry, and canary testing. It also discusses challenges like infrastructure baking, testing distributed systems, and balancing stability versus speed of delivery.
Microservices reativos usando a stack do Netflix na AWS
This document discusses using Netflix's microservices stack on AWS. It describes Netflix's architecture of using hundreds of microservices across multiple regions to handle billions of requests per day. It outlines the principles of Netflix's stack including stateless services, auto-scaling, no single points of failure, and designing for failures. Key technologies in Netflix's open source stack are explained like Eureka for service discovery, Ribbon for load balancing, Hystrix for latency and fault tolerance, RxJava for reactive programming, and Dynomite for distributed caching. Chaos engineering practices like fault injection testing are also covered.
Viewers also liked (18)
Agile tem que morrer? Já morreu? Hacker way? BS ou mais do mesmo?
Agile tem que morrer? Já morreu? Hacker way? BS ou mais do mesmo?
EXTRA: Workshop SOA, Microservices e Devops - Discoverability + Ui Arch
EXTRA: Workshop SOA, Microservices e Devops - Discoverability + Ui Arch
Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The G...
Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The G...
Microservices reativos usando a stack do Netflix na AWS
Microservices reativos usando a stack do Netflix na AWS
Similar to Lean the principles
A volta dos que não foram (recap de lean, agile, xp, kanban)
This document discusses different approaches to software development processes including agile, lean, and scientific management. It advocates focusing on learning and empowering people rather than optimizing parts in isolation. Quotes are provided from Thomas Jefferson and W. Edwards Deming about respecting people and trusting their intrinsic motivation rather than strict control. Kanban is mentioned as being 80% about people. The document encourages professionals to do their part with pride and not rely on tools alone but continuously improve processes through experience. It acknowledges there is still more to learn beyond what current methods cover.
Coaching & desenvolvimento de times
The document provides guidance and tools for coaching and developing teams, outlining frameworks for agile coaching, techniques for facilitating retrospectives and improvements, and strategies for helping individuals and teams overcome challenges through focused development. Key elements discussed include visualization tools, limiting work-in-progress, managing flow, and improving collaboratively using the scientific method.
Managing your tech career
This document summarizes a talk on managing your tech career and tracking your tech skills. The talk covered finding your path in the industry, building your personal brand, evolving your mindset, and tracking emerging technologies. It discussed understanding the different roles and paths available, developing your career narrative, maintaining an online presence, participating in communities, and dealing with imposter syndrome. The talk emphasized the importance of continuous learning, building a technology radar to track new tools and platforms, and appreciating how your skills fit within the broader tech ecosystem.
Management Control System at Toyota
The presentation is about Management Control System at Toyota. The presentation briefly covers the various techniques developed by Toyota with reference to the "Toyota House Diagram".
SharePoint Worst Practices: 5 Common Mistakes to Avoid #WMSPUG
This document discusses five common mistakes to avoid when implementing SharePoint: 1) Lack of proper planning, 2) Showcasing features instead of building solutions, 3) Having an undefined business case without measurable goals and ROI, 4) Having a poor understanding of SharePoint's capabilities and best practices, and 5) Unrealistic staffing with too few resources. The presentation provides examples and recommendations for how to successfully implement SharePoint through defining requirements, building appropriate solutions, quantifying expected benefits, gaining expertise, and assembling a dedicated project team.
Leadership 2020 -
Leadership 2020 - Exclusive Managment Training Presentation by Dr. Shailesh Thaker - Management Guru, Business Thinker, Motivator, Keynote Speaker and Corporate Trainer in India
Stop talking about innovation!
Stop Talking About Innovation!
We need to limit the use of the word and the term “innovation” and we need to ban the term “innovation culture” entirely.
This is the radical outset for a keynote or a session in which Stefan Lindegaard challenges common beliefs on innovation, explain why most companies fail with their efforts to become more “innovative” and share insights on how to build the capabilities that can help companies and organizations survive and prosper in these times of fast change and strong disruption.
The key messages:
- Focus on corporate transformation and digitalization – or die!
- Link your efforts to the challenges of your stakeholders and increase your ROI
- Work with the unusual suspects; internally as well as externally
- Focus on people, people and people – and upgrade their mindset and skills
- Learn to communicate better and differently – or fail!
About Stefan Lindegaard:
Stefan Lindegaard is an author, speaker and strategic advisor. His focus on corporate transformation, digitalization and innovation has propelled him into being a trusted source of inspiration to many large corporations. He believes business and innovation requires an open and global perspective and he has given talks and worked with companies in Europe, North America, South America, Africa and Asia.
Stefan Lindegaard has written several books including 7 Steps for Open Innovation, Making Open Innovation Work and The Open Innovation Revolution. His blog is a globally recognized destination with many free resources (books, white papers, exercises). You can read further at 15inno.com.
Linchpin
This document summarizes key points from a book about becoming an indispensable employee or "linchpin". It discusses how average workers are easily replaced and underpaid, while linchpins bring unique value that is difficult to replace. It encourages readers to think differently and use their creativity to solve problems rather than just following instructions. It also addresses the mental resistance people have to standing out and challenges assumptions about jobs and career success.
Be a Team Leader, not a Manager!
What's the difference between a team leader and a manager? How to become the leader and digging the best of your people's skills and talent?
Corporate politics and higher education presentation at HPAIR conference
This document discusses corporate politics and provides advice for navigating them. It begins by outlining the types of organizations that make up the corporate world, including large corporations, governments, and NGOs, which all have different agendas. Examples are then given of both positive and negative workplace cultures and politics at several large companies. The document warns that even seemingly great companies can be politically challenging. It provides examples of situations where employees were forced to leave jobs due to unfair treatment or politics. Finally, it suggests options for avoiding toxic corporate politics, such as starting one's own business, carefully researching potential employers, or becoming a consultant. The overall message is that politics are inevitable in large organizations but there are ways to minimize their impact or
Aprendendo de verdade com kanban
This document discusses Kanban, an agile project management method. It provides an overview of Kanban concepts and practices, including:
- Kanban focuses on continuous improvement and empowering workers rather than optimizing individual parts.
- Kanban aims to remove waste from processes through techniques like limiting work in progress and visualizing workflow.
- Examples of Kanban tools and techniques are described, such as using physical or digital Kanban boards to manage work flow and limit work in progress.
- The importance of learning from data and metrics to guide improvements is emphasized.
THE SIX TRAITS OF IT-DRIVEN BUSINESS INNOVATORS- Does Your Organization Share...
Leading IT executives react to a Harvard Business Review survey outlining the six behaviors of companies with innovative IT. Does your organization share any of these characteristics?
John Landry - June 2010
This document summarizes John Landry's 15 years of experience as an angel investor, highlighting lessons learned about evaluating investment opportunities and ensuring team success. Some key criteria for investment include evaluating whether an idea is addressing a major technological shift, if the product or service fills a scarce niche, and if the founding team has complementary skills. Landry also reflects on factors like the importance of the founding team starting together, maintaining momentum over 1-4 years, and selling investments within 3 years for best returns, rather than holding investments longer without sufficient growth. The document aims to share best practices for angel investors to identify promising startups and increase chances of successful exits.
SSA Resume Workshop 2017 Centriq
The document provides guidance on creating a technical resume, including sections that should be included and how to write meaningful content. It emphasizes highlighting skills, accomplishments and results through power words and quantification. Visual design elements like formatting, spacing and font styles are also covered to improve readability and appeal. References should be provided on a separate document upon request.
Lean transformation for Technology (IT) Vietnam
- Edward Deming taught Japanese business leaders about quality management in the 1950s, emphasizing that quality must be a top priority led by senior management.
- Following Deming's teachings, Japanese companies flourished internationally by focusing on high quality, outcompeting American firms that prioritized quantity over quality.
- Deming's 14 Points for management transformation centered on continuous improvement, cooperation across departments, and making quality everyone's responsibility. These principles can guide IT organizations to build quality into systems from the start.
02 18-1-ohnos method
Taiichi Ohno developed the Toyota Production System (TPS) and a new work culture at Toyota during 1945-1965 as the company fought for survival. Ohno's leadership focused on developing people through mentoring and empowering workers to continuously improve processes through kaizen. This established a culture where workers wrote their own standard work procedures and engaged in regular process improvement. Ohno's approach focused on developing a culture where workers closely observed processes, identified problems, and shared best practices. This grassroots problem-solving approach was core to TPS and enabled Toyota's flexibility and ability to produce different models using the same production lines.
Lean & kanban alem da agilidade
Lean and Kanban concepts were discussed over the course of a full-day workshop. The presentation covered Lean principles and origins, as well as how Kanban approaches workflow. Key aspects of Kanban discussed included visualizing workflow, limiting work in progress, and making policies explicit. The workshop included demonstrations of Lean and Kanban in practice as well as a group discussion session.
Team up
Lately, it seems that process became trendier than core leadership skills. Agile, Scrum, Kanban stole the focus.
BUT - it is leadership that fuels process adoption rather than process auto-magically fixing disfunction teams.
In this talk we'll explore what went wrong in this process adoption race: from hiring or promoting the wrong people, avoid setting clear expectations from our leaders, to dropping lean practices due to lack of deep understanding (forgetting why we started to begin with).
The dark side is interesting to explore, but we are here for the bright light - we will bring the FOCUS back to how we want our leadership to look like.
We'll try to figure out how we want our leaders to look like in the "Agile era"
Agenda:
== THE WHY ==
- The essence
- Goals balance
- Surviving in chaos
- Team leader definition
- Business vision
- Throughput .vs. latency
- Confidence is not cheap
- Risks management
- Beautiful code
- Beautiful document
== THE HOW ==
- Visibility over progress
- Must, Delegate and External
- Ownership as a driver
- Define “minimum working unit” early
- Define “done” that works for you
- Quality is God (or at least Jesus)
- Test to last
- Bullets knowledge base
- Estimate together
- Teach to move forward
SoT 2015 Career/Resume
John Clegg's introduction to writing a CV/Resume that IT employers want to read.
(these slides cover CV Part 1 and CV Part 2 bootcamps from the SoT2015 programme)
Scaling tech teams
As a startup CTO's company grows, their job changes from technical contributions to managing growing teams. They must adapt their role to focus on team building, collaboration, and scaling the engineering department. Some key steps include hiring experienced managers, conducting lightweight onboarding and values exercises, ensuring self-sufficient delivery teams, and maintaining cultural cohesion through communication between departments. Failing to adapt risks becoming a bottleneck, isolating engineering, and missing business value drivers.
Similar to Lean the principles (20)
A volta dos que não foram (recap de lean, agile, xp, kanban)
A volta dos que não foram (recap de lean, agile, xp, kanban)
SharePoint Worst Practices: 5 Common Mistakes to Avoid #WMSPUG
SharePoint Worst Practices: 5 Common Mistakes to Avoid #WMSPUG
Corporate politics and higher education presentation at HPAIR conference
Corporate politics and higher education presentation at HPAIR conference
THE SIX TRAITS OF IT-DRIVEN BUSINESS INNOVATORS- Does Your Organization Share...
THE SIX TRAITS OF IT-DRIVEN BUSINESS INNOVATORS- Does Your Organization Share...
More from Diego Pacheco
Naming Things Book : Simple Book Review!
The document discusses principles for naming identifiers in code such as variables, classes, and functions. It notes that naming is important because identifiers make up 70% of code and influence comprehension, recall, and bug fixing time. Good naming follows principles like understandability, using names that describe concepts, and consistency. It provides specific rules for naming classes, variables, functions for conciseness, consistency, and distinguishability. The goal is to use names that are understandable to both current and future engineers working on the code.
Continuous Discovery Habits Book Review.pdf
This document summarizes key points from the book "Continuous Discovery Habits" by Diego Pacheco. It advocates for continuous discovery through an outcome-oriented and customer-centric mindset. Discovery requires the collaboration of product managers, designers, and engineers to iteratively test assumptions and validate ideas with customers. The goal is to ensure teams are creating value for users and addressing their needs, pain points, and desires on an ongoing basis through experimental and visual approaches.
Thoughts about Shape Up
This document discusses the Shape Up methodology for agile software development projects. It introduces Shape Up as similar to Dual Track Agile, with an initial 6-week discovery process. Key aspects of how shaping works include setting boundaries, roughing out elements, addressing risks, writing a pitch, and creating simple breadboarding prototypes. Other topics covered are cutting scope, how the pitch works, using betting tables instead of backlogs, dealing with bugs, and making progress on the whole stack through scope mapping and discovery charts.
Holacracy
This document discusses Holacracy, an alternative organizational structure to traditional hierarchies. It notes that current management structures were designed for factories, while Holacracy is designed for humans. Holacracy eliminates hierarchies and instead focuses on clearly defined roles and circles within an organization. It aims to embrace autonomy through separating people from roles and having roles, not managers, make decisions. While challenging to implement due to issues of power, some companies have adopted aspects of Holacracy.
AWS IAM
This document discusses AWS Identity and Access Management (IAM). It provides an overview of IAM including its ability to provide fine-grained access control and integrate with SAML 2.0 and LDAP. It notes issues with passwords and credentials like entropy and rainbow table attacks. The document outlines IAM roles and policies and recommends making credentials temporary to improve security.
CDKs
This document is a profile for Diego Pacheco, who is a cat's father, head of software architecture, agile coach, SOA/microservices expert, DevOps practitioner, speaker, and author. He has expertise in topics such as Terraform, CDKs, and CDKs code generation and maintains GitHub repositories on these subjects.
Encryption Deep Dive
Encryption Deep Dive: Randomness, Entropy, RNG, PRNG, AES, AES Operational Modes, Data Rotations, Java Encryption APIs, Tradeoffs, challenges, Envelope Encryption, KMS, and much more on all things encryption.
Sec 101
This document profiles Diego Pacheco and provides an overview of key software security principles including defense in depth, the least privilege principle, encryption, TLS and mTLS, misconfiguration and error handling, input sanitization, cross-site scripting (XSS), insecure serialization/deserialization, known vulnerabilities, logging and audit trails, threat analysis, and engineering friction. The document emphasizes applying security best practices to protect customer experience, brand integrity, and compliance while avoiding friction for engineering teams.
Reflections on SCM
Reflections on SCM: DevOps, CI/CD, Branches, Architecture, PRs, and many more considerations and thoughts.
Management: Doing the non-obvious! III
This document discusses various management concepts and techniques, including:
- Biases that can negatively impact decision-making like planning fallacy and availability bias.
- How work is becoming indistinguishable from sabotage due to bureaucracy and predictability.
- The importance of having "skin in the game" and being willing to be wrong to drive change and learning.
- Dealing with scarcity by identifying high and low performance areas and reallocating resources accordingly.
Design is not Subjective
Design is Not Subjective! Software design and Lean UX, Ux, Design Thinking are not that different after all. UML was in the right direction the problem was where we applied. In this video, I will explain why Design is not subjective. Video https://www.youtube.com/watch?v=ijGR6Tbhr54
Architecture & Engineering : Doing the non-obvious!
Diego Pacheco is a software architect, agile coach, and speaker who focuses on non-traditional approaches. Some of his views include that requirements can change and duplication is okay, tests don't always improve design or find bugs, and complexity sometimes needs abstractions but other times they add unnecessary complexity. He also believes teams will always have technical debt so it's important to prioritize fixing quick wins over deep technical issues, and that architecture is about people and enabling teams.
Management doing the non-obvious II
This document discusses various management concepts and principles:
- You cannot regulate failure in complex systems and it is better to focus on recovering from failures rather than trying to predict and prevent them.
- Product teams are more effective than feature teams because they are focused on discovering customer needs rather than having predefined solutions.
- Sharing a vision rather than a detailed roadmap allows for more flexibility and ability to change tactics.
- Psychological safety and an environment where people feel included, safe to learn and contribute, and safe to challenge the status quo is important for teams.
- Discipline is needed to successfully execute digital transformations but often lacks longevity and focus shifts to short term goals.
Testing in production
The document discusses testing in production environments using "dark canaries". Dark canaries involve deploying code changes to a small percentage of real users without their knowledge to test for issues before broad deployment. The key benefits are that it allows testing with real users and traffic in the actual production environment and catching problems early before they affect everyone. Some challenges are potential privacy issues if users are not informed and ensuring changes don't negatively impact the small group of unaware users.
Nine lies about work
The document outlines 9 common lies about work and proposes alternative truths. The lies discussed include that people care most about the company they work for rather than their team, that the best plan wins rather than intelligence in real-time, and that feedback and performance reviews can reliably rate people. The author argues that people primarily care about their team, intelligence is needed to adapt to a dynamic world, and that reviews mostly reflect raters rather than ratees. The truths proposed emphasize caring for one's team, prioritizing real-time intelligence over static plans, and that people can best rate their own experiences.
Management: doing the nonobvious!
This document provides advice and perspectives on management and leadership from Diego Pacheco. Some of the key points discussed include:
- Ego can distort reality and inhibit innovation, so leaders should suppress ego with humility.
- Not all communication needs to happen between all people; structured teams are better models than rigid organization charts.
- Feedback is difficult to give and receive but is important for growth if approached without emotion or defensiveness.
- Scenario modeling and role playing exercises can help train leaders by anticipating problems before they occur.
AI and the Future
The document discusses several topics related to artificial intelligence and the future, including:
1) Whether AI-generated music has soul or not.
2) The possibility of AI judges making faster parallel decisions.
3) Elon Musk's view that we are all already cyborgs.
4) Musk's proposal that augmented humans could regenerate organs and tissues by 2100 through technologies like neuralink.
5) The potential to reengineer humans and expand lifespans to 120-150 years through these technologies.
Dealing with dependencies
This document discusses dealing with dependencies between teams when developing software. It acknowledges that fixed release schedules and monolithic codebases can create issues. Some potential solutions proposed include using contracts and mocks between teams, restructuring code using domain-driven design principles, and creating lean shared libraries to reduce duplication while allowing independence. The document advocates for moderate approaches between extremes rather than ignoring problems with dependencies.
Dealing with dependencies in tests
This document discusses different types of test doubles (fakes, stubs, mocks, spies, and dummies) that can be used to deal with dependencies in tests. It explains what each type is and provides examples of when each might be used. It also discusses how to design code for better test isolation by reducing coupling and avoiding tightly binding components together, though this can sometimes make the code harder to test. Cross-cutting concerns like authentication are discussed as things that may be difficult to fully isolate or mock at a component level.
Kanban 2020
This document discusses issues that can arise with Scrum implementations and introduces Kanban as an alternative. It notes problems with a focus on dates in Scrum and retaining the process rather than changing it. Kanban is presented as a lean approach that emphasizes continuous learning and improvement rather than utilization. The document outlines Kanban concepts like value stream mapping, cost of delay, Kanban boards, and metrics that can be used to test if a Kanban approach is being implemented.
More from Diego Pacheco (20)
Architecture & Engineering : Doing the non-obvious!
Architecture & Engineering : Doing the non-obvious!
Lean the principles
- 1. Lean: The Principles @diego_pacheco Software Architect | Agile Coach
- 3. Unlearning
- 4. Scientific Management & Taylor 1910 People are not Smart, enough to know the best way to do it! They are lazy! Workers will do as little as possible. Workers do not care about quality. Experts tell workers exactly what to do! Do the best and cheapest way! Pay extra if they do it the best way right! Experts(management/supervisors) break the work in small parts so the workers can do it.
- 5. W. Edwards Deming The Humanist “All anyone asks for is a chance to work with pride.” 1940 People are good. People care !!! Respect People. People are about Trust, Pride, and applause not numbers. Continuous improvements in work process: PDCA. Intrinsic Motivation
- 7. Deming
- 9. Thomas Jefferson (don’t copy the tools) In matters of style, swim with the current; In matters of principle, stand like a rock.
- 10. Principles
- 11. See the Waste
- 12. Waste
- 13. 5 whys Don’t attack the symptoms!
- 14. Critical Chain
- 16. Toyota Kata: Continuous Improvement * http://www-personal.umich.edu/~mrother/Homepage.html
- 18. Kanban
- 19. "Putting people in good systems results in better results than putting people in bad systems – so attending to the systems will help the people's behavior" via @alshalloway Kanban is 80% about People!
- 22. The Essence of Kanban is… 1. Visualize the Workflow 2. Limit WIP 3. Manage Flow 4. Make Process Policies Explicit 5. Improve Collaboratively (using Models and the Scientific Method)
- 28. Kanban: Visual Flow | See to Believe
- 29. Kanban was metrics !!!
- 31. Classes of Services: Based on Cost of Delay!
- 32. Classes of Services Based on post-its colors
- 33. Sometimes things get wild!
- 34. Kaizen ( Continuous Improvements)
- 35. Lean: The Principles @diego_pacheco Software Architect | Agile Coach