Books

Unlock the untapped potential in your retrospectives. Discover the small changes that make big differences, drawn from almost 10 years of practical experience running retrospectives.

Dit is de handleiding voor Geike's arduino workshop.

This book teaches kids between 10 and 14 years old the basics of programming. You need a Mac computer to follow along with the examples. The examples use Terminal, nano, Ruby and irb. (Yes, I'm serious!) (Leanpub authors: The GitHub repository for this book is here, as an example!)

At present, the Experiential Learning series currently consists of four volumes. This first volume—Beginning—concerns getting started: starting using the experiential method, starting to design exercises, and getting a particular exercise off to a good start. It should be particularly helpful for short classes—a day or two, or even an hour or two—though it could be for starting to use experiential parts of a longer workshop consisting of both short and long experiential pieces as well as more traditional learning models.

A developer-friendly, practical and pragmatic guide to lightweight software architecture, technical leadership and the balance with agility.

In the mid-2010s, I watched teams drown under unrelenting backlogs, firefighting at every turn, and ceremonies that solved nothing. Holy Land Kanban tells the true story of how we sketched our first Kanban board in Israel—and discovered an alternative to “Agile By the Book.” In these pages you’ll learn how to:Make work visible, so no task lurks in shadowLimit WIP, freeing teams to finish rather than fragmentPull delivery, letting demand guide flow instead of pushing chaosEstablish feedback rhythms that drive real learningEvolve your system one experiment at a timeWhether you’re piloting dozens of AI projects, grappling with product-ops complexity, or simply seeking speed without spin, these timeless Kanban patterns will help you regain clarity, calm, and traction—today and for years to come.

Perhaps you've been a team manager, project manager, or possibly a business analyst. You may be a tester or even a software developer. Maybe you've been through a good number of projects and have experienced the highs of success and fallen in a few potholes along the way. Well, your team or organization has decided that they want to "go Agile" and you've been volun-told to be the ScrumMaster. Congratulations! You've had a few days of training, but now what?