Lean Software Development i Malmö 5/12 2003
Heldag: Lean Software Development
|
Tid & Plats: |
|
|||
|
Tema: |
Lean Software Development |
|||
|
För vem: |
Utvecklare, testare, projektledare, produktchefer. |
|||
|
Presentatörer: |
Mary Poppendieck, Poppendieck LLC,
USA |
|||
|
Pris: |
4 995 kr exklusive moms |
|||
|
Anmälan |
Senast den 27/11 Registrera dig här! |
|||
|
Arrangör |
Lean Software Development
"Mary and Tom Poppendieck have provided us with a more understandable, robust, and everday framework for understanding the workings of agile processes." Ken Schwaber, chairman, Agile Alliance
Mary Poppendieck är IT och projektveteran från 3M. Under hennes tid på 3M fick företaget stora framgångar med Lean Thinking som bygger på best practices med ursprung i Toyota och andra framgångsrika japanska företag. Först när jag hörde talas of Lean Software Development utan någon bakgrund tänkte jag spontant: "Åh nej, inte en sälja-konsult-metod till" Det var lätt att vara skeptisk och tro att ännu en guru ville profilera sig med sin egen metod för att få en bra plats vid köttgrytorna. Men jag hade fel. Det Mary och hennes man Tom Poppendieck har gjort är att skapa en brygga mellan tänkesätt som gjort företag som 3M och Toyota framgångsrika och lättrörliga (agile) metoder som SCRUM och eXtreme Programming(XP). Mary är numera även SCRUM-master , dvs utbildad instruktör i SCRUM-metoden
Det Mary och Tom ger oss är ett systemtänkande som passar både i det lilla och stora företaget. Mary & Tom pekar i sin bok Lean Software Development -An Agile Toolkit på exempel som att Toyota startade som ett litet företag, det fanns helt enkelt ingen stor bilmarknad i efterkrigstidens sargade Japan. Men man tänkte på hur man skulle få ekonomi i att göra bra produkter, även i liten skala. Med det synsätt som Toyota grundades, blev resan till positionen som ett av världens största bilföretag väsentligt enklare. (Intressant är också Marys exempel när Toyota hjälpte GM att starta om en problemfabrik och fick den att bli en av USA:s absolut bästa. GM försökte sedan kopiera arbetsformerna moment för moment till andra fabriker, men förstod inte den bakomliggande filosofin. Naturligtvis fungerade det inte.)
Systemtänkade? Låter det tungt och jobbigt? Nej, det innebär inte att vi drar på oss en stor process-överrock. Det innebär att vi ser hela företaget, samt våra kunder och leverantörer som ett enda system. Det sundaste är att alla samarbetar för att få bästa resultat, eller hur? Våra agile-metoder för lättrörlig utveckling, som XP och SCRUM . Det var ingen överraskning efter att ha läst parets bok att jag hittade Eli Goldratts klassiska Målet (The Goal) bland referenserna. Mary & Tom visar varför XP, SCRUM och liknande slimmade metoder fungerar i ett system och hur vi kan gå vidare och tillämpa samma synsätt i fler delar av verksamheten, bara vi förstår systemet. Mary visar t ex utmärkta modeller för agile contracts, dvs hur man hanterar ex konsulters åtaganden och IT-projekt med lättrörlighet och flexibilitet, efter en framgångsmodell som Toyota skapade i relationen med sina underleverantörer.
Numera sitter Mary dessutom i styrelsen för internationella Agile Alliance (www.agilealliance.org) och har där fått förtroendet att ansvara för alliansens finanser.
|
|
Både i boken och under presentationerna ger Mary & Tom oss efter hand en verktygslåda med 22 verktyg. Några av dom, som Refactoring, känner vi direkt igen från XP. Andra verktyg som ex "Pull Systems" förklarar varför XP:s Planning Game fungerar så bra. Mary & Tom visar oss att Planning Game är en variation på det som japansk industri kallat kanban-kort i många, många år. |
Vi får också handfasta exempel på lyckad lättrörlighet (dvs agile) i allt från USA:s marinkår ("Improvise and adapt", minns ni?) till börskändisar som Nucore och Xerox.
Lean Software Development är en verktygslåda för oss som vill veta varför och hur agile fungerar. Det är inget konkurreande alternativ till XP och SCRUM, men ytterst användbart för alla som vill jobba lättrörligt enligt XP, SCRUM eller liknande, precis som t ex Scott Amblers Agile Modeling. Se Lean Software Development som ett turbo-kit för lättrörlig utveckling.
Erik Lundh
XP2003: Ward Cunningham, Kent Beck, Mary Poppendieck och Erik Lundh spelar ett spel om XP av Joshua Kerievsky inför publik.
Innehåll
Introducing Lean Software Development
We tend to keep a large inventory of software-in-process -
requirements that are not proven, analysis that is not reduced
to code, code that is not tested, sub-systems that are not
integrated, systems that are not released to production.
Lurking in this partially done software are huge risks. We
don't know that the software will actually work, that it will
integrate easily with the rest of our software, that it will
truly solve the business
problem.
Not only is a large inventory of partially done software development risky, it contains a lot of waste. Waste is anything we do that customers don't perceive as value, anything that gets in the way of value flowing rapidly from customer request to customer satisfaction. How long does it take for a customer request to find its way through your software development process? How much extra baggage does it pick up on the way?
Lean thinking has let to dramatic improvements in manufacturing and product development. It can have similar impact on software development. The Lean Development Class begins with a description of how lean thinking can be applied to software development and tailored to meet the needs of various environments.
Once you appreciate the value of lean software development, what happens next? Your first step is to take a walk through your software development process from receipt of customer request to delivery of customer value. While doing this walk-through, create a value stream map to helps you to really see the waste in your process. Then create a future map of how your value stream should work, and start working toward the future.
The next step in moving to Lean Software Development is to initiate Software Kaizen Events. A Kaizen Event is the fundamental improvement process for lean operations. At a Kaizen Event, front line workers address problems in their areas, defining and implementing solutions during the course of the Event. Kaizen Events charter cross-functional and cross-level teams to implement their own best ideas.
Getting Started With Lean Software Development
Course Outline
Introduction Lean Thinking
Lean Thinking focuses on understanding what customers will value and then delivering exactly that value and nothing else, as rapidly as possible.
Lean Thinking establishes the principles behind Agile Software Development. Whether you use XP or Scrum, you will find Lean principles behind these practices, making it clear why agile software development works so well.
Lean Software Development is different. First of all, don't do anything unless it adds immediate customer value. Second, don't make any decisions before their time. And third, organize to deliver value reliably, repeatedly, and very quickly.
Examples and Exercises
Discover Waste
Delay Commitment
Deliver Fast
Fundamentals of Lean Software Development
Good software doesn't just happen, integrity must be built in from the start. This means involving everyone in the development process from the start - not only those who will be using the software and those who will be writing the software, but also those who will be providing operational support. It also means developing software and tests at the same time, keeping the design simple and clean as time goes on.
Examples and Exercises
Design for Maintainability
Build Integrity In
Getting Started
What do you do to get started with Lean Software Development? Lean initiatives are start with a map of the current flow of work and information in your organization, helping you to discover the waste. Then a new map is created, based on lean thinking. Finally, the workers deign and implement the changes to their process, usually through Kaizen Events.
Mary PoppenDieck
Mary Poppendieck has been in the Information Technology industry for twenty five years. She has managed solutions for companies in several disciplines, including supply chain management, manufacturing systems, and digital media. As a seasoned leader in both operations and new product development, she provides a business perspective to software development problems.
As Information Systems Manager in a video tape manufacturing plant, Poppendieck first encountered the Toyota Production System, which later became known as Lean Production. She implemented one of the first Just-in-Time systems in 3M, resulting in dramatic improvements in the plant's performance.
Poppendieck's team leadership skills are legendary in 3M, where new product development is a core competency. One team commercialized a graphics interface controller three times faster than normal. Another team not only developed an image database system in partnership with a start-up company, but also set a new international standard for image formats.
Three times Poppendieck has partnered with small companies, twice negotiating and funding a multi-million dollar equity investment. But understanding small companies from the investor point of view was not enough; so she joined one of the start-ups to lead its R&D effort. Today Poppendieck is Managing Director of AgileAlliance and is a Senior Cutter Consortium Consultant.
A popular writer and speaker, Poppendieck's tutorials on managing software development offer a fresh perspective on project management. Her book Lean Software Development: An Agile Toolkit, was published by Addison Wesley in May, 2003.
Contact
Phone: +1 952-934-7998
Email: mary at poppendieck.com
Web:www.poppendieck.com
Expertise
· Lean Software Development
· Value Stream Mapping
· Software Kaizan Events
·Leading Software Projects
· Software Contracts
Education
Master of Science, Mathematics
University of Maryland
College Park, MD
Bachelors of Science, Mathematics
Marquette University
Milwaukee, WI
Publications
Software Development Magazine, May and June, 2001, Lean Programming (Two Part Article); May, 2002, Wicked Projects; August 2003, Concurrent Development
C/C++ User's Journal, October, 2003, Lean Software Development
Cutter IT Journal, September, 2002, Using XP for Safety-Critical Software
Cutter Executive Report, August, 2003, Lean Development and the Predictability Paradox.
Book: Lean Software Development: An Agile Toolkit, Addison Wesley, June 2003
Mary Poppendieck on Panel with Ken Schwaber, Martin Fowler, Kent Beck, and David Parnas.
Tom Poppendieck
Tom Poppendieck is an enterprise analyst and architect, and an agile process mentor. He focuses on identifying real business value and enabling project teams to realize that value. Tom specializes in upstream, customer side processes and in effective collaboration with the downstream, development side of a project team to maximize development efficiency, system flexibility, and business value.
Tom has delivered excellent results as mentor or coach of Agile RUP, Scrum, and XP teams in diverse business domains. Tom is a practitioner as well as a coach using agile methodologies that are use case/feature driven, domain model based, and component, and service-oriented architecture centered.
Tom Poppendieck led the development of a world-class product data management practice for a major commercial avionics manufacturer that reduced design to production transition efforts from 6 months to 6 weeks. He also led the technical architecture team for very large national and international Baan and SAP implementations.
Tom has 22 years of experience in computing including 8 years of object technology. His modeling and mentoring skills are rooted in his experience as a physics professor. Tom maintains a broad technical, process and management knowledge base to support productive collaboration with all project stakeholders and contributors. His early work was in IT infrastructure, product development, and manufacturing support, and evolved to consulting project assignments in healthcare, logistics, mortgage banking, and travel services.
Contact
Phone: +1 612-804-7217
Email: tom at poppendieck.com
Web:www.poppendieck.com
Expertise
· Training and Coaching
o XP
o Scrum
o Agile Modeling
· Customer Engagement
o Use Cases
o Conceptual Models
o Business Rules
o Value Stream Mapping
Education
PhD in Physics
University of Wisconsin
Madison, Wisconsin
Publications
Lean Software Development: An Agile Toolkit Addison Wesley, June 2003.
Erik Lundh
|
Erik Lundh har jobbat med produktorienterad utveckling av programvara i 20 år, sedan 90-talet med fokus på bättre sätt att utveckla. År 2000 fick Erik kontakt med eXtreme Programming(XP) och lättrörlig utveckling(Agile) via arbete med ett svenskt tvärindustriellt designcentrum. Erik var med på den första internationella XP-konferensen XP2000 och har deltagit varje år sedan dess. Designcentret lades på is, men XP väckte stort intresse. Sedan dess har Erik varit fullt upptagen med att propagera för bättre arbetsformer med XP som konkret metod, samt agera coach i nyckelprojekt när team och företag anammar XP som lättrörlig arbetsmetodik. Erik har de senaste åren varit coach i ett antal XP-projekt med hög profil samt utbildat 100-tals utvecklare, testare, projektledare och linjechefer i lättrörlig utveckling med XP. Eriks arbete med spridning och införande av XP och lättrörlig utveckling har uppmärksammats internationellt. På senare tid har han blivit inbjuden till flera expertpaneler på internationella konferenser: XP2002 och OOPSLA 2002 tillsammans med bl a Kent Beck, Ron Jeffreis, Rob Mee, Gay Pollice(Rational) Erik är också en mycket aktiv medlem i det sydsvenska kostnadsfria förbättrings-nätverket SPIN-SYD med ett 40-tal företag (Ericsson, ABB, IKEA, mfl ) samt Lunds Tekniska Högskola som medlemmar. Publikationer: Mer om Erik: |
Erik Lundh
OOPSLA 02: Erik i panel med Kent Beck, Ron Jeffreis, Rob Mee mfl
TCRE02 workshop under RE02
XP2002: Erik presenterade sitt sätt att sprida XP via nätverk och satt i panel med Kent Beck |
Agenda
|
8:30 |
Registrering |
| 9:10 |
Hur passar Lean Software Development in i Agile-familjen? Erik Lundh - svensk pionjÀr inom XP-coaching |
|
9:15 |
Introduction to Lean Thinking â?? Mary Poppendieck Mary PoppenDieck Comments by Erik: |
|
10:00 |
Kaffe med smörgås |
|
10:30 |
Examples and exercises: Discover Waste, Delay Commitment, Deliver Fast â?? Mary & Tom Poppendieck Comments by Erik: |
|
12:00 |
Lunch |
|
13:00 |
Fundamentals of Lean Software Development Mary PoppenDieck Comments by Erik:
|
|
14:00 |
Examples and exercises: Build Integrity In, Design for Maintainability Mary & Tom Poppendieck Comments by Erik:
|
|
15:00 |
Kaffe |
|
15:30 |
How to get started: Value Stream Mapping and Software Kaizen Events
Mary PoppenDieck Comments by Erik: Software Kaizen Events: Focused one-week team projects that often brings dramatic results . Kaizen Events is a famous bets practice i some of Japans most sucessful industries |
|
16:30- |
Sammanfattning, diskussion och frågor |
| 17:00 |
