One of the most important, yet also among the most neglected, misunderstood, and feared elements of Agile culture is Transparency. In many instances people simply pay lip service to the idea of openness, and in some cases people even work actively against it.

In reality, organizations can indeed quite easily foster a safe, transparent, and productive environment, and provide radiators to help make informed decisions. This contributes to happy, productive, and trust-based Agile teams (and therefore leads to better software and more satisfied customers).

So, how can we help make this happen? How can we remove the fears and worries associated with Transparency, and replace them with trust, safety, and confidence?

Join Sesh in a highly interactive session as he shares real-life examples, easy-to-apply practical tips, and secrets to help improve human aspects such as trust, teamwork, collaboration, and communication: All by making Transparency the centerpiece of team culture.


Outline/Structure of the Talk

 Transparency (5 minutes)

  • Definition
  • Clearing misconceptions

Role of Transparency in Agility (10 minutes)

  • Its place in Agility
  • What an "opaque" and closed team culture looks like
  • What an "open" and transparent team culture looks like
  • How to get to the Nirvana stage

Strengthening Agility and Trust by Promoting Transparency (15 minutes)

  • Why? Benefits and advantages
  • Who? Roles and responsibilities
  • How? Intangibles (culture, attitude, mindset, process) and tangibles (tools and technologies)

Practical Steps Towards Transparency (10 minutes)

  • Tips on encouraging and creating Transparency and Trust
  • How to create real-life/real-time radiators
  • How to generate meaningful and non-judgmental conversations
  • Call to action

Questions (5 minutes)

Learning Outcome

At the end of the session attendees will be able to

  • understand what transparency actually means in the context of Agility
  • make the case for, value, and promote a strong culture of transparency and trust
  • identify problems and issues proactively in their Agile teams
  • report data, status, and concerns in an open and fearless manner
  • work together to deliver world-class software

Target Audience

ScrumMasters; Managers; Team Leads; Product Owners

schedule Submitted 4 years ago

Public Feedback

comment Suggest improvements to the Speaker
  • Ellen Grove
    By Ellen Grove  ~  4 years ago
    reply Reply

    Hi Sheshadri

    I like the outline of your proposal.

    Can you elaborate a little more about the interactive aspects of your session? It's not clear from the outline or slides how the attendees will be involved.

    And do you have any video of any of your presentations?  Can you give me some idea of your speaking experience (besides the Rally conf)?



    • Seshadri Veeraraghavan
      By Seshadri Veeraraghavan  ~  4 years ago
      reply Reply

      Hi Ellen,

      Thank you very much for your response and for your questions; glad to hear you liked the outline of the proposal!

      Other than the very recent Rally talk, my previous experience includes presenting at Agile India 2015 just earlier this year (please see related link in my submission, reproduced here: It was received very well and I had several follow-up conversations with people that had questions on the topic and wanted to discuss it further. The recording (video) located at the bottom of the site above has poor audio quality due to a bad microphone but it gets better as the session goes on.

      At IHS I've conducted several workshops covering topics such as trust-building and cultural adjustments for Agile for teams ranging from 5 to 45 people and also have undertaken several training sessions on various Agile-related topics. I've conducted these sessions in Houston, Englewood (CO), Bengaluru, and just last week in Calgary and have received strongly positive reviews and feedback.

      All my sessions are typically quite interactive. I tend to involve the audience as much as possible by asking questions, opinions, views, and their experiences so it doesn't become a one-way knowledge transfer but in effect becomes effective knowledge sharing.

      Hope this helps, Ellen. Please let me know if you have any further questions.

      Best regards,