culture

  • Encouraging a Bring Your SELF to Work Day with your teams

    Most of us work in teams. We go to work and see the same folks each and every day. We check in when we fill our coffee mugs, and we offer a “see ya tomorrow” when we leave. In between, we work with them – either as a group, in pairs or quasi-independently with occasional interactions. We might spend more waking hours with these people then we do with our family and non-workplace friends.

    But how well do we know them?

    If you’re working with or on a team, you have a vested interest in getting to know each other. Doing so develops trust, openness, respect, courage and commitment – many of the values we prize in Scrum and Agile. So here’s an exercise that you might consider: throw a “Bring Your Self to Work” Day. (I’d seen this listed as a topic at an open space, but I wasn’t able to attend, so you’re stuck with my imagination.)

    Before you laugh it off and say “don’t we do this every day already?” or roll your eyes at a seemingly trite concept, hear me out. I’m not about to preach being fully invested in being 100% present in your own daily activities (though that’s a noble goal). Rather what I’m proposing is a team-based exercise, whether on-site or off.

    In fact, despite the name, you might opt to meet at a restaurant or other non-work location. Holding an event after working hours sounds ideal, but it could be hard to pull off if co-workers have their own family- or commute-based constraints. And given the choice of having the whole team participate vs. a convenient time for most of the team, I’d choose the former.

    Here are a few suggestions for pulling this off.

    Keep it Social – meeting at the office always carries connotations of work. Heck, even the word “meeting” is so charged that you might consider referring to the gathering by another name. If budgets allow, consider social activities such as bowling or karaoke – making sure, of course, that the activity is something that all are able to take part in. And even if getting out of the office isn’t feasible, try to find a space far enough away from your work area that there aren’t the normal distractions.

    Share a Meal – something we all have in common is the need to feed ourselves. Whether you and the team decide to brown bag it out at a picnic table or in a bright conference room (preferably with natural light), or you head to a food court or restaurant, the gesture of “breaking bread” together is powerful and commonly accepted. If you splurge and have food brought in (bonus points if it’s not pizza), odds of participation increase greatly 😉

    Start Conversations Small – setting things in motion with a firm demand for all to open themselves up completely is the quickest way to kill the mood. Instead, begin by asking small, basic questions like:

    • what movies are good this season?
    • what was your favorite thing to do as a kid?
    • what was the worst thing about school?
    • hobbies / books / interests / etc.

    You can be creative – more creative than I am – but the point is to get people talking about themselves, maybe even laughing with each other. When this happens, we start to find unexpected connections and create or reinforce our bonds.

    I’ve done this with just about all my teams, and my favorite questions usually relate to our childhoods. Living on the west coast, I find that these teams are so diverse in terms of where they’re from and when they grew up, so the stories from our early years are always filled with new things to learn. Many remarks of “Oh, I remember that/those!” pepper the conversations, and people really open up and respect others more.

    Ask a Keystone Question – if and when the team is comfortable with the conversation, I encourage you to ask a deeper and more meaningful question, something that gets to the heart of your SELF. It doesn’t have to be too deep or serious, but it should allow for each member to see that they’re truly part of a trusting group. Something along the lines of “what’s one thing you have (talent, interest, experience) that you haven’t told anyone at work?”  I’ve heard answers ranging from “I used to sing opera” and “I’ve always wanted to visit Nepal” to much more intimate stories of personal loss or achievement.

    Again, the point isn’t to put people on the spot and be too vulnerable, but to show that it’s safe to share with this group, to show a bit of our true selves. You can’t (and shouldn’t try to) force connections and respect, but these connections are meaningful and usually happen as a result of honest and open conversation.

    Treat the Team as a Family – after the day is over and we’re back in our work routines, it’s very important to keep these bonds alive. Treat your team as an extended family. You don’t have to bring up the stories that were shared, but try to keep that emotion and connection with your co-workers as often as possible. It enables stronger, more natural collaboration and clearer communication. When appropriate, celebrate individual achievements as a team and help each other out with personal goals by occasionally checking in.

    And don’t make this a once-a-year activity. Anytime the team changes adds (or loses) a member, or if the group needs a collective pick-me-up, break out the invitations to another “Bring Your Self to Work” Day.

  • 29. Frederic Laloux and Dr. Clare Graves Walk into a Bar

    Announcing the brand new Podcast Topic Index. Search and sort to find any topic discussed on our podcasts.


    Victor is once again joined by Dale Ellis (@theDigitalDale), Jason Kerney (@JasonKerney), Zach Bonaker (@ZachBonaker) and Garrett Borunda (LinkedIn) at the Cape Rey in Carlsbad for a lively morning of Agile and Coffee.

    In this episode, our Agile heroes discuss:

    Reach out to Vic (@AgileCoffee) and use the hashtag #tellAgileCoffee to interact with us on an upcoming episode.

    announcements:

  • 28. “Agile” Under the Microscope

    Victor is joined by Dale Ellis (@theDigitalDale), Jason Kerney (@JasonKerney), Zach Bonaker (@ZachBonaker) and Garrett Borunda (LinkedIn) at the Cape Rey in Carlsbad for a lively morning of Agile and Coffee.

    In this episode, our Agile heroes discuss:

    ACCUSWest 2015 archive at AgileLib.net, courtesy of Tobias Mayer

    Coming soon is Dr. Dave‘s 5 Saturdays program’s Train the Facilitators workshops: May 30th and June 6th. More info at 5Saturdays.org

    Reach out to Vic (@AgileCoffee) on Twitter and use the hashtag #tellAgileCoffee to interact with us on an upcoming episode.

  • 27. Putting Together an Agile Coach Camp

    To share an abundance of topics, Victor is joined by Dale Ellis (@theDigitalDale), Larry Lawhead (@LarryLawhead), Jon Jorgensen (@waterScrumBan) and Dr. Dave Cornelius (@DrCorneliusInfo) in the Irvine studio for a lively morning of Agile and Coffee.

    In this episode, our Agile heroes discuss:

    • A brief report on last month’s ACCUS West
    • Applying Agile to students
    • Hang the DJ
    • Can Agile practices change us psychologically?

    We’re at a crossroads, and you can help! Is this format working for you? How can we improve upon it? AND – what ideas do you have for recording the sessions over the interwebs? Would you like to join one? Let Vic know by twitter or email.

    Mark your calendars for Dr. Dave’s 5 Saturdays program’s Train the Facilitators workshops: May 30th and June 6th. More info at 5Saturdays.org

    Reach out to Vic (@AgileCoffee) on Twitter and use the hashtag #tellAgileCoffee to interact with us on an upcoming episode.

  • 23. We Discuss a Listener’s Topic!!

    Vic is joined by Dale Ellis (@thedigitaldale), Dr. Dave Cornelius (@DrCorneliusInfo) and Larry Lawhead (@LarryLawhead) for a lively morning of Agile and coffee.

    Today our heroes discuss the following topics:


    Want more? Visit our brand new forums on the AgileCoffee website.

    AgileGathering.com has the info about our upcoming Agile Coach Camp US West, April 10-12, 2015

  • 21. Death March Agile vs the ScrumBut

    For this episode, Vic is joined by Jon Jorgensen (@WaterScrumBan) and Dale Ellis (@thedigitaldale) for a lively morning of Agile and coffee.

    Today our heroes discuss the following topics:

    • Training vs Discovery – learning styles, immersive learning, guided discovery, peer stimulus
    • Positivity-resistant peeps – believe in your team, like attracts like
      • books: Joy, Inc by Richard Sheridan & Five Dysfunctions of a Team by Patrick Lencioni
    • Agile mechanisms without values – Deathmarch Agile, Scrumbut
    • DevOps, Docker, Agile – automated testing, microservices slidesvideos for DockerCon 2014

    Want more? Visit our brand new forums on the AgileCoffee website.

    BTW, have you gone to iTunes or Stitcher to give us a review? It takes so little time and would sure help us a lot. Thanks!

    Reach out to Victor (@AgileCoffee) on Twitter –  and use the hashtags #askAgileCoffee or #tellAgileCoffee to interact with us on an upcoming episode.

  • 10. Is Your Company Culture Killing You?

    Jon and Vic are joined by Dr. Dave Cornelius (@DrCorneliusInfo) in an undisclosed location for a lively morning of Agile and Coffee.

    In this episode, our Agile heroes discuss the following topics:

    1. Culture as the Silent Killer
    2. Deliver Fast
    3. Flex Training

    Reach out to Jon (@waterScrumBan) and Vic (@AgileCoffee) on Twitter –  and use the hashtags #askAgileCoffee or #tellAgileCoffee to interact with us on an upcoming episode.

  • 9. Starting a New Job as a Scrum Master

    Jon and Vic are joined by Dr. Dave Cornelius (@DrCorneliusInfo) and Brett Palmer (@Brett_Palmer) in an undisclosed location for a lively morning of Agile and Coffee.

    In this episode, our Agile heroes discuss the following topics:

    1. Wisdom of crowds
    2. Respect people
    3. First week on the job
    4. Training Conquest
    5. Coaching retreats / bootcamps

    Reach out to Jon (@waterScrumBan) and Vic (@AgileCoffee) on Twitter –  and use the hashtags #askAgileCoffee or #tellAgileCoffee to interact with us on an upcoming episode.

  • 6. Last ‘cast from Paradise Perks: Goodnight, Paradise – pt.1

    Fresh off their Scrum Day San Diego appearance, Jon and Vic are joined by Dr. Dave Cornelius (@DrCorneliusInfo) and Brett Palmer (@Brett_Palmer) for a lively morning of Agile and Coffee.

    It’s our last podcast from Paradise Perks in Irvine (alas, the institution has shuttered its doors), and this session (recorded on June 14th) is divided into three parts, all using the lean coffee format. In this episode, the Agile heroes discuss the following topics:

    1. Culture eats what? Key Man syndrome and amoeba hump reverts
    2. “Agile practies make me tired”
    3. Two new uses for Agile Coffee: afterglows and cold-calling

    Reach out to Jon (@waterScrumBan) and Vic (@AgileCoffee) on Twitter –  and use the hashtags #askAgileCoffee or #tellAgileCoffee to interact with us on an upcoming episode.

  • Scaling Me, Scaling You

    I just scheduled our next meetup and threw these two questions out:

    • How many teams is too many for one roving scrummaster?
    • How many members before a team is too large?

    What’s great is that the group can discuss / debate the question. Despite being in Scrum environments for over six years, I don’t have THE answer, but I DO have some opinions based on solid experiences.

    Without playing too much of my hand prior to the actual meet-up, here’s what I’m thinking:

    Roving ScrumMaster

    I was hired here at SendGrid as an Agile Coach tasked with leading the transformation and maintaining the learning and culture that goes along with that. One year into my job here, we had nine teams located between Anaheim (five), Boulder (three) and Romania (one); and for most of that year, each dev team provided its own scrum master. I and another coach (Stuart joined us in January, 2012) would coach the teams, paying much attention to the nine scrum masters.

    Since then, however, we’ve taken over the role of scrummaster for each team, allowing the devs to focus more fully on the design / development / testing work of the sprint. As you can imagine, Stu and I became busier than ever trying to juggle multiple teams and all the communications and dependencies that go along with this.

    Good to Great

    It’s been said that a good scrummaster can handle 3-4 teams, but a great scrummaster will insist on working with only one. I’m a firm believer in this model, but that wasn’t currently possible in the time frame I describe. Back then (early spring 2012) we were told that the organization would work to hire more scrummasters (and they did by mid-summer), but that in the meantime it was up to Stu and I to handle the responsibilities. The teams woul no longer provide their own scrummaster.

    Results varied. It started with both Stu and I taking four apiece. (The Romanian team was being “managed” by their own “scrum master”.) But Stu and I each had at least one team in Boulder (we’re in Anaheim), and that added complexity.

    Part of my role as Coach has been to spread Agile learnings throughout the organization, including up through management / leadership. I’ve worked with our VPs of Engineering (we’re on our third in two years) to understand the business situation and share my teams’ concerns. It comes down to values on both sides: commitment and focus for the teams and delivery and growth goals from business folks. These values are not contradictory, but neither are they perfectly aligned.

    Pizza Teams?

    Okay, dear readers, time for a pop quiz. What is the ideal size of a scrum team? If you answered “seven, plus or minus two”, congrats – that’s the magic number, also supported by the Scum Alliance and other leading Agile voices. The “two-pizza rule”, attributed to Jeff Bezos, states that no team should be so big that it cannot be fed with two pizzas. In my experiences, this jives with our successes.

    But can a team of only two devs make it work? (Lots of leftover pepperoni and cheese slices.) What about teams larger than nine? Can their scaffolding support them? We’ve hadt tw0 2-person teams, plus another (in Romania) that now brims with ten. I don’t even know what goes on a Romanian pizza.

    Anyway, these are some topics I hope to work through next week. In the meantime, I’m craving pepperoni.