This is a good question. First, one lifecycle clearly does not fit all. Teams find themselves in a unique situation: team members are unique individuals with their own skills and preferences for working, let alone the scaling/tailoring factors such as team size, geographic distribution, domain complexity, organizational culture, and so on which vary by team. Because teams find themselves in a wide variety of situations shouldn’t a framework such as DA support several lifecycles? Furthermore, just from the raging debates on various agile discussion forums, in agile user groups, at agile conferences, and even within organizations themselves it’s very easy to empirically observe that agile teams are in fact following different types of lifecycles.
This is a dynamic 3-day, high-impact, interactive workshop where participants will experience the fundamental concepts of Reliability Excellence in order to drive performance improvement efforts within your class is a learning process that begins with a clear understanding of the learning objectives, behavior change expectations and desired performance improvement results. Then you will learn the tools and processes required to develop, implement and sustain word-class maintenance and reliability programs.
Learn more about Reliability Excellence Fundamentals