program selection system

I present agile practices—KPT, Estimate Retrospectives, Positive Strokes, Iteration Planning, Darts, Task Kanban, and Overtime Tickets—that I have actually practiced in a project where I worked as a Technical Lead. I also discuss the benefits and careful points we experienced when implementing these practices from the viewpoint such as team building and leader’s mind-set.

“None of the number of people, technology nor a power of money will complete this construction after all. It is the people’s feelings which we can only rely on.”

Agile Development teams can utilize a number of techniques to visualize and track the items they work on. There is also various models to manage your personal life, Getting Things Done and the Mark Forster models.
For Product Owners and analysts there is a lack of similar tools and techniques. This demonstration will show how a Kanban board (task board with “states”) can be combined with a “round robin” scheme to keep analysist and Product Owners working on multiple tasks of high priority, but with potentially long lead times and fuzzy done criteria.

I will present examples of process improvement (Kaizen) in factories in Japan, demonstrate how the Toyota Production System (TPS) constantly improves the way things are done to meet changing customer needs, involving wokrplace(Gemaba) people. After presentation of key TPS concepts, small groups will explore commonalities between Agile and TPS by developing Mind Maps, and then exchange the results. Note that this is a re-run of the same program at Agile2007, presented by Mary Poppendieck and Kenji Hiranabe(me). This time, the content is shortened, focusing on the best stories.

This workshop explores three important Lean concepts - Kanban, Flow and Cadence (KFC) - which can be combined to generate a more pipeline-based approach to software development, as opposed to the more common timebox-based approaches of more traditional Agile methods. The presenters will describe their experiences implementing these ideas at Yahoo!

How Real Options can help in running your project. Real Options is a decision-making process based on Financial Option Theory and Applied Psychology that can be used to manage risk.

The main challenge of this session is changing people’s mindset and behavior. We found a rational decision-making process based on maths and logic, rather than emotion and intuition. This session demonstrates that Real Options are at the heart of most Agile practices and principles, and are what drives Toyota.

After this session making decisions will never be the same again.

Any process with a recognizable workflow can be made into an efficient pull system by applying the kanban method. We can use kanban to transform either a traditional phase/gate software development system or a time-boxed iterative system into a lean continuous-flow system.

—— begin 90 word abstract ——
How can we as software professionals and craftsmen know that we are producing the most valuable system at just the right time for our users? The concept of “pull” from lean manufacturing challenges mainstream approaches to software development and reconsiders how value is delivered to the customer by inverting the thought process and focusing first on delivery. In this demonstration participants will experience how a real working system can be constructed from the ground up by employing popular industry “signals” to “pull” the creation of working software.
—— end 90 word abstract ——

Come and take it! Learn how to build the right system where each agent takes just what they need, just in time, to create value for the customer.

How can we as software professionals and craftsmen know that we are producing the most valuable system at just the right time for our users? The kanban method and the concept of “pull” from lean manufacturing, in combination with agile values and practices, provide a powerful guide for how we can improve our profession by employing popular industry “signals” to “pull” the creation of working software.
By inverting the thought process and focusing first on delivery, “pull” challenges mainstream approaches to software development by reconsidering how value is delivered to the customer.

In this demonstration participants will experience how a real working system can be constructed from the ground up through the definition of executable specifications. See how through a series of micro-iterations, requirements can pull the creation of executable specifications, developer tests, production code, and refactorings.