Skip to main content

Shaping Great Teams on Bad Projects

Ever since I read "The World's Most Powerful Leadership Principle: Servant Leadership", I've felt invigorated about corporate software development. This book has made me change my mental models and perspectives on building great teams on bad projects.

One of the key things I learned from this book was that there is an undeniable difference between managers and leaders. As James C. Hunter says it best, "Management is what you do: planning, budgeting, estimating, organizing, problem solving, and strategizing. Leadership is who we are." Leadership can be defined as something simple as knowing how to inspire your teammates to become better than they think they are. Incidentally, I look at this much like the military. A skilled leader of a unit (usually a Captain or Major, I believe) has the commanding ability to inspire his men to become more courageous and more heroic while in the heat of battle.

"The Heat of Battle" can be applied to software Death March projects: you're in a situation where your team's confidence is deteriorating and their determination to finish the project is fading. From demanding clients, to features that aren't even possible to implement, to teammates giving up on you--these are all products of an environment where "all odds are against you". This is where the servant leadership characteristic needs to be implemented. It is a characteristic and discipline that needs to be practiced over time.

Ultimately, your team members need to understand that they are leaders as well. There is no "lead" the pack. Everyone puts in 100%. Externally to the unit (your production team), there are titles like "Lead Software Architect", "Lead Software Engineer", or "Project Manager"; however, internally they must all understand that they are all equal in value, opportunity, and mentorship. Everyone on the team has a voice and you have to hear them out.

Good luck and have fun,
Jaime Bueza

Jaime Bueza is a software developer in Vancouver, British Columbia, Canada. He has developed web applications for Nintendo, Starbucks, Electronic Arts, Ritchie Brothers, Kiwi Collections, Cox Communications and Microsoft. When he's not developing useful software that constantly evolves with business requirements, he's creating tutorial videos for aspiring front-end developers.
Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.

Cheers,
Jaime

World of Warcraft Ninjalist addon: version 0.1 coming along quite nicely

After toying around with more GUI related issues in World of Warcraft's API, I've decided to take a totally different direction. Originally when I architected this addon, I knew in my mind it would be a super simple Console application that a user could easily paste in a name and add it to the database; however, why stop there?

After discovering AceGUI, I can easily start developing UI components in no time! As of right now, I've got it saving data in between game sessions--the interesting part will come when I'll have to develop the web service that will parse the SavedVariable.lua, eliminate duplicate entries, as well as, do a huge merge between their copy and whats on the server's (per realm basis of course).

Here's a screen shot of the responses when adding new Ninjas to your list:
When a user clicks add after entering a name in the textbox, it'll go ahead and add that person to the ninjalist tagging the user's realm and current date/time. Someday, I…

Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:



Now, whenever you make a commit, it should show up like this in the log:



Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this



Want more emojis? check out the Emoji Mardown Cheatsheet!