Things We Don’t Do in Our Team

Photo by Anwaar Ali on Unsplash

We don’t have long-lived branches other than master

We don’t assign developers to repositories

We don’t have User Acceptance Testing (UAT)

We don’t blame

We don’t write a wall of text on cards

We don’t do hours long sprint planning

We don’t tell the team what to do

We don’t ignore technical debt

We also don’t over-bake our technical solutions

We don’t split people into Operation and Innovation

Software Engineer | Tech Lead | Engineering Manager jamiewen00.gitbook.io/tech-lead-handbook/

Love podcasts or audiobooks? Learn on the go with our new app.

Right Before Your Eyes

How You Can Grow Wisdom in Your Organisation

Use A Shareable Calendar For Your Team’s Best Success

Going “All In” with Your Word

Why Kiyosaki’s advice on “Work to Learn, Don’t Work for Money” in Rich Dad Poor Dad is worth your…

Interesting vs. right is a false choice

My Resignation Interview

These are the Only 3 Tactics You Need to Win at Any Negotiation

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jamie Wen

Jamie Wen

Software Engineer | Tech Lead | Engineering Manager jamiewen00.gitbook.io/tech-lead-handbook/

More from Medium

5 steps to create an effective hiring plan for your product teams (Part II)

Challenges of Software Modernization

software upgrade

Our Engineering Values

We Need Fifty Words for Engineering Velocity