Usuario:Lefue/Taller2

Mary Poppendieck es una ingeniera de control de procesos, conferencista y escritora conocida por escribir el premiado libro Lean Software Development: An Agile Toolkit en el año 2003, en donde describe cómo los principios de Lean Manufacturing pueden aplicarse al desarrollo de software, dándo lugar al área conocida como Lean software development. Desde entonces, Mary se dedica a dar clases y conferencias junto a su esposo Tom Poppendieck, con quien escribió otros tres libros: Implementing Lean Software Development: From Concept to Cash en 2006, Leading Lean Software Development: Results are Not the Point en 2009 y The Lean Mindset: Ask the Right Questions en 2013. Es presidenta de Poppendieck LLC., una empresa consultora especializada en la aplicación de técnicas de producción Lean en el desarrollo de software.​​​

Trayectoria profesional

Obtuvo su título de grado universitario en matemáticas en Marquette University, y su título de maestría también en Matemática por University of Maryland.​ A comienzo de la década de 1980, mientras trabajaba para 3M en la producción de cintas de video, conoció el concepto de Just-in-Time o justo a tiempo, los cuales implementó junto a su equipo para mejorar sus procesos y afrontar la competencia de Japón. Esto les permitió mejorar sus procesos y reducir los costos a la mitad.​​ Luego, en 1998, trabajando para un proyecto gubernamental de desarrollo de software, es que se enfrentó con el método tradicional de desarrollo de software waterfall o desarrollo en cascada. Las diferencias entre este método de desarrollo usado en software y su experiencia previa con métodos Lean en otras áreas de producción la motivó a proponer un nuevo paradigma de desarrollo de software basado en Lean. Su primer libro Lean Software Development: An Agile Toolkit describe sus propuestas.​​

Desde entonces, se dedica a dar charlas en congresos y ofrecer clases. También escribió otros libros sobre desarrollo de software.​

Publicaciones

• Lean Software Development: An Agile Toolkit (2003)​
• Implementing Lean Software Development: From Concept to Cash (2006)​
• Leading Lean Software Development: Results are Not the Point (2009)​
• The Lean Mindset: Ask the Right Questions (2013)​

Mary considered retirement 1998, but instead found herself managing a government software project where she first encountered the word "waterfall." When Mary compared her experience in successful software and product development to the prevailing opinions about how to manage software projects, she decided the time had come for a new paradigm. She wrote the award-winning book Lean Software Development: An Agile Toolkit in 2003 to explain how the lean principles from manufacturing offer a better approach to software development.

Matt: How did that lead to Lean Software Development?

Mary: I never heard the term “waterfall” while I was working at 3M. We always had developers understand their customers and test every bit of code as they wrote it. The first time I heard about this thing called “waterfall,” it was prescribed by a contract for the State of Minnesota, and I couldn’t figure out how it could possibly work. Actually, it didn’t work very well at all, and I decided it was a rather strange way to develop software. So I decided to write a book, taking ideas from Lean Manufacturing and applying them to software development.

ALI: When did you first start applying Lean to your software development work? Where did you get the inspiration from? Mary: I think its important to set the record straight – most early software engineering was done in a manner we now call ‘Lean.’ When I was learning how to program, I was assisting a physicist do research into high energy particle tracing. The first computer I worked on was a minicomputer that he scrounged up from a company that had gone bankrupt. With a buggy Fortran compiler and a lot of assembly language, we controlled a film scanner that digitized bubble chamber film and identified frames with unique events for further study. My next job was designing automated vehicle controls in an advanced engineering department of General Motors. From there I moved to an engineering department in 3M where we developed control systems for the big machines that make tape.

Bio

De Personales 1

1. Mary Poppendieck started her career as a process control programmer, moved on to manage the IT department of a manufacturing plant, and then ended up in product development, where she was both a product champion and department manager. Mary considered retirement 1998, but instead found herself managing a government software project where she first encountered the word "waterfall." When Mary compared her experience in successful software and product development to the prevailing opinions about how to manage software projects, she decided the time had come for a new paradigm. She wrote the award-winning book Lean Software Development: An Agile Toolkit in 2003 to explain how the lean principles from manufacturing offer a better approach to software development. Over the past several years, Mary has found retirement elusive as she lectures and teaches classes with her husband Tom. Based on their on-going learning, they wrote a second book, Implementing Lean Software Development: From Concept to Cash in 2006, a third, Leading Lean Software Development: Results are Not the Point in 2009, and a fourth book, The Lean Mindset: Ask the Right Questions in 2013. A popular writer and speaker, Mary continues to bring fresh perspectives to the world of software development.

De Entrevista 1

1. I started out as a programmer. In the early 1980s, I became a systems manager in a manufacturing plant. We were experiencing serious competition from Japan, and we discovered that they were doing something different. They called it “Just-in-Time,” which later came to be called “Lean.” We got a book about how the Toyota Production System worked, and tried it in our plant. Over time, we cut our costs in half.
2. Mary: I never heard the term “waterfall” while I was working at 3M. We always had developers understand their customers and test every bit of code as they wrote it. The first time I heard about this thing called “waterfall,” it was prescribed by a contract for the State of Minnesota, and I couldn’t figure out how it could possibly work. Actually, it didn’t work very well at all, and I decided it was a rather strange way to develop software. So I decided to write a book, taking ideas from Lean Manufacturing and applying them to software development.

Libros

De Personales 1

1. Están mencionados los nombres

De Entrevista 1

1. Matt: So we understand lean a little bit now. Can you tell me about the books you've written on the subject - what makes them different? Mary: The first book we wrote in 2003 was “Lean Software Development.” It explains why lean thinking makes sense in software development. The second book, written in 2006, was Implementing Lean Software Development. It contains what we learned in three years about how to go about implementing Lean principles. The third book, which we just completed, is “Leading Lean Software Development.” It’s about the way leaders frame the way they look at system development, and about leadership roles. We wrote it because many leaders were looking for some guidance on Lean and Agile implementations. We don’t provide answers in this book, but we do talk about how leaders might think about the system development process.

Referencias

Personales

1. http://www.poppendieck.com/people.htm Bio - libros escritos - educación
   1. Mary Poppendieck started her career as a process control programmer, moved on to manage the IT department of a manufacturing plant, and then ended up in product development, where she was both a product champion and department manager. Mary considered retirement 1998, but instead found herself managing a government software project where she first encountered the word "waterfall." When Mary compared her experience in successful software and product development to the prevailing opinions about how to manage software projects, she decided the time had come for a new paradigm. She wrote the award-winning book Lean Software Development: An Agile Toolkit in 2003 to explain how the lean principles from manufacturing offer a better approach to software development. Over the past several years, Mary has found retirement elusive as she lectures and teaches classes with her husband Tom. Based on their on-going learning, they wrote a second book, Implementing Lean Software Development: From Concept to Cash in 2006, a third, Leading Lean Software Development: Results are Not the Point in 2009, and a fourth book, The Lean Mindset: Ask the Right Questions in 2013. A popular writer and speaker, Mary continues to bring fresh perspectives to the world of software development.

Entrevistas

1. http://www.informit.com/articles/article.aspx?p=1380369 Matt Heusser took the opportunity to sit down with Mary and Tom before their conference presentation to discuss some of the issues in software development today – and what we can do about them ALGO DE BIO
   1. Matt: You are best known for Lean Software Development, which came out of manufacturing. How were you initially exposed to Lean? Mary: I started out as a programmer. In the early 1980s, I became a systems manager in a manufacturing plant. We were experiencing serious competition from Japan, and we discovered that they were doing something different. They called it “Just-in-Time,” which later came to be called “Lean.” We got a book about how the Toyota Production System worked, and tried it in our plant. Over time, we cut our costs in half.
   2. Matt: So we understand lean a little bit now. Can you tell me about the books you've written on the subject - what makes them different? Mary: The first book we wrote in 2003 was “Lean Software Development.” It explains why lean thinking makes sense in software development. The second book, written in 2006, was Implementing Lean Software Development. It contains what we learned in three years about how to go about implementing Lean principles. The third book, which we just completed, is “Leading Lean Software Development.” It’s about the way leaders frame the way they look at system development, and about leadership roles. We wrote it because many leaders were looking for some guidance on Lean and Agile implementations. We don’t provide answers in this book, but we do talk about how leaders might think about the system development process.
   3. Matt: So we understand lean a little bit now. Can you tell me about the books you've written on the subject - what makes them different? Mary: The first book we wrote in 2003 was “Lea .......
2. https://www.agileleanireland.org/ali2019-keynote-interview-mary-poppendieck/ With Agile-Lean Ireland 2019 only a few short months away, we had a chat with one of our keynote speakers, Mary Poppendieck, to find out her thoughts on topics ranging from eliminating proxies, Lean, scaling Agile, and more
   1. ALI: When did you first start applying Lean to your software development work? Where did you get the inspiration from? Mary: I think its important to set the record straight – most early software engineering was done in a manner we now call ‘Lean.’ When I was learning how to program, I was assisting a physicist do research into high energy particle tracing. The first computer I worked on was a minicomputer that he scrounged up from a company that had gone bankrupt. With a buggy Fortran compiler and a lot of assembly language, we controlled a film scanner that digitized bubble chamber film and identified frames with unique events for further study. My next job was designing automated vehicle controls in an advanced engineering department of General Motors. From there I moved to an engineering department in 3M where we developed control systems for the big machines that make tape.
3. https://www.citerus.se/interview-with-mary-poppendieck-an-introduction-to-lean-software-development/
   1. Gustaf: When did you first start working according to Lean principles? From where did you get the inspiration? Mary: I was working in a manufacturing plant making video tapes in the mid 1980´s, and our Japanese competitors were selling video tapes at half of what it cost us to make them. We needed to understand how they could do this, and we discovered Just-in-Time production. We did two things: first, we provided every single worker in the plant with training in how a Just-in-Time flow works and had the workers design the details of a pull system. Then we stopped scheduling each workstation and instead sent a weekly schedule to the packing station. It worked like magic; inventory disappeared, quality improved, costs dropped, and customer response time was a week instead of a month.
   2. She is currently President of Poppendieck LLC, a consulting firm specializing in bringing Lean production techniques to software development.
4. https://www.infoq.com/interviews/mary-tom-poppendieck-architects-devops/
   1. Mary: Okay. My name is Mary Poppendieck and I started life as a process control engineer and I worked at University of Wisconsin and 3M for lots and lots of years and retired -- I don't know, before 2000. So, subsequently became author, speaker -- stuff like that

Otras ref

1. https://www.javiergarzas.com/2012/10/lean-software-development-2.html del artículo wiki Lean software development#cite ref-1
   1. La popularización del término «lean” aplicado al software, el lean software development, y su asociación a lo «ágil» aparece principalmente con el libro “Lean Software Development” de Mary y Tom Poppendieck.
2. IEEE paper tutorial from Mary: https://www.computer.org/csdl/magazine/so/2012/05/mso2012050026/13rRUxly93Y