Professional Documents
Culture Documents
59493
59493
https://ebookmass.com/product/radical-therapy-for-software-
development-teams-improving-software-development-practices-and-
team-dynamics-1st-edition-gregory-lind/
https://ebookmass.com/product/effective-software-development-for-
the-enterprise-beyond-domain-driven-design-software-architecture-
and-extreme-programming-1st-edition-tengiz-tutisani/
https://ebookmass.com/product/desire-as-belief-a-study-of-desire-
motivation-and-rationality-alex-gregory/
https://ebookmass.com/product/get-it-done-surprising-lessons-
from-the-science-of-motivation-ayelet-fishbach/
Agile Software Development : Trends, Challenges and
Applications 1st Edition Susheela Hooda
https://ebookmass.com/product/agile-software-development-trends-
challenges-and-applications-1st-edition-susheela-hooda/
https://ebookmass.com/product/agile-project-management-creating-
innovative-products-agile-software-development-series-2nd-
edition-ebook-pdf/
https://ebookmass.com/product/infection-control-and-management-
of-hazardous-materials-for-the-dental-team/
https://ebookmass.com/product/development-in-coastal-zones-and-
disaster-management-1st-ed-edition-amita-singh/
https://ebookmass.com/product/program-development-and-grant-
writing-in-occupational-therapy-making-the/
Radical Therapy
for Software
Development Teams
Lessons in Remote Team Management
and Positive Motivation
―
Gregory Lind · Maryna Mishchenko
Radical Therapy
for Software
Development Teams
Lessons in Remote Team
Management and Positive
Motivation
Gregory Lind
Maryna Mishchenko
Radical Therapy for Software Development Teams: Lessons in Remote
Team Management and Positive Motivation
v
Table of Contents
Review����������������������������������������������������������������������������������������������������������������33
Case Study 1: Team Dynamics and Communication�������������������������������������������34
Case Study 2: Growth Mindset����������������������������������������������������������������������������37
Best Practices for Maintaining a Positive Team Culture and
Encouraging a Growth Mindset���������������������������������������������������������������������38
Review����������������������������������������������������������������������������������������������������������������40
vi
Table of Contents
vii
Table of Contents
Best Practices����������������������������������������������������������������������������������������������110
Radical Process for Non-Software Products�����������������������������������������������������111
Step 1: Blueprint Integration������������������������������������������������������������������������111
Step 2: Daily Transparency Check-Ins���������������������������������������������������������112
Step 3: Continuous Improvement����������������������������������������������������������������112
Example�������������������������������������������������������������������������������������������������������112
Case Study 2������������������������������������������������������������������������������������������������113
Best Practices����������������������������������������������������������������������������������������������114
Review��������������������������������������������������������������������������������������������������������������115
viii
Table of Contents
ix
Table of Contents
Use Case: Transitioning Away from Agile – The Case of XYZ Corporation���������165
Background�������������������������������������������������������������������������������������������������165
Challenges Faced����������������������������������������������������������������������������������������165
The Decision to Move Away from Agile�������������������������������������������������������166
The Consequences��������������������������������������������������������������������������������������166
The Radical Therapy and Radical Transparency Solution����������������������������167
Review��������������������������������������������������������������������������������������������������������������171
x
Table of Contents
xi
Table of Contents
Index�������������������������������������������������������������������������������������������������235
xii
About the Authors
With over two decades of professional experience, Gregory Lind’s
career has traversed every facet of software development. He has delved
into realms ranging from web design, HTML/CSS, and DevOps to
back-end engineering, data administration, project management, and
team leadership. This journey culminated in assuming roles within the
C-Suite of developer-focused startups. While the majority of his tenure
has been dedicated to nonprofit and government-oriented startups,
his commitment to open source principles has remained unwavering.
Throughout his journey, he’s consistently championed open source
methodologies, tools, and values, integrating them into every phase of
his work.
xiii
CHAPTER 1
Introduction to Radical
Unveiling the Power of Radical Transparency
In the heart of the software and tech industry, a tale of two approaches
unfolds – one shrouded in secrecy and the other thriving on openness. The
first scenario paints a picture of a proprietary system where decisions were
made behind closed doors. A select few dictated the direction, withholding
insights from the very users, developers, and managers who would be
impacted. This confined strategy seemed enticing in theory, promising
control and exclusivity. Yet, as reality set in, the pitfalls emerged. Delays
occurred, errors crept in unnoticed, and the end product bore little
resemblance to what was needed.
This story of a closed environment resonates with experiences
witnessed across industries. From the catastrophic failure of the Theranos
scandal to the fiasco of Volkswagen’s emissions scandal, hidden intentions
often lead to disaster. A study by Transparency International showed that
companies with low transparency scores were more prone to unethical
behavior and financial misconduct (www.transparency.org/en/press/
ti-study-finds-the-worlds-biggest-companies-need-to-be-a-lot-
more-transpare). In software development, this lack of transparency can
result in software that fails to meet user needs, leading to dissatisfaction
and lost resources.
Contrast this with open source projects that embody the spirit of
collaboration and transparency. The Linux kernel, for instance, is an
exemplar of a collaborative approach, fostering innovation through open
dialogue and shared decision-making. Studies have shown that open
source software exhibits fewer defects and higher quality due to the
collective effort of developers worldwide. This approach also generates a
community around the project, and as long as the community is managed
with guidelines that allow for respectful collaboration and contribution,
the diversity of ideas can grow the project in ways the originators may have
never imagined.
What if we could take these lessons and apply them universally in
software development? What if we shifted from a secretive proprietary
model to one where transparency was the cornerstone – embracing open
source principles, freeing up communication, and building positive
internal and external communities? This book is your guide to unmasking
the potential of radical transparency in software development, for your
product teams and throughout your organization. By integrating feedback
loops, open communication, and inclusive decision-making, we can create
products that are not just functional, but adaptive and transformative.
Throughout these pages, we’ll explore real-world examples from
successful open source projects and internal or proprietary projects
being built with radical transparency. We’ll examine how companies that
practice transparency have cultivated positive cultures that breed trust and
innovation. We’ll dissect the shortcomings of proprietary approaches that
ignore transparency and reveal the practical steps to embrace openness
and collaboration. This book is an invitation to rewrite the narrative
of software development, product management, and organization
hierarchies and processes in general – one where every stakeholder’s voice
is heard, decisions are made collectively, and innovation is unbounded
by secrecy. Let’s embark on this journey to harness the power of radical
transparency, transforming how we build software and shaping the future
of our industry and many others.
2
Chapter 1 Introduction to Radical
Hello and welcome to radical therapy, a guide and tool to help you
bring some much-needed sunshine into the often cloudy world of software
development, cloud-native applications, and agile projects in general.
The ideas in here are not just for software, but that’s the “use case” we
will apply. Any team or set of teams that work from a business side and
technical side and have to interact can benefit from this book and the
learning within. What we hope you really get out of this is an idea of how to
keep you and the rest of your team, whatever role you play in it, motivated,
excited, and productive.
Now, you might be thinking: “Therapy? For software developers?
Isn’t that a bit... out there?” But hear me out. In today’s fast-paced and
constantly changing world of technology, it’s more important than ever to
take care of your mental health and well-being. And that’s where radical
therapy and more importantly radical transparency comes in. By fostering
a culture of openness, honesty, and positivity in your team, you can create
a work environment where everyone feels empowered to do their best
work and grow both personally and professionally. And the best part? You
don’t have to sacrifice creativity or innovation to do it. In fact, most teams
see a dramatic increase in productivity as well as increase in the longevity
of their teams through the retaining of talent.
In this book, we’ll explore the latest research and techniques from
the world of modern psychology and combine them with adaptive and
iterative processes and tools to help you build a team that’s both happy
and productive. We’ll talk about setting and meeting expectations,
fostering a growth mindset, and creating a self-managed development
process that allows for flexibility and creativity while still maintaining
structure. So buckle up, friends, and get ready for a radical journey to
software development nirvana.
Starting Chapter 1, we will introduce you to a pair of radical therapists;
they will be your guide through the tool as one therapist will be the skeptic
of the idea of transparency and positivity in the workplace and instead
want to stick with the old and tested methods. Meanwhile, the second
3
Chapter 1 Introduction to Radical
4
Chapter 1 Introduction to Radical
5
Chapter 1 Introduction to Radical
6
Chapter 1 Introduction to Radical
Daily Summaries
and Inclusive Contributions
Central to radical transparency is the practice of submitting daily
summaries and code contributions. At the close of each workday, team
members compile concise summaries of their accomplishments, struggles,
and code contributions. This ensures ongoing alignment, prevents
bottlenecks, and promotes collaboration.
This is different than the stand-up meeting – we focus on what we did
and where that work can be found. It’s about accountability, removing
blocks, and celebrating achievements. Kudos... Or congratulating your
team members is especially valued here.
Benefits of Daily Summaries:
7
Another random document with
no related content on Scribd:
Her hart did leape, and all her hart-strings tremble,
For sudden ioy, and secret feare withall,
And all her vitall powres with motion nimble,
To succour it, themselues gan there assemble,
That by the swift recourse of flushing blood
Right plaine appeard, though she it would dissemble,
And fayned still her former angry mood,
Thinking to hide the depth by troubling of the flood.
Tho when they had long time there taken rest, xlii
Sir Artegall, who all this while was bound
Vpon an hard aduenture yet in quest,
Fit time for him thence to depart it found,
To follow that, which he did long propound;
And vnto her his congee came to take.
But her therewith full sore displeasd he found,
And loth to leaue her late betrothed make,
Her dearest loue full loth so shortly to forsake.
FOOTNOTES:
[102] xvii 8 bathe 1609
[103] friend 1609
[104] xviii 8 strooke 1609
[105] xxiv 8 his om. 1609
[106] xxviii 6 He] Her 1596: Him conj. Upton
[107] certes 1596
[108] xxxi 5 withstand 1596
[109] xxxv 1 certes 1596
[110] xl 5 launc’t 1609
[111] xliv 4 in] on 1609
Cant. VII.
Nor[122] hedge, nor ditch, nor hill, nor dale she staies, xxii
But ouerleapes them all, like Robucke light,
And through the thickest makes her nighest waies;
And euermore when with regardfull sight
She looking backe, espies that griesly wight
Approching nigh, she gins to mend her pace,
And makes her feare a spur to hast her flight:
More swift then Myrrh’ or Daphne in her race,
Or any of the Thracian Nimphes in saluage chase.
Thence she them brought toward the place, where late xxxv
She left the gentle Squire with Amoret:
There she him found by that new louely mate,
Who lay the whiles in swoune, full sadly set,
From her faire eyes wiping the deawy wet,
Which softly stild, and kissing them atweene,
And handling soft the hurts, which she did get.
For of that Carle she sorely bruz’d had beene,
Als of his owne rash hand one wound was to be seene.
FOOTNOTES:
[112] Arg. 4 doole 1609
[113] i 1 darts 1609
[114] 8 launcedst 1609
[115] iv 6 snatcht vp from the ground 1609
[116] vi 3 reliques 1609
[117] x 9 ore-sight 1609
[118] xii 1 captiue Collier &c.
[119] xiii 3 doolefull 1609
[120] xviii 7 hither 1609
[121] xxi 2 th’ 1609
[122] xxii 1 Nor] For Collier
[123] xxv 1 Which] With 1596
[124] xxx 3 shewed, 1596
[125] xxxiii 1 Thenceforth 1596
[126] xxxiv 1 sad] said 1596
[127] xxxvi 8 faith 1596
[128] xxxvii 8 arrowes, 1596
[129] xxxviii 9 melancholy, 1596
[130] xli 6 neuer 1609
[131] xlv 9 wield 1609
[132] xlvi 3 likely 1609