Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as “post-mortems”) are only held at the end of the project—too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today. Now Esther and Diana show you the tools, tricks and tips you need to fix the problems you face on a software development project on an on-going basis. You’ll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes and how to scale these techniques up. You’ll learn how to deal with problems, and implement solutions effectively throughout the project—not just at the end. This book will help you: Design and run effective retrospectives Learn how to find and fix problems Find and reinforce team strengths Address people issues as well as technological Use tools and recipes proven in the real world With regular tune-ups, your team will hum like a precise, world-class orchestra.

Proven, 100% Practical Guidance for Making Scrum and Agile Work in Any Organization This is the definitive, realistic, actionable guide to starting fast with Scrum and agile–and then succeeding over the long haul. Leading agile consultant and practitioner Mike Cohn presents detailed recommendations, powerful tips, and real-world case studies drawn from his unparalleled experience helping hundreds of software organizations make Scrum and agile work. Succeeding with Agile is for pragmatic software professionals who want real answers to the most difficult challenges they face in implementing Scrum. Cohn covers every facet of the transition: getting started, helping individuals transition to new roles, structuring teams, scaling up, working with a distributed team, and finally, implementing effective metrics and continuous improvement. Throughout, Cohn presents “Things to Try Now” sections based on his most successful advice. Complementary “Objection” sections reproduce typical conversations with those resisting change and offer practical guidance for addressing their concerns. Coverage includes Practical ways to get started immediately–and “get good” fast Overcoming individual resistance to the changes Scrum requires Staffing Scrum projects and building effective teams Establishing “improvement communities” of people who are passionate about driving change Choosing which agile technical practices to use or experiment with Leading self-organizing teams Making the most of Scrum sprints, planning, and quality techniques Scaling Scrum to distributed, multiteam projects Using Scrum on projects with complex sequential processes or challenging compliance and governance requirements Understanding Scrum’s impact on HR, facilities, and project management Whether you've completed a few sprints or multiple agile projects and whatever your role–manager, developer, coach, ScrumMaster, product owner, analyst, team lead, or project lead–this book will help you succeed with your very next project. Then, it will help you go much further: It will help you transform your entire development organization.

In today's fast paced world, the internet can provide quick answers to personal questions. But when an individual raised by society to live, breathe and look at the world with female eyes transitions to male, some of the most enlightening, helpful and profound advice can only come in retrospect. Letter to my Brothers, features essays from respected transmen mentors who share the wisdom they wish they would have known at the beginning of their journey into manhood.

This is the digital copy of the printed booik (Copyright © 2001). With detailed scenarios, imaginative illustrations, and step-by-step instructions, consultant and speaker Norman L. Kerth guides readers through productive, empowering retrospectives of project performance. Whether your shop calls them postmortems or postpartums or something else, project retrospectives offer organizations a formal method for preserving the valuable lessons learned from the successes and failures of every project. These lessons and the changes identified by the community will foster stronger teams and savings on subsequent efforts. For a retrospective to be effective and successful, though, it needs to be safe. Kerth shows facilitators and participants how to defeat the fear of retribution and establish an air of mutual trust. One tool is Kerth's Prime Directive: Regardless of what we discover, we must understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand. Applying years of experience as a project retrospective facilitator for software organizations, Kerth reveals his secrets for managing the sensitive, often emotionally charged issues that arise as teams relive and learn from each project.

FunRetrospectives is a book with the necessary tools to develop the main element of continuous improvement: an effective, committed team! With several years working with agile teams, Paulo Caroli and Tainã Caetano Coimbra know there are two main ingredients to finding the path to success and continuous improvement. First, a team that is aligned and committed to the project. Second, a work environment that fosters collaboration, one in which everyone can openly reflect, debate, and learn. But how can we achieve that? Each person in a team brings a different life experience and perspective, and we know that a group of people doesn't become a team overnight. That's why the main purpose of this work is to offer the necessary activities and tools to make everyone comfortable, aligned, and ready to be part of the best possible experience. The authors have gathered years of experience in this book, offering simple and straightforward activities. There will always be ups and downs, but everything that happens is essential for the team's growth, and a fun, safe environment allows you to get the best out of every situation.

A rollicking guided tour of one extraordinary summer, when some of the most pivotal and freakishly coincidental stories all collided and changed the way we think about modern sports The summer of 1984 was a watershed moment in the birth of modern sports when the nation watched Michael Jordan grow from college basketball player to professional athlete and star. That summer also saw ESPN's rise to media dominance as the country's premier sports network and the first modern, commercialized, profitable Olympics. Magic Johnson and Larry Bird's rivalry raged, Martina Navratilova and John McEnroe reigned in tennis, and Hulk Hogan and Vince McMahon made pro wrestling a business, while Donald Trump pierced the national consciousness as a pro football team owner. It was an awakening in the sports world, a moment when sports began to morph into the market-savvy, sensationalized, moneyed, controversial, and wildly popular arena we know today. In the tradition of Bill Bryson's One Summer: America, 1927, L. Jon Wertheim captures these 90 seminal days against the backdrop of the nostalgia-soaked 1980s, to show that this was the year we collectively traded in our ratty Converses for a pair of sleek, heavily branded, ingeniously marketed Nikes. This was the year that sports went big-time.

Leonardo da Vinci (1452–1519) was one of the pre-eminent figures of the Italian Renaissance – he was also one of the most paradoxical. He spent an incredible amount of time writing notebooks, perhaps even more time than he ever held a brush, yet at the same time Leonardo was Renaissance culture’s most fanatical critic of the word. When Leonardo criticized writing he criticized it as an expert on words; when he was painting, writing remained in the back of his mind. In this book, Joost Keizer argues that the comparison between word and image fuelled Leonardo’s thought. The paradoxes at the heart of Leonardo’s ideas and practice also defined some of Renaissance culture’s central assumptions about culture and nature: that there is a look to script, that painting offered a path out of culture and back to nature, that the meaning of images emerged in comparison with words, and that the difference between image-making and writing also amounted to a difference in the experience of time.