Mary Poppendieck, Thought leader in the software industry

Mary Poppendieck

Biography: Mary Poppendieck

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 six 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 popular writer and speaker, Mary continues to bring fresh perspectives to the world of software development.

Software Passion: Putting Passion back into Programming 

Presentation: "What is this thing called "Pull"?"

Track: MASTERING LEAN MANAGEMENT / Time: Monday 13:30 - 14:30 / Location: Rytmisk Sal, Musikhuset

Pull means a lot of things to a lot of people:
Pull = Pursuing Passion
Pull = Putting Customers First
Pull = Producing Based on Demand
These definitions of pull have something in common; they all contain a strong element of observation, orientation, decision, and action – the OODA loop. As the pace of business increases and unexpected events become common,
pull becomes like an increasingly attractive alternative to push.

The problem is, pull doesn’t work without preparation. Pull requires an environment that sends the correct signals, methods to rapidly detect the right patterns, and people who have the skills and training to make the right decisions. So the real challenge of pull is creating the environment, devising the patterns, and developing the people that ensure the right decisions are made and rapidly carried out, no matter what situation presents itself.'
Keywords: Pull, Push, Passion, OODA, Customer, Demand, Uncertainty
Target Audience:  Team leads and managers who influence work environments.

Workshop: "Lean in a Nutshell"

Track: TRAINING: AGILE SUNDAY / Time: Sunday 09:00 - 16:00 / Location: Trifork 1

It’s hard to imagine how the Empire State Building - all 85 stories plus a dirigible mooring dock - could be built in a year. In the spring of 1930, there was nothing but a hole in the ground, and by fall, the building looked pretty much the way it looks today. How did they do it?

Fundamentally, they framed the problem differently than we do today. Their mental model - which dictated what was important and what was not – would not be recognized in today's commercial world, except perhaps by those who understand lean thinking. The Empire State Building was not framed by cost, scheduled, and scope. It was constrained by two acres of land, New York City's zoning ordinances, $35,000,000 of capital, the laws of physics, and an absolute deadline. It was constructed by deeply experienced leaders who framed the issues they faced in terms of flow - the flow of materials, the flow of people, and the flow of cash.

Join Mary and Tom Poppendieck for a Lean in a Nutshell - a fast-paced tutorial aimed at senior developers and team leads. The lecture and discussion will focus on framing the software development process; it will cover four key frames that really make a difference when you are developing software: (1) A systems view, (2) Essential technical capability, (3) What it takes to deliver reliably, and (4) How to improve.

Here is the table of contents in a nutshell:

  • Failure Demand – what it is, what causes it, and why you have to get rid of it
  • Technical Excellence – what it means, where it comes from, and why it’s not optional
  • Workflow – how it’s different than scheduling and why it’s more important than deadlines
  • Customer Outcomes – just how concerned should the development team be?
  • Relentless Improvement – taking retrospectives to the next level