This book helps participants in agile software development environments learn to become leaders. Facilitative leaders should be at every level of the organization, from individual contributor to informal team leader to managers of all stripes -- it takes much focus and intentionality from senior organizational leaders, who have special obligations in creating successful lean and agile development environments. But, beyond the principles of facilitative leadership for agility, People over Process provides tips and demonstrative scenes for the more important and common software meetings: architecture simulations, project planning, team configurations, retrospectives, and more. The author fully illustrates the principles and shares proven techniques for the most important leadership events in agile projects. While this book focuses on facilitating extraordinarily well-prepared meetings, it serves as a metaphor for leadership more broadly. The leader's obligation to help their team make rigorous fact-based decisions; to gain broad input and have participants aligned on the outcomes and next steps; and to do so in an efficient way that respects the time of the participants is as relevant to every-day leadership activity as it is to conducting meetings. The author mixes background and explanation with demonstration -- in this case, the story of an agile project at the fictitious Pacifica Bank. The scenario constructed at Pacifica illustrates the concepts of effective leadership and productive workplace environments. The book concentrates on the flow of software from understanding what is needed through design, development, testing, and deployment. Essentially, the author provides a simple and powerful model of leadership, examples, and tips. This is not a cookbook on how to lead -- It is a set of principles and examples. All leaders must find their own way for their team, their organization, and their unique challenges.

This business parable reviews two different systems development projects. One project was an abject, expensive failure, while the other succeeded in creating a major new revenue stream, bringing in new customers. By reviewing the tales of these two systems, readers will develop a better understanding of what works and what doesn t when it comes to the leadership and action steps required to reinvent a company s procedures to get in step with the times.

CEO Evan Nogelmeyer discovers to his dismay that in today s business world, technology is not just for technologists. But does he discover this soon enough and once he does, does he have the tools and the business savvy he needs to stave off disaster? Evan and his team are all well-intentioned, successful business leaders with advanced degrees and backgrounds in marketing and business. But, without technical backgrounds, do they have what it takes to manage the technology overhaul so critical to the very survival of their company and the future of their own careers?

A Tale of Two Systems: Lean and Agile Software Development for Business Leaders reviews two fictional systems development projects: Cremins United and Troubled Real Estate Information Management, both launched at the imaginary Cremins Corporation. Cremins is a venerable printing company that must transform itself to survive in the Internet age. One project proves to be an abject and expensive failure, while the other succeeds in creating a major new revenue stream and solving important customer needs. Contrasting the methods employed in a traditional, process-centric 'waterfall' approach, with a lean and agile-inspired approach, this book provides business leaders with a tangible understanding of why lean thinking is so well-suited to contemporary environments requiring flexibility, speed, and the input of specialized knowledge.

At the conclusion of the two tales, author Michael Levine articulates a series of conclusions and principles based on Lean Product Development, Agile, and his 25 years of experience in business systems development.

While the tales told and the companies and employees that inhabit them are pure fiction, the lessons to be learned are very real and very applicable in today s highly competitive market, where victory goes time and time again to the lean and the agile.

This book helps participants in agile software development environments learn to become leaders. Facilitative leaders should be at every level of the organization, from individual contributor to informal team leader to managers of all stripes -- it takes much focus and intentionality from senior organizational leaders, who have special obligations in creating successful lean and agile development environments. But, beyond the principles of facilitative leadership for agility, People over Process provides tips and demonstrative scenes for the more important and common software meetings: architecture simulations, project planning, team configurations, retrospectives, and more. The author fully illustrates the principles and shares proven techniques for the most important leadership events in agile projects. While this book focuses on facilitating extraordinarily well-prepared meetings, it serves as a metaphor for leadership more broadly. The leader's obligation to help their team make rigorous fact-based decisions; to gain broad input and have participants aligned on the outcomes and next steps; and to do so in an efficient way that respects the time of the participants is as relevant to every-day leadership activity as it is to conducting meetings. The author mixes background and explanation with demonstration -- in this case, the story of an agile project at the fictitious Pacifica Bank. The scenario constructed at Pacifica illustrates the concepts of effective leadership and productive workplace environments. The book concentrates on the flow of software from understanding what is needed through design, development, testing, and deployment. Essentially, the author provides a simple and powerful model of leadership, examples, and tips. This is not a cookbook on how to lead -- It is a set of principles and examples. All leaders must find their own way for their team, their organization, and their unique challenges.

There are many books that seek to explain Lean and Agile software that offer theory, techniques, and examples. Michael Levine's first book, A Tale of Two Systems, is one of the best, synthesizing Lean manufacturing and product development with agile software concepts in an engaging business novel. However, there has been precious little practical guidance for those seeking to change existing organizations to become Lean and Agile, until now. Mr. Levine has followed the successful approach of A Tale of Two Systems, telling two simultaneous intertwined and contrasting stories, to bring organizational transformation to life. Mary O'Connell and James "Wes" Wesleyan, recently engaged to be married, share a commitment to Lean and Agile Software. They have recently become leaders in two very different companies - one, stuck in a slow-moving, unresponsive, process-driven quagmire of a software culture; the other, struggling through the chaos of a sales-driven, process-less swirl. Together with their wise mentor, Neville Roberts, they identify two approaches to making needed changes: Drive People (a top-down approach focused on processes and tools), and People Driven (an enablement approach focused on people and organizations). Mary and Wes evaluate their situations and choose approaches that best fit for them, and the transformations commence. A Tale of Two Transformations differs from many information technology books by grappling with all the complexities of our organizations: the people, the politics, the financials, the processes - in short, the culture from which our Lean and Agile journeys must begin. The change model presented in the flow of the stories is generally applicable, and can help anyone thinking about how to improve their organization.