Tag: management

Book: Esther Derby, Diana Larsen “Agile Retrospectives: Making Good Teams Great”

When I wrote about Alexey Krivitsky’s book Agile Retrospective Kickstarter a month ago, I mentioned that much of his work is based on the work of Esther Derby and Diana Larsen (as he openly acknowledges in his book). At that time, I also promised to write separately about the book by these women facilitators. So here I am, fulfilling that promise.

I read the book in English, although in 2017, it was also published in Russian by Dmitry Lazarev Publishing under the title “Agile Retrospectives: Turning Good Teams into Great Teams.”

Why do teams need retrospectives? I’ve already written about this in detail elsewhere, but here’s a brief reminder: retrospectives help teams learn from their mistakes and grow. Without them, no Agile methodology can operate at full capacity.

Esther and Diana explain how to make such meetings as productive as possible, drawing from their many years of experience and unique insights. It is in this book that they propose the five-stage format for retrospective meetings, which Alexey Krivitsky actively adopts and promotes in his own book.

Read more

Book: Alexey Savchenko “Game as a Business”

Alexey Savchenko is a name well-known in the Russian gaming community, and not just there. For some time, he officially held the position of Evangelist for the Unreal game engine, and even now, many still refer to Alexey by that title. Open in communication, always ready to help—a remarkable colleague. When he announced that he was planning to release a book about the gaming business, I had no doubt that it would be worth purchasing and reading.

Although Alexey is now primarily involved in working with business partners, he has had a long journey and knows game development from many different angles, including as the owner of his own studio. In his book Game as a Business, he set out to describe all aspects of the gaming industry and project development—”from dream to release,” as the subtitle states.

Alexey structured the book along this very path, beginning with “I have a dream… I want to make games.” From there, he meticulously yet accessibly explains what awaits an aspiring game developer on the road to creating their dream game and, ideally, achieving fame and fortune.

It is evident that the author has a deep understanding of the subject, and the book is both accessible to industry newcomers and engaging for professionals. Despite my many years in the gaming industry, I thoroughly enjoyed reading this book.

One of the most valuable aspects is how Alexey begins his advice by helping newcomers understand what lies behind their dream. Does the aspiring developer truly want to create their own game? Are they ready for the challenges this path entails? This guide is specifically for people who have decided to start their own business and are willing to risk their time, money, family relationships, and ambitions. Because if all you want is to make games, then joining an established studio is also an excellent path to consider.

Read more

Book: Alexey Krivitsky “Agile Retrospective Kickstarter”

Lately, I have been actively rereading various books and articles about Agile, and sometimes even exploring new material. In my opinion, Agile methodologies offer a lot of valuable practices, but one of the most useful ones is retrospectives—meetings where the team can look back, reflect on what has been done, analyze their experiences, and choose a few experiments to improve how things are done.

When people implement different Agile methodologies, they often forget that flexibility is not just about introducing daily stand-ups and breaking tasks into short sprints. It is fundamentally about learning from experience, adapting, and evolving. Without retrospectives, this does not work. That is precisely why retrospectives are so important. However, even these meetings can either be conducted properly and effectively or simply for the sake of formality (“because it is required”). For this reason, retrospectives are sometimes the subject of not only individual articles but even entire books.

Agile Retrospectives Kickstarter is one such book. Although it was written by a Russian-speaking author, Alexey Krivitsky, it was originally written in English, with the Russian version created later with the help of his colleagues.

The book itself is relatively short, just over 50 pages. The author, a practicing Agile coach, shares his experience in conducting retrospectives. However, he does not do this by providing an extensive set of examples or academic knowledge. Instead, he has compiled experiences from many sources into a highly condensed “retrospective cheat sheet,” offering a collection of possible exercises for conducting effective retrospective meetings. Alexey candidly admits from the outset that he did not invent any of these exercises (or at least does not remember inventing any) and even borrowed the methodology for breaking a meeting into several stages from other coaches. His contribution was to compile all of this into one relatively short guide that can be kept handy and used whenever preparing for a retrospective.

Read more

Book: Constantine Koptelov “Order in Chaos”

Sometimes even I fall for advertising, especially when it’s promoted in a reputable community. A few weeks ago, I came across an invitation to a free webinar on strategic sessions in a remote setting. It’s clear that the topic of remote work is being exploited by just about everyone these days, but I’m genuinely interested in the subject of strategic planning in general (and this is a good moment to remind everyone of the excellent book Good Strategy, Bad Strategy by Richard Rumelt). At the same time, I’ve spent many years building workflows with remote teams. So, this webinar touched on two areas of interest for me.

The webinar was hosted by Constantine Koptelov, someone I hadn’t heard of before. However, the hour-long presentation flew by almost unnoticed. I took several notes during the session and became so intrigued by the topic that I immediately purchased Constantine’s book, Order in Chaos: Objective and Key Results (OKR), which I’ll tell you about today.

Read more

Book: Henrik Kniberg “Scrum and XP from the Trenches”

Not long ago, on the last day of 2020, I wrote a review of the book Kanban and Scrum — Making the Most of Both, which I highly recommend to anyone interested in implementing Agile methodologies. However, this book was not the first by the author, Henrik Kniberg. His first book, published in 2007, also drew on his personal experience with agile methodologies and was titled Scrum and XP from the Trenches. Kniberg himself admits that he wrote this relatively short book over a single weekend, when he felt a strong urge to share his experiences with others.

This time, I won’t delve into the specifics of agile methodologies or why I’m singling out Kniberg’s books in particular, as I covered that in my previous review. Instead, I’ll briefly describe the book itself.

It’s also a very concise account of how he and his teams implemented various practices from Scrum and Extreme Programming in their work, with concrete examples and specific descriptions of the pros and cons. He’s not afraid to admit mistakes and point out what can go wrong. This is quite normal for agile methodologies, where much is governed by the motto “experiment and see what works best for your specific team.” The key is to frequently evaluate what’s been done (unlike older methodologies, where you might work for a year only to realize that you’ve been doing it wrong all along).

Read more

Book: Henrik Kniberg & Mattias Skarin “Kanban and Scrum — Making the Most of Both”

Since the beginning of the 21st century, the software development industry has undergone a tremendous number of changes. Nowadays, if you aren’t familiar with Agile methodologies and words like Kanban and Scrum leave you puzzled, chances are you might hear, “Out of the profession!”

Many people now see Agile methodologies as some kind of panacea for all problems. It’s like, “Back in the day, everyone worked with Waterfall, so things were slow, expensive, and unpredictable.” And if you suddenly switch to modern agile methodologies, happiness will immediately follow. But there is no cure-all, and any methodology requires proper application. In my experience, I haven’t seen a single company that fully applies all aspects of agile methodologies, and that’s generally fine. Agile is more about approaches and practices that each team should try, experiment with, and find what works best for them. Of course, there are certain principles that need to be followed.

I also know several companies (fairly large ones) that became disillusioned with Agile after trying the wrong approach or implementing it incorrectly. Personally, I’m not an avid fan of every methodology, but I’ve worked extensively with Agile, tried different approaches with teams, and continuously read about implementation practices—regardless of the old saying, it’s better to learn from others’ experience.

And I must say, there aren’t that many good books on the subject. Many authors provide rather superficial descriptions of techniques, while some are more focused on selling themselves as trainers than on helping companies understand what to do and how to do it. I can say that even some official certifications from the Agile community provide very superficial knowledge, and people then flaunt an official certificate without any real experience or, at times, even a basic understanding of how to work with the methodology.

Read more

Book: Maxim Dorofeev “The Jedi Way”

Three years ago, also in November, I wrote a review of Maxim Dorofeev’s book Jedi Techniques. In it, Maxim aimed to consolidate the essence of his time-management training. The book was very good, although it didn’t reinvent the wheel. Now, Maxim has released its follow-up, The Jedi Way.

However, calling it a sequel isn’t quite accurate. The new book is more a reflection on his earlier advice and a re-evaluation of his own methods. In this way, I actually liked it even more than the first.

As I mentioned, in the first book, Maxim compiled what he considered the best elements from numerous methods. He amusingly illustrated these concepts through the characters of a rational little person and a monkey, supposedly living in our heads and competing for our attention and time. These characters were borrowed from Tim Urban, and they fit seamlessly into the narrative.

However, these were largely well-known techniques and tips from other methods. Maxim simply brought them together and presented them in an appealing way.

Read more

Book: “Dealing with Difficult People”

Sometimes, I read individual articles from Harvard Business Review and even posted one on my blog (Misconceptions about Feedback). They also publish books that compile several articles on specific topics, organized into sub-series.

I decided to read one from the Emotional Intelligence series, titled Dealing with Difficult People, as this topic has interested me for several years. The book includes eight articles by seven authors. It’s not very thick (around 150 pages), and with a more modest font size, it would be even slimmer.

As the title and description suggest, the main theme of the book is dealing with difficult people, those under stress, and troublesome colleagues.

On one hand, it’s a collection of very short articles, and I wouldn’t say each one is revolutionary or highly valuable. On the other hand, it’s brief and to the point, unlike many business writers who often stretch a single idea over 300 pages.

Read more

Book: Susan Cain “Quiet”

I remember, during my childhood, there was a period when I became very interested in various tests, even collecting them in a separate notebook. It all started with Eysenck’s temperament test, where people were categorized as choleric, sanguine, melancholic, or phlegmatic. But Eysenck had another test, which, by the way, overlapped significantly with his temperament test—the introversion-extroversion test.

Who are introverts and extroverts? There are actually a huge number of scientific interpretations, and they sometimes differ in the details. But I’ll try to explain in simple terms.

Introverts are generally rather reserved people; they tend to focus on their inner world. They are usually not very sociable, feel uncomfortable in public or in large groups, and would prefer an evening with a book to a party.

Extroverts are the opposite of introverts 😉 They enjoy being in the spotlight, often becoming the life of the party, have a large number of friends and acquaintances, and are very sociable.

Read more

Book: Guy Kawasaki “Art of the Start 2.0”

Guy Kawasaki is described as “the boldest venture capitalist in Silicon Valley,” according to the cover of the Russian edition of his book The Art of the Start. In the original English version, however, no one characterizes him this way, nor did he include his own name in the book’s title—that was the work of the Russian publishers (in the Russian version, the book is titled Startup by Kawasaki.)

I can’t speak to his boldness, but Guy Kawasaki is best known for promoting the Macintosh brand at Apple in the 1980s, and he is credited with creating both the strategy and even the term “evangelism” (when a product gains passionate fans who promote and advertise it on your behalf—”evangelists”).

The book is often recommended as an excellent guide for those wanting to start their own business and for those seeking investors for such ventures. The book’s subtitle positions it as a collection of time-tested methods for launching any business.

Yes, the book consists of a series of relatively short chapters covering everything that might be needed to start a new business: from preparing a pitch and finding investors to hiring employees and working with customers.

Read more