Tag Archives: Team Culture

What makes a meaningful standup update?

Hey there! I know it can be difficult to know what to say in standup. One of the most important things you can do to keep your team in the loop is to share a meaningful standup update on your progress. Think of it like a relay race – each team member needs to know where the baton is, how fast it’s moving, and whether there are any obstacles ahead.

When I enter standup and giving my update, I like to ponder: “What info can I give to the team that might be meaningful for a standup update?”

Tips for sharing meaningful standup updates

  1. Update the team on your current work status
    Let your team know how close you are to meeting milestones, deadlines, and if you’ve encountered any issues. For example, “I’m 85% complete with the License/phone selector for site settings and should have it ready for review by tomorrow morning.”
  2. Communicate any changes that may impact others
    Let your team know of any changes to your work that may impact or unblock the work of others. For example, “I’ve finished the API bits for both site and account phone/license, which should now unblock the UI stories for the rest of the team.”
  3. Customize your updates
    Tailor your updates to your team members’ interests and needs. For example, provide more details on a technical challenge for a team member who’s interested.
  4. Be proactive in sharing updates or asking questions
    Don’t wait for someone to ask for an update. For example, “I wrote up a bug I believe I noticed a bug in production, I would like to see if we should address it now or a future sprint.”
  5. Provide context
    Share not only what you’ve done but why you’ve done it. Providing context can help non-technical team members better understand the value it brings, and how it fits into the overall vision. For example, “I’ll be starting work on the date pickers, this is part of the new reporting view we’re building.”

Why do Good Standup Updates matter, you ask?

Well, here are a few reason:

  • Keep your team up-to-date
    Regular updates help everyone stay informed about the progress of the project and any potential roadblocks.
  • Identify and address issues early
    Sharing updates on any issues or challenges you’re facing can help your team address them early on, preventing them from becoming bigger problems down the line.
  • Foster team cohesiveness
    Sharing updates can help your team understand each other’s work and goals, leading to better communication and collaboration towards a shared vision.

“The single biggest problem in communication is the illusion that it has taken place.”

– George Bernard Shaw (1856 to 1950)

So, the next time you’re in a standup meeting, don’t just rattle off a list of tasks you completed – instead think of your standup updates like a baton in a relay race – an opportunity to keep everyone informed, stay on track, and work together to reach the finish line.

Ask yourself: “What info can I give to the team that might be meaningful for a standup update?” and you’ll build a strong team culture that values open communication and collaboration, leading to more productive and successful projects.

Become an Effective Software Engineering Manager – Book Review

Become an Effective Software Engineering Manager is an essential guide for learning to grow and lead engineers.

This is the single best book I’ve read on what it means to be a great Engineer Manger. It’s an enjoyable and honest read.

Become an Effective Software Engineering Manager Book Cover

Rating

(Higher is better, 5 is neutral)

  • Would I recommend? 10 / 10
  • Did I learn anything? 10 / 10
  • Did I learn anything I can apply? 9 / 10
  • High Information density? 8 / 10
  • Would I re-read? 9/10

Buy Become an Effective Software Engineering Manager on Amazon

Become an Effective Software Engineering Manager Overview

The author will take you on a journey from day one to being a central influencing helping your team be the effective and impactful.

The book is broken down into 3 major sections: Managing Yourself, Working with and Managing others, Working with Teams and the Organization at Large.

Who should read Become an Effective Software Engineering Manager?

Certainly every Engineering Manager and Head of Engineering. This could be a playbook for creating a philosophy around great management.

Senior Engineers who are considering Engineer Manager route or want to build empathy with an Engineer Manager’s role.

My main takeaways

Being organized is very key to being a great manager. Use your calendar, email, reminders, and notes effectively. Specifically automated reminders will give you super powers.

You have two options for leading: The Stick or The Carrot. The Stick driving everyone forward with pressure & deadlines. The Carrot by motivating & aligning on mission.

There is a hierarchy of needs in the workplace. First two are Physiological (pay & benefits) and Safety (job security & environment. These two we have control over as manager, but don’t lead to long term job satisfaction. The next three are Belonging, Esteem, and Self-actualization. As managers we can contribute to these fulfilling items by finding opportunities that align with a reports interests.

There tends to be two developer archetypes: Cathedra Builders and Bazaar Browsers. Those that want to go deep and be a subject master, building towards perfections; and later are those that desire for exciting new things and never want to be stagnant. Each have their space in an organization and both are motivated in their own ways. Don’t try to fit one in the others role for long if you can help it.

Delegation has a range of levels of oversight. From no oversight to showing another how to do a task. Closing the right level of delegation depends on the task and the individuals capabilities.

If you liked this book, next I’d recommend:

Going deeper on team culture: Elegant Problem
Going deeper on leading with positive impact: Multipliers
Going deeper on project management: Waltzing with Bears

Debugging Teams – Book Review

Debugging Teams is a short, clean, and to the point read. It’s a great book to pick up, read a page or two & set down and ponder. Every section speaks lightly, yet bluntly about team culture & being a great team member.

Debugging Teams Book Cover

Rating

(Higher is better, 5 is neutral)

  • Would I recommend? 9 / 10
  • Did I learn anything? 8 / 10
  • Did I learn anything I can apply? 7 / 10
  • High Information density? 8 / 10
  • Would I re-read? 7/10

Buy Debugging Teams on Amazon


Debugging Teams Overview

Debugging Teams speaks honestly and cuts to the chase. It provides practical advise with how to work with (and around) bad culture and defines what good culture looks like.

It reminds us that good team culture starts with ourselves. We have to be humble to grow ourselves to be an example of what good culture is.

Debugging Teams sets that bar of what that good team culture should looks like and thusly what bad culture looks like.

Who should read Debugging Teams?

Pretty much everyone! Specifically leadership, managers, and junior to senior devs.

I consider this essential reading for any of team member as an introduction to thinking about team culture.

My main takeaways

Culture is important from day 1, bad culture from one teammate infects an entire team and pushes away good talent. It’s hard & nearly impossible to override one toxic teammate with many good ones, it just doesn’t work.

Therefor don’t tolerate having the Brilliant Jerk on the team. They aren’t worth it. They set bad culture and diminish the team around them.

Be the example of the culture you’d like to see, be humble, you likely have faults as well. We need to be aware of our own ego.

If you liked this book, next I’d recommend:

Going deeper on team culture: Elegant Problem
Going deeper on leading with positive impact: Multipliers
Going deeper on project management: Waltzing with Bears
Going deeper on managing a team: Become an Effective Software Engineering Manager

Favorite Quotes

“Software development is a team sport”

“If you spend all your time working along, you’re increasing the risk of failure and cheating your potential for growth”

“Relationships always outlast projects”

“Understand the difference between constructive criticism of someones’ creative output and flat-out assaults against someone’s character. […] If you truly respect someone, you’ll be motivated to choose tactful, helpful phrasing.”

“Your self-worth shouldn’t be connected to the code you write – or any project you build.”

“When you stop learning, you get bored. It’s really easy to get addicted to being a leading player; but only by giving up some ego will you ever change directions and get exposed to new things. Be willing to learn as much as teach.”

“Admitting you’ve made a mistake […] is a way to increase your status over the long run.”

“A ‘strong culture’ is one that is open to change that improves it, yet is resistant to radical change that harms it”

pg 31

Get Together – Book Review

I rather enjoyed Get Together and recommend it often to my friends who find themselves leading communities. I’ve build several communities and indirectly followed some of the exact same patterns. Having this book as a guid would have been a huge help. Reading through it I’ve learned new ideas for forming strong communities.

Get Together Book Cover

Rating

(Higher is better, 5 is neutral)

  • Would I recommend? 8 / 10
  • Did I learn anything? 7 / 10
  • Did I learn anything I can apply? 7 / 10
  • High Information density? 6 / 10
  • Would I re-read? 8/10

Get Together on Amazon

Get Together Overview

There is a bit of a science to building strong thriving communities, and Get Together shares some of those patterns that can be implemented in nearly any scenario.

Get Together shares what they call the 3 phases of growing a community: Spark the Flame (Getting things started), Stoke the fire (Building strong community), Passing the torch (Empowering the next set of leaders)

Who should read Get Together?

Anyone who is either looking to, or already leading a group. Be it either social or in a work environment. If you are looking for ideas of how you might get your group off the ground or stoke your group to grow to the next level, this is a good read.

My main takeaways

Find core, excited people in your community and empower them to get involved and participating.

You can build a community about anything your passionate about, even a cloud fan group!

Make gatherings Purposeful, Participatory, and Repeatable.

Create a space to talk and provide prompts to keep conversation going.

Give members a sense of identity, giving tokens and ownership.

Empower the next set of leaders. You don’t need to lead forever.

If you liked this book, next I’d recommend

Building a multiplier team culture: Debugging Teams

Example of strong company culture: Creativity Inc.