Software Delivery Notebook

Tag: Culture

  • Westrum’s study of information flow

    Westrum's study of information flow
    The Software Delivery Notebook
    Westrum’s study of information flow
    Loading
    /

    Ron Westrum is famous for his classification of organizational culture, but he’s also done great work on hidden events, and information flow. This episode looks at Westrum’s study of information flow and it contains highly relevant lessons for all organizations, not just safety-critical industries.

    When information fails to flow, it stops the “safe and proper functioning of the organization,” and looking at the flow of information is a powerful indicator of how well the organization functions.

    The properties of great information are receiver-centric. Good information…

    1. Answers the questions the receiver needs answered
    2. Is timely
    3. Is presented in a way that makes it usable by the receiver

    This paper has a whole host of insights, explored through interesting real-world stories.

  • Work Is Water: Flow, Not Drowning

    Work Is Water: Flow, Not Drowning
    The Software Delivery Notebook
    Work Is Water: Flow, Not Drowning
    Loading
    /

    From the article Work Is Water on The New Stack.

    Modern work environments often overwhelm individuals with an endless stream of tasks, akin to a river flooding its banks. It suggests that attempting to rush work through only exacerbates the problem, leading to more interruptions and a feeling of being constantly submerged.

    Embrace a “flow” mentality inspired by natural waterways and find out how slowing down, continuous small-scale planning, and intentional decision-making is how you get things done.

  • Restorative practice for software teams

    Defining Restorative
    The Software Delivery Notebook
    Restorative practice for software teams
    Loading
    /

    Looks at the Defining Restorative paper from Ted Wachtel, founder of the International Institute for Restorative Practices (IIRP).

    The explores the historical evolution of restorative justice from ancient roots to modern applications and outlines a supporting framework and how it can be used in the context of software teams.

    It builds trust, fosters buy in, and reinforces that social capital.

  • Understanding transformational leadership

    Understanding transformational leadership
    The Software Delivery Notebook
    Understanding transformational leadership
    Loading
    /

    Find out what transformational leadership looks like and how it benefits work performance and employee wellbeing and satisfaction.

    Based on DORA’s research program, this episode looks at one of the most impactful capabilities you can bring to your software team, which is based on 5 qualities:

    • Vision: Having a clear concept of where the organization and the team are going and where they should be in five years.
    • Inspirational communication: Communicating in a way that inspires and motivates, particularly in uncertain or changing environments, and inspiring pride in being part of the team.
    • Intellectual stimulation: Challenging followers and the team to think about problems and basic assumptions in new ways.
    • Supportive leadership: Demonstrating care and consideration for followers’ personal needs and feelings.
    • Personal recognition: Praising and acknowledging achievement of goals and improvements in work quality, and personally complimenting outstanding work.

  • Improving developer experience

    Improving developer experience
    The Software Delivery Notebook
    Improving developer experience
    Loading
    /

    This paper on Psychological Affordances and their influence on DevEx improvement interventions from Catherine M. Hicks is a goldmine for understanding how to make a lasting difference to development teams.

    Find out what a “psychological affordance” is, how definitions of developer experience differ, and how to create the right conditions for success.

    For that code cleanup up tool to actually get used effectively, it’s not enough to just provide the tool. Leadership needs to actively signal that this work is valued, is visible, is important.

  • Developer productivity at Google

    Google Developer Productivity: Code Quality and Beyond
    The Software Delivery Notebook
    Developer productivity at Google
    Loading
    /

    A peek inside Google’s research on developer productivity, which looks at causal relationships to find what helps developers get stuff done (and what gets in the way).

    Looks at factors like shifting priorities, documentation, time spent in meetings, distributed and remote working, and technical debt.

    “Maybe it’s not just the presence or absence of documentation that matters, but the quality and purpose of that documentation.”

  • Changing organizational culture

    Changing organizational culture
    The Software Delivery Notebook
    Changing organizational culture
    Loading
    /

    Explores the culture of organizations using Westrum’s typology and looks at how you can change it using John Shook’s lessons from NUMMI.

    You’ll find out how to classify your culture and how to improve it to create positive change in your organization.

    “Generative cultures are all about open communication, sharing knowledge, and focussing on solutions not blame. Information flows freely, people feel safe speaking up, and problems are seen as opportunities to improve.”