Go to...

Lean Coffee Baltimore Topics for August

lean-coffee-aug

Lean Coffee Topics in dot-voted order

Lean Coffee is a structured, but agenda-less meeting. Participants gather, build an agenda, and begin talking. Conversations are directed and productive because the agenda for the meeting was democratically generated. We met at Mad City Coffee at 07:30 . We enjoyed an hour and a half of coffee and conversation.

August Topics

Distributed Teams

When everyone in your company is distributed, what are some ways you can stay connected?

Paired Programming

How do you sell paired programming to your organization? Management sees it as one for the price of two.

Test Driven Development

How exactly does it work?  We hear that it’s a good thing but why?

Method Turf Wars

Coaches and consultants get so passionate about the frameworks they promote. It used to be Waterfall against Agile.  Now it’s seemingly SAFe , Scrum at scale, enterprise Kanban and Lean… For the customers, do they really care? They just want stuff to work!

Meetups and Conferences

Have you been to any good meetups or conferences lately?  Do you know of any upcoming events?

Conversations

We had some really good conversations around the topics. Rather than bullet them out here, I’ll respond in the comments to encourage a little conversation.

About Derek Huether

I'm Vice President of Enterprise Engagements at LeadingAgile. I'm super focused on results. But I also take the hand waving out of organizational transformations. I come from a traditional PM background but I don't give points for stuff done behind the scenes. The only thing that counts is what you get done and delivered. Author of Zombie Project Management (available on Amazon)

2 Responses to “Lean Coffee Baltimore Topics for August”

  1. August 9, 2014 at 8:32 am

    I find you need to sell paired-programing to both your management and the team. I recognize that pairing is not easy. You should compare it to exercise. I wouldn’t suggest you run a marathon tomorrow, if you have not been training for it. Instead, just try to get out of the house and go for a walk. Something short. Pairing is no different. Don’t try to convince everyone to do 8 hours of pairing 5 days a week. It’s physically and mentally exhausting. Think of some of simple benefits like replacing formal weekly code reviews with an informal paired code review. Doesn’t that sound a little easier to sell?

  2. August 9, 2014 at 6:55 pm

    Check this out, to discuss the topic of distributed teams. How to run a team who never see each other.

Leave a Reply

Your email address will not be published. Required fields are marked *