Bøker av Katherine Radeka

"When Agile Gets Physical distills the right principles, derives methods to apply them, and in doing so represents a major milestone in defining the best practice of hardware product development." -Andrew Flint, Product Development Director, IMPINJWhy is it that so many hardware teams get stuck when using Agile? Why do they still endure long, slow loopbacks? Why do organizations waste valuable time and resources fixing problems in late development that could have been found earlier?Software and hardware teams face separate problems at different stages. But some Agile Software experts suggest that the necessary solutions are often the same. We've seen too many implementations of Agile tools and practices that just don't translate to physical products.The authors have personally had to untangle many physical product teams who used Agile in ways that slowed them down, caused rigidity and sacrificed the full potential of their outcome.If you want to get the speed, flexibility and responsiveness of agile principles without force-fitting a method that was designed to solve a different set of problems, this book is for you.When Agile Gets Physical reveals how you'll use the best parts of Agile to accelerate your time-to-market with proven methods, and:Why the common problems hardware teams have experienced for decades can easily be avoided.How you'll get a stronger product that beats your competition to market up to 50%+ faster by building a reusable library of resources every team member can understand.What Agile Software advocates are getting wrong about physical product development and why abandoning agile principles isn't the answer.How a simple reframing of important decisions improves efficiency, communication, and results without losing the "big picture view".If you feel like progress is too slow, your teams probably feel the same way. The research in this book pinpoint why this is, what changes to make and how hundreds of international companies using our framework detected problems earlier to get better outcomes later.Katherine and Kathy's combined experience in agile for physical product development will show the exact steps to take towards integrating your software and hardware teams more closely, and how to keep the benefits of agile without force-fitting the wrong methods or adapting them beyond recognition.Once you get a closer look, you'll be wondering why you weren't using this method from the start.What is Agile For Hardware?Agile for hardware means the ability to be fast, flexible and responsive as a product moves from idea to launch. As you explore an idea for a product, you learn new things that change the conceptualization of the product.While software engineers can easily make changes at any point in the process by writing new code, physical products are much harder to change once the team starts building prototypes.For a hardware team to be fast, flexible and responsive, they need to be aware of the Last Responsible Moments to make their most important decisions. You'll learn how you can leverage this concept to preserve flexibility, even in areas that seem too rigid to do this effectively.Who is this book for?This book is for anyone working on physical product development. That includes but is not limited to:Chief Technology OfficersVPs of Engineering, Product Development, Innovation or Research & DevelopmentProduct Development Project LeadersSystem Architects and other Technical LeadsScientists and EngineersOr anyone responsible for teams creating physical products.

Do your products take too long to get to market? The Rapid Learning Cycles framework is an approach to product development that has helped hundreds of teams get their products to market faster.When you can get your product into customers' hands faster, you see your vision brought to life sooner. You can beat any competition to market with your best ideas. You can shorten the time it takes before your company begins to earn money from your ideas. You can reduce development costs, making it easier for investors, executive teams and program sponsors to buy into your ideas. If your idea is meant to fail, it will fail faster, freeing you up to go on to your next idea. All along the way, you'll build knowledge that will accelerate your progress now, and speed up the teams that will develop the next product even more.The Rapid Learning Cycles framework was developed experientially, building on Katherine's work with four different companies in four different industries that all needed to get their best ideas to market faster. Then Katherine began teaching this framework to teams all over the world. She followed up with every early adopter team, and used her observations to continue to refine the framework into a flexible approach to help teams get tangible products to market faster.Agile is not enough for tangible products.Agile software development experts may say that hardware teams should "just use Agile" or "just use Scrum." But hardware teams have not had consistent success with this approach, because some of the assumptions of Agile Software Development don't apply to products that must obey the laws of physics, chemistry and biology.Software and service teams can roll out updates that impact current customers immediately, and decisions can be reversed if they don't work as expected. When your product requires a supply chain, production process and distribution network, you will make decisions that you will live with, as long as you have products in the field that are under warranty. Software can be built and re-built every day; hardware prototypes can take months, even with 3D printing and other rapid prototyping tools. In this environment, teams need to think beyond accelerating build activities with Agile.Rapid Learning Cycles is Agile for hardware and other tangible products.The Rapid Learning Cycles framework addresses the ways that product development gets slowed down:Instead of creating detailed plans that get instantly out of date, teams work in short cycles of learning that help them thrive in extreme uncertainty.Instead of locking down decisions too early and then being forced to live with them, teams pull learning forward and push decisions later to maintain flexibility and remove obstacles before they appear.Instead of wasting time and money on product builds that don't work, teams leverage modeling, rapid prototyping and other experimental methods to accelerate the learning they need to make good decisions that stick.The 2nd Edition expands upon the concepts in this book with more details on key framework elements like the Core Hypothesis, the Learning Cycles Plan and how to prioritize Knowledge Gaps. It includes major revisions, based on our field experience, to the chapters on structuring the learning cycle, metrics, program leadership and using Rapid Learning Cycles to accelerate a Lean Startup with many knowledge gaps to close. It captures the state-of-the-art best practices to help you get your best ideas to market faster.Register your book to gain access to Readers' Resources help you jump right into some experiments to help you test the Rapid Learning Cycles framework in your product development organization. The instructions are in the back of the book.

This book compiles the experiences of over 150 companies that have embraced the theories of Lean product development. It provides an integrated view of Lean as it is practiced inside successful companies today. Examples, case studies, and stories drawn from small, medium, and large companies in a variety of industries support concepts and provide opportunities for readers to see the concepts in action. Each chapter includes actionable recommendations to provide ideas on how to try the concepts out for themselves and their teams.