Radical Therapy for GMB Development Team

Get Transparent and Communicate while Building Better Products

Get Started

Benefits of Radical Transparency in Software Development

Radical transparency is a management philosophy that advocates for complete openness and honesty in communication and decision-making.

In software development, radical transparency involves sharing all relevant information, including goals, metrics, feedback, and progress, with all team members in real-time. By doing so, teams can improve collaboration, build trust, foster accountability, enhance decision-making, and promote a culture of continuous improvement.

  • Encourages open communication and collaboration among team members
  • Builds trust and fosters a culture of honesty and accountability
  • Improves decision-making by providing more information and insights
  • Facilitates continuous improvement by identifying areas for growth and development

Positivity for Teams

  • Reduces conflicts and misunderstandings by making expectations clear and explicit
  • Increases productivity by eliminating unnecessary bureaucracy and delays
  • Enhances employee engagement and satisfaction by promoting transparency and fairness
  • Helps attract and retain top talent by demonstrating a commitment to openness and transparency
  • Encourages innovation and experimentation by creating a safe space for sharing ideas and feedback
Get Started!

2 Week Introductory Radical Lesson Plan!

Lesson Plan: Radical Transparency in Software Development

Week 1

  • Introduction to radical transparency in software development:
    In this session, we will discuss what radical transparency is and how it can benefit software development teams.
  • Benefits of frequent check-ins in GitHub and how to use them effectively:
    We will explore the advantages of using frequent check-ins in GitHub and best practices for using them effectively to enhance communication and collaboration.
  • How to provide positive feedback in pull requests and foster a culture of trust and openness:
    We will discuss the importance of positivity in pull requests and how it can help build trust and foster a culture of openness and accountability.
  • Hands-on practice in providing constructive feedback:
    In this session, we will practice providing constructive feedback in a safe and supportive environment.

Week 2

  • Overview of training katas and their role in developing new skills:
    We will discuss what training katas are and how they can be used to develop new skills.
  • How to set up and run training katas:
    We will cover the steps involved in setting up and running training katas for specific programming languages or tools.
  • Hands-on practice in running a training kata session:
    In this session, we will practice running a training kata session and receiving feedback from peers.

Summary

Overall, the lesson plan emphasizes the importance of transparency, communication, and collaboration in software development. By encouraging frequent check-ins, positivity in pull requests, and setting up training katas for new skills, teams can build trust, foster a culture of continuous improvement, and achieve better outcomes.

Bootcamp

By implementing these exercises and strategies, teams can improve their communication, collaboration, and overall effectiveness in software development. Radical transparency can help to create a more positive and productive work environment where team members feel valued and supported.

Frequent check-ins on GitHub

Not once a day, not at the end of the sprint... every time you finish a piece of functionality... check it in!

Positivity in pull requests

When reviewing each other's code, team members should focus on providing constructive feedback rather than pointing out mistakes. By adopting a positive attitude and framing feedback in a helpful way, teams can create a more supportive and collaborative work environment.

Setting up training katas for new skills

Kata exercises are short, focused programming challenges that help developers improve their skills in a particular area. By setting up regular kata sessions and inviting team members to participate, teams can create a culture of continuous learning and development.

Regular team retrospectives

Retrospectives are regular team meetings where team members reflect on their recent work and discuss ways to improve. By fostering an open and honest dialogue, teams can identify areas for improvement and work together to implement solutions.

Standups

The daily standup is an important communication tool, but it should also set the direction and mood for the day. With dealines looming and bugs to fix, an ice breaker that relaxes every one is a great way to start off. Tips: Remote teams use a standup bot instead of a meeting. Part times teams use what did you do last, what will you do next and what is blocking you.

Standup Jokes of the Day

Break the ice, and get the day started off right with a standup joke...not a standup joke like standup comedian... but well sort of... but for you know... your stand up.