Agile India 2014 Final Schedule is now available...   |   Attend the World's First Agile Job Fair   |   Join us for Agile Art!
Agile Software Community of India Agile India 2014 Conference
 
Lean Software Development: Mapping the Value Stream  
 
Workshop Details:
Mary and Tom have agreed to come to India to address the User Group in India. They will be arriving in Mumbai on June 27 and leaving from Delhi early the morning of Monday July 7.

We are planning 3 workshops on Lean Software Development in the following cities:
  • Mumbai - 28th June Saturday - Hotel Sea Princess (2 PM - 5 PM)
  • Bangalore - 30th June Monday - Taj Gateway (4 PM - 7 PM)
  • Delhi - 6th July Sunday
You can download the slides here :
Topic:

Of the many methods that have arisen to improve software development, Lean is emerging as one that is grounded in decades of work understanding how to make processes better. This workshop provides a practical, hands-on introduction to applying lean principles to software development.

The workshop will focus on workflow through a development organization:

  • How to pull value from customers
  • How to level the workload and increase the flow of value
  • How to find bottlenecks that create lumpy workflow, late delivery, and thrashing.
Value Stream Maps will be developed and critiqued, so participants can envision for themselves how they can use this lean tool to expose waste in their development process.

Audience:
This workshop will interest managers and team leads who understand XP and Agile, and are looking for practical ways to analyze and improve their workflow and discipline.

Agenda:
The workshop will start out with a brief overview of the Lean principle: Eliminate Waste. Then teams of 5-7 people will choose a real situation from among the members of the team, and sketch it with in value stream map. Next, each value stream map will be presented and critiqued. The workshop will conclude with an overview of the basic disciplines necessary for XP/ Agile software development.

Registrations:
In the spirit of complicating things for ourselves, we'll use the concept of a Position Paper for registration. You'll need to fill in your position papers on our wiki : Lean Workshop Position Paper's Wiki Link. Position Paper is your Price-of-Admission.

What is a Position Paper?

A Position Paper is a plain text response to the following questions:
  • What's your experience applying Agile values and principles in your teams/organizations?
  • What do you plan to learn /explore from this workshop?
  • How do you plan to contribute?
Rationale for requesting position papers:

We have limited 35 slots for each workshop. We wish we could accommodate everyone, but we cannot. So we need to find ways to identify the best candidates to attend this workshop. Keeping a registration fee really does not cut it. Position Papers are an excellent way to achieve this.

What we've seen at various leading conferences like OOPSLA, AWTA (Austin Workshop on Test Automation), AAFTTVW (Agile Alliance Functional Testing Tool Visioning Workshop), SDTConf (Simple Design and Testing Conference), Agile Coach Camp, etc is that having people write a position paper before coming to a conference/workshop leads to better discussion because people have thought about what they want from the conference/workshop. You don't want participants to come, heat the chair, eat & drink and leave with the same amount of knowledge as before.

We are looking for passionate and responsible individuals, who strive to learn new concepts, push the boundaries and constantly try to challenge themselves.

Position papers are rarely rejected. If we are not happy with the position paper, we might ask the participant specific questions to help them come up with a better position paper.

You can look at similar (but different) position papers that were submitted for the Simple Design and Testing Conference here and Agile Coach Camp here.

Presenters:
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 product manager and department manager. After Mary left the corporate world in 1998, she found herself managing a government software project where she first encountered the word “waterfall.” When she compared her experience in successful software and product development to the prevailing opinions about how to manage software projects, Mary decided the time had come for a new paradigm. So she wrote the award-winning book “Lean Software Development: An Agile Toolkit” to explain how the lean principles from manufacturing offer a new way of thinking about 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 sequel, “Implementing Lean Software Development: From Concept to Cash” which was published in 2006. A popular writer and speaker, Mary’s classes on lean software development offer a fresh perspective on product development in general and software development in particular.

 
Tom Poppendieck is a physicist and a photographer whose modeling and mentoring skills are rooted in his work as a physics professor.  His experience in IT infrastructure, product development, and manufacturing support, led to consulting project assignments in healthcare, logistics, mortgage banking, and travel services. He 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.

In 2003 Tom co-authored the award-winning book "Lean Software Development: An Agile Toolkit", and joined his wife Mary in spreading its message throughout the world. The sequel, “Implementing Lean Software Development: From Concept to Cash” was published in 2006.


http://poppendieck.com/people.htm

 
 
 
 
   
   
   
 
 
   
   

2005-2014 Copyright © Agile Software Community of India
Website designed and hosted by Agile FAQs