This document discusses lean thinking and its application to software development. It begins by describing the traditional waterfall development process and its limitations. Next, it covers the origins of lean manufacturing from Toyota and its principles of eliminating waste, continuous flow, and responding to pull signals. The seven types of waste in development are then mapped to lean manufacturing wastes. The document concludes by outlining seven lean development principles and tools that can help eliminate waste and deliver value faster through techniques like kanban boards and iterative development.
Leaping from Waterfall to Agility & Agile Innovationrudreshts
This session brings out the key learnings of an engineering team at Harman when they adopted Agile Project Management Principles. The team had prior exposure to Waterfall Methodology but relatively new to Agile.
Although commitment, support from stakeholders along with training was provided to teams during Phase -1 of the adoption, real learning was in Phase – 2 when they started practicing the principles by owning complete agile lifecycle from iteration planning to retrospective. This presentation talks about five simple yet profound lessons learnt by the team during the journey and cultural change which enabled the team to innovate.
Leaping from Waterfall to Agility & Agile Innovationrudreshts
This session brings out the key learnings of an engineering team at Harman when they adopted Agile Project Management Principles. The team had prior exposure to Waterfall Methodology but relatively new to Agile.
Although commitment, support from stakeholders along with training was provided to teams during Phase -1 of the adoption, real learning was in Phase – 2 when they started practicing the principles by owning complete agile lifecycle from iteration planning to retrospective. This presentation talks about five simple yet profound lessons learnt by the team during the journey and cultural change which enabled the team to innovate.
Agile Cafe Boulder - Panelist and keynote slidesCloud Elements
Agile Cafe, 2/3 in Boulder, CO. Presentations from Adam Woods at StoneRiver, Bill Holst at Colorado Springs Utilities and keynote by Jean Tabaka at Rally Software.
Learn about problems of mature teams, about myths of pair programming and pair synergetic behaviors. How to implement pair programming in your company and how we did it in DaftCode.
Agile and Startups - What can go wrong - a Case study (Presented at ExpoQA 20...Vipin Jain
I recently got this wonderful opportunity to present a case study "Agile and Startups - What can go wrong" at ExpoQA, Madrid. The talk is about how startups think, build on the idea and try to sell it, until it is influenced by external factors like market and competitors. A lack of strong product owner didnt help as well. Agile, is a technology and is prone to failure as well, until it is practiced right.
Story Points considered harmful – a new look at estimation techniquesVasco Duarte
Story Points are the typical estimation unit for Agile Teams. But do they really work, or are there better ways to estimate? In this talk, we‘ll look at the problem of estimating, as well as empirical data questioning the validity of story points, and we‘ll explore new techniques, based on cognitive psychology, chronobiology, and good old common sense, that will immediately help your teams estimate more accurately.
Make simplified process decisions with the aid of our content ready Agile Delivery PowerPoint Presentation Slides. Discuss the technical requirements and schedule of your project using this professionally designed scaled agile framework PPT slideshow. The visually appealing PowerPoint complete deck contains forty-four topic-specific templates that help to represent agile delivery phases and goals. Take advantage of the sprint methodology PPT slides to showcase a strategic framework based on different criteria. Utilize the ready-to-use agile project management PowerPoint templates to represent the stages of the software delivery process such as initiation planning execution and release. Talk about the risk mitigations strategy that results in a decrease in risk and increase in value You can also use the scrum methodology PPT graphics to discuss the factors affecting the agile delivery such as market, customers, architecture impact, dependencies and so on. Thus, download our eye-catching and informative agile manifesto PowerPoint presentation to demonstrate the roles in disciplined agile delivery. Our Agile Delivery Powerpoint Presentation Slides ensure all elements combine beautifully. You will discover the best formula. https://bit.ly/3rUUrFL
Presentation I gave to the Chicago ACM about Lean Software Development. Full audio can be found here:
https://soundcloud.com/griffinc/intro-to-lean-software
Estimating is hard to get right;
Why is estimating hard to get right?;
Why do we need to estimate;
Agile estimating and planning;
Determine the teams velocity;
Identify features and stories;
Define stories or features;
Planning Poker;
Agile Release Plan;
What if you don’t know the teams velocity?;
Estimating from ideal team structure;
The effect of rework;
Proposals and SOW’s;
Agile Cafe Boulder - Panelist and keynote slidesCloud Elements
Agile Cafe, 2/3 in Boulder, CO. Presentations from Adam Woods at StoneRiver, Bill Holst at Colorado Springs Utilities and keynote by Jean Tabaka at Rally Software.
Learn about problems of mature teams, about myths of pair programming and pair synergetic behaviors. How to implement pair programming in your company and how we did it in DaftCode.
Agile and Startups - What can go wrong - a Case study (Presented at ExpoQA 20...Vipin Jain
I recently got this wonderful opportunity to present a case study "Agile and Startups - What can go wrong" at ExpoQA, Madrid. The talk is about how startups think, build on the idea and try to sell it, until it is influenced by external factors like market and competitors. A lack of strong product owner didnt help as well. Agile, is a technology and is prone to failure as well, until it is practiced right.
Story Points considered harmful – a new look at estimation techniquesVasco Duarte
Story Points are the typical estimation unit for Agile Teams. But do they really work, or are there better ways to estimate? In this talk, we‘ll look at the problem of estimating, as well as empirical data questioning the validity of story points, and we‘ll explore new techniques, based on cognitive psychology, chronobiology, and good old common sense, that will immediately help your teams estimate more accurately.
Make simplified process decisions with the aid of our content ready Agile Delivery PowerPoint Presentation Slides. Discuss the technical requirements and schedule of your project using this professionally designed scaled agile framework PPT slideshow. The visually appealing PowerPoint complete deck contains forty-four topic-specific templates that help to represent agile delivery phases and goals. Take advantage of the sprint methodology PPT slides to showcase a strategic framework based on different criteria. Utilize the ready-to-use agile project management PowerPoint templates to represent the stages of the software delivery process such as initiation planning execution and release. Talk about the risk mitigations strategy that results in a decrease in risk and increase in value You can also use the scrum methodology PPT graphics to discuss the factors affecting the agile delivery such as market, customers, architecture impact, dependencies and so on. Thus, download our eye-catching and informative agile manifesto PowerPoint presentation to demonstrate the roles in disciplined agile delivery. Our Agile Delivery Powerpoint Presentation Slides ensure all elements combine beautifully. You will discover the best formula. https://bit.ly/3rUUrFL
Presentation I gave to the Chicago ACM about Lean Software Development. Full audio can be found here:
https://soundcloud.com/griffinc/intro-to-lean-software
Estimating is hard to get right;
Why is estimating hard to get right?;
Why do we need to estimate;
Agile estimating and planning;
Determine the teams velocity;
Identify features and stories;
Define stories or features;
Planning Poker;
Agile Release Plan;
What if you don’t know the teams velocity?;
Estimating from ideal team structure;
The effect of rework;
Proposals and SOW’s;
My presentation for the Council for Programs in Technical and Scientific Communication (http://cptsc.org/) annual meeting. My teaching approach for UX and project management in an agile environment.
Designing for Dialogue: Persona-fying Healthcare UsersGuiseppe Getto
This is a poster for the 2014 NC Health Informatics Career and Internship Fair/Business of Healthcare Symposium at East Carolina University. The poster explains how developing personas can help improve healthcare communication and the design of digital healthcare systems.
Introduction to Lean Principles
Planning of your work processes to improve flow
Amy Hodgkinson and Trevor Taylor
National Improvement Leads, NHS IQ
Presentation from the Productive Endoscopy Workshop, Tuesday 15th October 2013 at Ambassadors Bloomsbury , London, WC1H 0HX
This meeting brought together teams from around the country, and embarked on creating and testing the productive endoscopy toolkit. The aim of the day is to allow time with your team for sharing of experiences and exchange of good practice, learn how to apply lean techniques and hear the impact of successfully implemented case studies.
Radical Roadmapping - Creating Synchronized Agile Product and Technology Road...Matt Roberts
This session will discuss why a company would create and maintain three major artifacts - Innovation Roadmap, Infrastructure/ Platform Roadmap, and Operations/DevOps Roadmap - as well as the process to do so. Further, it will cover how to synchronize them in order to move away from making "OR" decisions to making "AND" decisions that will please all stakeholders. It will also discuss key cultural changes that must be present in order to achieve maximum benefit from this approach and challenges experienced along the way to making this a reality at Socialware, a SaaS product company. Finally, this session will include real world examples of the evolution of these roadmaps over 18 months that participants can take away and use as guidelines for their own situations.
This was presented at the Keep Austin Agile 2016 conference, the #AgileAustin Product SIG and Product Camp Austin 2016 (#PCATX17)
Jan kennedy - I have an idea - what now? @WBIS2014winebis
Jan Kennedy, director of the Munich chapter of the Founder institute lead us through the choices and decisions that a would-be entrepreneur faces after having that idea.
The modern digital landscape transformed the way companies do business and the fundamental definition of sustainable business. The software is now the connective tissue of every product and service, and people increased affinity with technology redefined their experience standards and expectations.
This scenario has a bi-dimensional effect on organizations of all kinds.
Internally, this shift is quickly becoming a crucial operational challenge for businesses that require a complete rethinking of the way they organize and manage their work.
Externally, human-centricity has become a mandatory requirement to achieve success. Defining a business model around the continuous fulfillment of human needs is the only way to establish a sustainable business.
In this session, combining my experiences at Apple, Google, Samsung, Nokia, and Sony, we will introduce operational principles and present practical examples that can be implemented to establish a human-centered impact-oriented problem-solving practice, horizontally across any organization.
How to form an efficient team, how to architect a supportive workspace, how to define a productive process, but also how to manage team finance and how to connect multiple streams of work, are few examples of what will discuss in this session. The human-centered, impact-oriented, culture behind this paradigm has the ability to improve employees performance, increase customer satisfaction, and ultimately, increment business profitability and longevity.
Convergent Experiences: Why UX Approaches to Designing Modern Web Systems are...Catherine Hills
Presented at the Web Meetup Melbourne (November 2017) - "Web Accessibility, UX Approaches, and Lessons Learned from 22 years in Design"
Human-centered design and right-time right-context experiences are hugely important for building user-centered web applications. Competing with detailed considerations of the system user are business objectives of speed and value to market. Now, with the convergence of experiences in new technologies such as the Progressive Web, UX approaches such as early stage prototyping and testing, the establishment of accessible front-end design systems and Lean, experimental feedback loops are more important than ever. These UX practices support nimble, collaborative design behaviour and limit system front-end technical as well as design legacy in all that we build in our systems. The goals of these UX approaches are to benefit our users as well as optimise our workflows and human interactions in our teams.
https://www.meetup.com/en-AU/the-web/events/244943794/
"Considering Research" - Dave Hora @ User Research London 2019Dave Hora
We look at research from the perspective of mindset and impact. We examine:
• the research process
• the system that creates a user experience
• growth and development for researchers
Meaningful Technology for Humans: How Strategy Helps to Deliver Real Value fo...Björn Rohles
Presentation from the Silicon Techie Night #24 (2024) about strategy. It outlines ten impulses how strategy helps to deliver real value for people, by aligning business mission, vision, and strategy.
La quasi totalità degli sviluppi software è basata su un approccio per progetto. Un progetto, per definizione, è qualcosa di effimero. Ha un inizio, e soprattutto una fine, qualcosa di temporaneo. Il software non è temporaneo. Un software sopravvive fino a quando esiste almeno una persona che lo utilizza. A volte sopravvive anche più a lungo.
Perché continuiamo ad usare qualcosa di effimero per gestire qualcosa che effimero non è? Quali alternative abbiamo? Possiamo fare veramente a meno dei progetti?
What is good design, from One Big FieldFergus Roche
A presentation for the BBC Academy [with Anchor] for the "Innovation Academy: user experiences & interface design" panel by
Fergus Roche, One Big Field on Thurs 3rd Mar 2011.
I gave this talk at Velocity2015 conference in Santa Clara.
The goal is to teach a basic standard design process for learning about a new area, and then provide some tips on how devops folks can apply the process to their work.
I first tell a story with examples of how I came to understand the design problems in the devops space by using a standard design process with 4 key tools:
- Personas
- Mental Models
- Thinking by Analogy
- Prototypes
Then I close with tips on how to apply the tools more generally.
Product design for Non Designers - Montreal Digital Nomad MeetupSebastian Tory-Pratt
The basic principles of product design are very simple. And you don't need to be able to code to start building your product. This deck introduces some basic principles to help you start moving from idea to tangible product.
Best Crypto Marketing Ideas to Lead Your Project to SuccessIntelisync
In this comprehensive slideshow presentation, we delve into the intricacies of crypto marketing, offering invaluable insights and strategies to propel your project to success in the dynamic cryptocurrency landscape. From understanding market trends to building a robust brand identity, engaging with influencers, and analyzing performance metrics, we cover all aspects essential for effective marketing in the crypto space.
Also Intelisync, our cutting-edge service designed to streamline and optimize your marketing efforts, leveraging data-driven insights and innovative strategies to drive growth and visibility for your project.
With a data-driven approach, transparent communication, and a commitment to excellence, InteliSync is your trusted partner for driving meaningful impact in the fast-paced world of Web3. Contact us today to learn more and embark on a journey to crypto marketing mastery!
Ready to elevate your Web3 project to new heights? Contact InteliSync now and unleash the full potential of your crypto venture!
Explore Sarasota Collection's exquisite and long-lasting dining table sets and chairs in Sarasota. Elevate your dining experience with our high-quality collection!
What You're Going to Learn
- How These 4 Leaks Force You To Work Longer And Harder in order to grow your income… improve just one of these and the impact could be life changing.
- How to SHUT DOWN the revolving door of Income Stagnation… you know, where new sales come into your magazine while at the same time existing sponsors exit.
- How to transform your magazine business by fixing the 4 “DON’Ts”...
#1 LEADS Don’t Book
#2 PROSPECTS Don’t Show
#3 PROSPECTS Don’t Buy
#4 CLIENTS Don’t Stay
- How to identify which leak to fix first so you get the biggest bang for your income.
- Get actionable strategies you can use right away to improve your bookings, sales and retention.
Salma Karina Hayat is Conscious Digital Transformation Leader at Kudos | Empowering SMEs via CRM & Digital Automation | Award-Winning Entrepreneur & Philanthropist | Education & Homelessness Advocate
How to Build a Diversified Investment Portfolio.pdfTrims Creators
Building a diversified investment portfolio is a fundamental strategy to manage risk and optimize returns. For both novice and experienced investors, diversification offers a pathway to a more stable and resilient financial future. Here’s an in-depth guide on how to create and maintain a well-diversified investment portfolio.
When listening about building new Ventures, Marketplaces ideas are something very frequent. On this session we will discuss reasons why you should stay away from it :P , by sharing real stories and misconceptions around them. If you still insist to go for it however, you will at least get an idea of the important and critical strategies to optimize for success like Product, Business Development & Marketing, Operations :)
Reflect Festival Limassol May 2024.
Michael Economou is an Entrepreneur, with Business & Technology foundations and a passion for Innovation. He is working with his team to launch a new venture – Exyde, an AI powered booking platform for Activities & Experiences, aspiring to revolutionize the way we travel and experience the world. Michael has extensive entrepreneurial experience as the co-founder of Ideas2life, AtYourService as well as Foody, an online delivery platform and one of the most prominent ventures in Cyprus’ digital landscape, acquired by Delivery Hero group in 2019. This journey & experience marks a vast expertise in building and scaling marketplaces, enhancing everyday life through technology and making meaningful impact on local communities, which is what Michael and his team are pursuing doing once more with Exyde www.goExyde.com
Textile Chemical Brochure - Tradeasia (1).pdfjeffmilton96
Explore Tradeasia’s brochure for eco-friendly textile chemicals. Enhance your textile production with high-quality, sustainable solutions for superior fabric quality.
2. Waterfall Development Process Lean Approach Lean Development References
Waterfall Development Process
Lean Approach
Lean Development
References
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
3. Waterfall Development Process Lean Approach Lean Development References
Introduction
Waterfall Approach: Building software it's like building an
house
Analyze requirements
Design
Build
Verify
Mantain
Linear process: each phase completed
before the next one can start
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
4. Waterfall Development Process Lean Approach Lean Development References
Phases
Analyze requirements
Who are the stakeholders?
What is this software supposed to do?
Do we have conicting requirements?
...
Requirements should be
Documented
Actionable
Measurable
Testable
Traceable
...
The output is a Product Requirement Document
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
5. Waterfall Development Process Lean Approach Lean Development References
Phases
Design
Architecture of the software
How can we satisfy the requirements?
What aspects should we maximize?
Compatibility?
Security?
Performance?
Modularity?
...
Design principles
Output is a Design Description
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
6. Waterfall Development Process Lean Approach Lean Development References
Phases
Build
Actual coding
Testing of the single components
Integration between various parts
Output is the software solution
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
7. Waterfall Development Process Lean Approach Lean Development References
Phases
Verify
Testing of the entire solution
Fix of the issues
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
8. Waterfall Development Process Lean Approach Lean Development References
Phases
Maintain
Support
Maintainance
Other xes...
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
9. Waterfall Development Process Lean Approach Lean Development References
Conclusions
Advantages
Easy to understand
Good planning reduces costs
Easy to manage
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
10. Waterfall Development Process Lean Approach Lean Development References
Conclusions
Useful for projects with
clear requirements
xed context
clear timeframe
xed resources
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
11. Waterfall Development Process Lean Approach Lean Development References
Conclusions
In the real world it often does not work :(
Issues
Not exible
Late feedbacks
High cost for delays
No customer interaction
Decisions are taken far from the moment they will be applied
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
12. Waterfall Development Process Lean Approach Lean Development References
Conclusions
Usually building software is not at all like building an house
Answers to a lot of questions changes during the project
What do we want?
Are we going in the right direction?
Does it really work as expected?
Does it really feel as expected?
Do we still have the same resources available?
...
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
13. Waterfall Development Process Lean Approach Lean Development References
Conclusions
Let's get inspired by some other kind of production system...
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
14. Waterfall Development Process Lean Approach Lean Development References
History of Manufacturing
USA - Ford: Continuous system for mass production
Model T - 1910s-30s
A bomber an hour - 1944
Based on
Standardization
Assembly line
No variation of the product
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
15. Waterfall Development Process Lean Approach Lean Development References
History of Manufacturing
Japan - Toyota - Toyota Production System (1948-1975)
Initialy called Just In Time
Adapt to changing requirements
Reduce setup costs
Allow small batches
the market requires more customization and personalization
Workers can contribute more
Availability of component is key
Not inventory!
Kanban
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
16. Waterfall Development Process Lean Approach Lean Development References
History of Manufacturing
Kanban
Inspiration: shelf lling policy in a supermarket
When a order comes, the needed parts are taken and
assembled, the ticket is sent upstream to the previous step
the previous steps prepare what is written on the kanban and
send the product with the kanban downstream
if at this stage materials from a precedent step are needed, the
kanban mechanism works the same with the previous-previous
step as well
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
17. Waterfall Development Process Lean Approach Lean Development References
History of Manufacturing
Example
customer asks for a bike
assembly
take the wheels and send the wheel kanban upstream
take the frame and send the frame kanban upstream
assemble the bike and give it to the customer
wheel area
recieve the kanban, prepare a new pair of wheels, attach the
wheel kanban to the wheels
each part needed to build has a kanban, that is sent upstream
frame production area
recieve the frame kanban, prepare a new frame, attach the
kanban to the frame
each part needed to build has a kanban, that is sent upstream
...
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
18. Waterfall Development Process Lean Approach Lean Development References
History of Manufacturing
Lean Manufactoring is a concept expressed in 1990 in the
book The machine that changed the world
In a chapter by John Krafcick, CEO google self driving cars
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
19. Waterfall Development Process Lean Approach Lean Development References
Lean Manufacturing Concepts
Lean Manufacturing
Focus on reducing everything that does not provide value
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
20. Waterfall Development Process Lean Approach Lean Development References
Lean Manufacturing Concepts
Key Concept: Value
Value is everything the customer is willing to pay for
Value is dened by customer
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
21. Waterfall Development Process Lean Approach Lean Development References
Lean Manufacturing Concepts
Key Concept: Waste (MUDA)
Waste is bad and undesirable both from an economical and
ethical point of view
Waste is any activity that does not produce value
Is waste so bad?
Someone has to pay for the waste. This means minor margin
or customer paying more than needed.
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
22. Waterfall Development Process Lean Approach Lean Development References
Lean Manufacturing Concepts
The 7 Kind of waste
overproduction
transportation
stocks
motion
waiting
defects
overprocessing
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
23. Waterfall Development Process Lean Approach Lean Development References
Waste
Overproduction
Producing items not needed right now
- why?
needed = required to satisfy an order
coming from a customer
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
24. Waterfall Development Process Lean Approach Lean Development References
Waste
Transportation
Moving things does not change their value
risk and cost
producing where it costs less then moving where you sell works
only if you think in huge batches: you reduce the cost per unit
and if you produce enough you will have an advantage
so we somehow produce a lot and move things around to
satisfy the process, not the customer
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
25. Waterfall Development Process Lean Approach Lean Development References
Waste
stocks
raw materials / uncompleted items / nished goods
storing, counting, and listing items does not change their value
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
26. Waterfall Development Process Lean Approach Lean Development References
Waste
motion
Of people or parts during production, useless and risky
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
27. Waterfall Development Process Lean Approach Lean Development References
Waste
waiting
goods not being processed
value is not reaching the end of the
ow as fast as possible
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
28. Waterfall Development Process Lean Approach Lean Development References
Waste
overprocessing
more work than needed
producing with higher quality than needed
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
29. Waterfall Development Process Lean Approach Lean Development References
Lean Principles
Lean Manufacturing principles
1) Specify Value
2) Identify Value Stream
3) Make the Value Stream ow
4) Implement Pull Scheduling
5) Pursue Perfection
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
30. Waterfall Development Process Lean Approach Lean Development References
Lean Principles
Specify value
What is value for the customer?
Dened by customer
In a specic time
At a specic price
Represents needs of the customer
Are you willing to pay...
$20 to Bill, so he can add MP3 player to your car?
$20 to John so we can store your car for two days?
$20 to Marie, so we can x the mp3 player Bill installed upside
down?
...
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
31. Waterfall Development Process Lean Approach Lean Development References
Lean Principles
Identify Value Stream
each step in the entire production
creates value
creates no value but is (still) needed
Muda type 1
does not create value and it is not needed
Muda type 2
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
32. Waterfall Development Process Lean Approach Lean Development References
Lean Principles
Make the Value Stream Flow
remove type 2 waste
work on type 1 waste usually caused by
batch queue
goods waiting for a next step
meanwhile, value is postponed, we're waiting for the economy
of scale to be happy
rethik process and steps
every aspect: position, assumptions, speed, noise
small improvements can give more benets than New Big
Machines
workers are key pieces of this approach as they know better
their job
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
33. Waterfall Development Process Lean Approach Lean Development References
Lean Principles
Bicycle production - traditional
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
34. Waterfall Development Process Lean Approach Lean Development References
Lean Principles
Bicycle production - lean
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
35. Waterfall Development Process Lean Approach Lean Development References
Lean Principles
Implement pull scheduling
produce something only if a subsequent steps requires so
from production for inventory to production for customer
resources are used only if there is real demand
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
36. Waterfall Development Process Lean Approach Lean Development References
Lean Principles
Pursue perfection
focus and iterate
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
37. Waterfall Development Process Lean Approach Lean Development References
Example: Cola value ow
Auminum production
australia, bauxite, estraction phase
4tons to ll a truck
factory, 2tons of alumina powder - 30 mins
500k tons to ll a ship container - 2 weeks
travel to norway - 4 weeks
wait in the foundry - 2 months
melted
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
38. Waterfall Development Process Lean Approach Lean Development References
Example: Cola value ow
From Aluminium to can
hot rolling, sweden / norway
cold rolling, somwhere else (sweden / germany)
cut and preparation, uk
printing and cap
sorting
shipment to ller
lling
deposit
supermarket
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
39. Waterfall Development Process Lean Approach Lean Development References
Example: Cola value ow
Sumary:
Total time of value production: 3 hours
Elapsed: 319 days
lift up: 30 times
14 storage facilities across the world
4 times pack and unpack
24 percent of aluminim lost
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
40. Waterfall Development Process Lean Approach Lean Development References
Example: Cola value ow
Why?
A single can is very small
Everything in the ow is very large
Economy of scale requires so
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
41. Waterfall Development Process Lean Approach Lean Development References
Introduction
Lean Development
Rethink development with lean principles in mind
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
42. Waterfall Development Process Lean Approach Lean Development References
Waste Types
Waste types table
Lean Manufacturing Lean Development
Overproduction Extra features
Transportation Task switching
Inventory Work partially done
Motion Motion
Waiting Waiting
Defects Defects
Overprocessing Extra processes
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
43. Waterfall Development Process Lean Approach Lean Development References
Waste Types
Overproduction - Extra Features
Real temptation for Product Owners and Developers
Adding extra features is percieved as harmless, it is not
needs to be tested
needs to be maintained
can contain bugs
becomes obsolete
Cost of development is not always percieved
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
44. Waterfall Development Process Lean Approach Lean Development References
Waste Types
Transportation - Task switching
People are often assigned to multiple
projects
Or multiple teams
Or multiple roles
This may be needed in some scenarios
but every context switch creates waste
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
45. Waterfall Development Process Lean Approach Lean Development References
Waste Types
Inventory - Work partially done
Uncompleted features
Something is there, so you do not want to remove it
But is not nished so you cannot enable it
Will it really work at the end?
Is code you have spent resources on, but is not producing value
Brings costs and risks for no reason
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
46. Waterfall Development Process Lean Approach Lean Development References
Waste Types
Motion
Also, accessibility issue
How far should I go to get the answer?
Artifacts move as well
Requirements
design docs
code
code / feature hando
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
47. Waterfall Development Process Lean Approach Lean Development References
Waste Types
Waiting
Each wait postpones the value for the customer
Slower ouput means slower response to request
One of the principles of lean development is to decide as late
as possible, waiting makes this less ecient
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
48. Waterfall Development Process Lean Approach Lean Development References
Waste Types
Defects
Waste amount is the impact multiplied the time it goes
undetected
Finding defects early is crucial
test immediatly
iterate often
release in production soon
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
49. Waterfall Development Process Lean Approach Lean Development References
Waste Types
Overprocessing - Extra processes
Excessive Paperwork
If there is noone waiting for it, it is a waste
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
50. Waterfall Development Process Lean Approach Lean Development References
Principles
Seven Principles
Eliminate waste
Amplify Learning
Decide as late as possible
Deliver as fast as possible
Empower the team
Technical decisions taken by techicals
Late decisions means not having time to review everything
Build integrity in
External and internal
See the whole
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
51. Waterfall Development Process Lean Approach Lean Development References
Tools
Tools to...
Eliminate Waste
Map the value stream, nd the blocked areas, correct them
Amplify Learning
Feedback Loops
Iterative processes
Decide as late as possible
Concurrent development
Keep options available
Wait until the last responsible moment
Deliver as fast as possible
Pull system: let people gure out what to do
Kanban or similar signals
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
52. Waterfall Development Process Lean Approach Lean Development References
Tools
This course as a kanban board
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
53. Waterfall Development Process Lean Approach Lean Development References
Tools
Tools to... (2)
Empower the team
Manager Leader
Cope with complexity Cope with change
Plan and budget Set direction
Organize and sta Align people
Track and control Enable Motivation
hire good people, and leave them alone
If you put fences around people you get sheep
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
54. Waterfall Development Process Lean Approach Lean Development References
Lean from the real world
Stories from the real world
Reduce Waste in bugs
Lean handling of icons and strings
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
55. Waterfall Development Process Lean Approach Lean Development References
References
Bibliography
Lean Thinking - Womack and Jones - part 1
Lean Development - Poppendieck and Poppendieck -
introduction, chapter 1, concepts from other chapters as well
francesco mapelli (@mapelli) University of Insubria
Lean Thinking
56. Waterfall Development Process Lean Approach Lean Development References
References
Attribution
Diagrams of the bicycle factory layout taken from Lean
Thinking and Strategic Asset Management , MRO Software
Salami picture by André Karwath aka Aka
francesco mapelli (@mapelli) University of Insubria
Lean Thinking