Feb
4

Just added:

Joshua Kerievsky will talk about “The Limited Red Society“.

You’ve heard about limiting WIP (Work-In-Progress) but how good are you at limiting red time? Red time is when you have compilation errors and/or failing tests. A growing group of practitioners have learned how to effectively reduce red time while test-driving and refactoring code. To understand how to limit red time, it helps to visualize it. In this talk, I will analyze live programming sessions using graphs that clearly visualize red time. You’ll learn what programming processes help or hurt our ability to limit red time and you’ll gain an appreciation for the visual cues that can help make you a better programmer and fellow member of the Limited Red Society.

Joshua Kerievsky leads Industrial Logic, a fourteen-year-old company that guides organizations in successful agile transitions. He has more than twenty years of experience in the software field, is an expert and early pioneer in agile management and Extreme Programming, and is a prolific author of eLearning albums that help companies around the world “scale agility faster.” Joshua’s 2004 bestselling book, Refactoring to Patterns, won a Jolt Cola award. His pioneering work in agile processes has helped popularize readiness assessments, storytest-driven development, and agile chartering.

Feb
3

Just added:

Henson Graves will speak on “Why Programs Fail“.

Some personal observations are made about why large software intensive programs often fail, or at least are over budget, don’t meet schedule, and under produce in terms of quality. The observations apply not only to software systems but to software-intensive physical systems. The observations start with failures in organization and responsibility allocation, and work down to failures attributed to processes and design methods. Observations are made about how development progress can be realistically measured. Some conclusions emerge as to how to avoid pitfalls, and what could be done to fix systemic problems. The methods for measuring technical progress suggest methods for determining program success or failure prognosis. One wants to at least keep from get blindsided unnecessarily when a program goes in the ditch.

Over 30 years of aerospace experience with the development and analysis of software-intensive systems. Lockheed Martin Senior Fellow (Emeritus). Developed one of the first effective auto-code systems (“LEAP”), to produce software for an operational satellite; technical lead for the DARPA Simulation Based Design Program; lead for Joint Strike Fighter distributed product information management system; published over 20 papers on a variety of system, software, and information management topics; currently focusing research and development to integrate formal methods of logic with Model-Based System Engineering methodology, including the establishment of a formal semantics for SysML using OWL.

Feb
3

Just added;

Mike Sivertsen will speak on “Cognitive Kanban: Improving Decisions in a Complex World“.

Complexity is ever-present and increasing in systems engineering and software development. However, most systems engineering standards, computer models and associated approaches are best suited to environments in which requirements are known or knowable, and cause and effect are closely linked.

The Cynefin (ku-NEV-in) framework (developed by David Snowden) provides for improved decision making in both typical and more challenging situations. Simple, complicated, complex and chaotic domains require different approaches in order to best meet project goals. Through techniques derived from social computing and a kanban-like “pull” approach, people’s fragmented knowledge and understanding (“cognition”) can be combined to build better decisions than the sum of the parts. This speeds and strengthens individual and organizational responses to competitive threats. Examples drawn from business, science and technology will illustrate lessons to be learned and useful practices across a continuum from strategic to tactical.

For 30 years Michael (Mike) Sivertsen has applied a wide range of technical skills and “Learning Faster” business solutions to increase organizational and individual performance. These solutions have individually returned cost-savings up to $1 million. His industry background in energy, IT, and aerospace has spanned positions such as Health Physicist, Nuclear Engineer Instructional Designer, Business Systems Analyst, Information Architect, Consultant–Organization and Leadership Development, and Systems Engineer.

In 2004, he received Lockheed Martin Aeronautics’ highest award, the Aero Star, for developing a unique tool for improving program management leadership. From 2004 to 2006, Mike pioneered advances in information and knowledge management to enable capturing the “lessons learned” of work groups and individuals on the largest aerospace program in U.S. history, the F-35 aircraft. Mike is currently a leader in a knowledge continuity program at Lockheed Martin Aeronautics (LM Aero) in Fort Worth, Texas.

Mike earned a Bachelor of Science in Physics from the University of Minnesota in 1979 and a Master of Knowledge Management from California State University, Northridge, in 2009. He currently holds a Certified Systems Engineering Professional (CSEP) designation from the International Council on Systems Engineering (INCOSE).

Feb
3

Just added:

James Sutton will be speaking on “Lean Systems Engineering: Key to Accomplishing Big Things“.

Lean focuses work on value, which speeds development and reduces waste. Agile emergentbehavior provides ways to deal with ambiguity and defer commitment until it is absolutely necessary. In software projects, Lean and Agile are most commonly applied to fairly simple problems; their writings mostly address these kinds of situations. Developing more complex systems, or even simpler systems where above-normal assurance of success is needed, is greatly aided by the ideas in Systems Engineering. Mr. Sutton will give an overview of how relatively simple ideas from Systems Engineering can “super-charge” your Lean efforts and make your programs successful even in highly-challenging situations and with very-demanding customers.

James Sutton’s passion is for unleashing the power and joy of human creativity in the development of systems. He is a chief software-systems architect whose designs and processes have consistently quadrupled productivity compared to company and industry norms, accompanied by a ten-times reduction in defects compared to normal. His book “Lean Software Strategies” won the 2007 Shingo Prize, which Business Week has called “The Nobel Prize of Manufacturing.” He is an INCOSE (International Council on Systems Engineering) CSEP (Certified Systems Engineering Professional), with a Master’s degree in Systems Engineering from Southern Methodist University. More recently, he joined with other recognized experts such as David Anderson, Dean Leffingwell, Alan Shalloway and Don Reinertsen in co-founding the Lean Software and Systems Consortium.

Dec
11

Just added:

Bohdan “Bo” W. Oppenheim will be speaking about “Lean Enablers for Systems Engineering“.

Lean Thinking is the paradigm that enabled Toyota to rise to the best and largest auto company in the world. The paradigm includes not only Lean manufacturing but also extraordinary effective Product Development and Systems Engineering, as well as a culture based on Respect for People.

Systems Engineering is regarded as a technically sound process but often burdened with waste and inefficiencies. Lean Systems Engineering is a new body of knowledge applying the wisdom of Lean Thinking to Systems Engineering. Systems Engineering and Lean have overlaps and differences, but both represent processes that evolved over time with the common goal of delivering product or system lifecycle value to the customer. Lean Systems Engineering represents synergy of the two, leading to superior systems engineering process.

Most emphatically, Lean Systems Engineering is not a re-packaged FBC or Acquisition Reform”. Lean Systems Engineering does not mean “less Systems Engineering”; it means more and better Systems Engineering, with better preparations, planning, front-loading, training, and more common sense, leading to better program execution.

Lean Enablers for Systems Engineering is a product designed by 14 experts from industry, academia, and U.S. and foreign governments, supported by 115+ strong Lean Systems Engineering Working Group of INCOSE. Lean Enablers are formulated as 194 “do’s” and “don’ts” of Systems Engineering practice focused on Mission Assurance/Product Success and elimination of waste.

The lecture will cover of three parts:

1. Description of the development process of Lean Enablers for SE
2. Presentation of a sample of 194 Lean Enablers organized into six Lean Principles: Value, Value Stream Mapping, Flow, Pull, Perfection, and People.
3. “Validation” of the Lean Enablers by surveys, and by benchmarking with recent studies by NASA and U.S. Government Accounting Office.

Bohdan “Bo” W. Oppenheim is the founder and Co-Chair of the Lean Systems Engineering Working Group of INCOSE, and leader of the development effort of Lean Enablers for Systems Engineering (scheduled to recive the Best INCOSE Product Award in 2010). He is a Professor of Mechanical and Systems Engineering and Graduate Director of Mechanical Engineering at LMU in Los Angeles, California. He serves as the local Coordinator of the Educational Network of the Lean Advancement Initiative consortium at MIT. He is on the Steering Committee of the Lean Education Academic Network. For seven years he served as a Director of the U.S. Department of Energy Industrial Assessment Center assessing 125 U.S. industrial plants for lean productivity. He consulted Boeing, Northrop Grumman, Raytheon, Airbus, EADS, Telekomunikacja Polska, and 50 other firms on Lean, Systems Engineering and Quality. He has $2.5 million in externally funded grants on his credit. He teaches graduate courses on Lean Systems Engineering, Lean Manufacturing, Lean Product Development, Lean Final Engineering, Lean Office, Lean Supply Chain, and Quality. He authored 25 journal papers.

He was born in Warsaw, Poland.

His engineering degrees include Ph.D. from Southampton, U.K., U.K. in Systems Dynamics; Engineer’s Degree from MIT in Ocean Systems; MS from Stevens Institute of Technology; and B.S. (equiv.) from Warsaw Technical University in Aeronautics. His professional experience spans space, naval, mechanical, software, and manufacturing industries.