Showing posts with label ProjectManagement. Show all posts
Showing posts with label ProjectManagement. Show all posts

Thursday, January 31, 2013

On leading teams

I recently saw a presentation that opened my eyes on some points I probably should have known about long time ago. For me it was a breakthrough, and I apologize I wasn't aware of them sooner.

First of all, regarding the question: "What is my top responsibility as a team lead? What should be the No. 1 in my TODO list?". The simple answer is:

Keep asking myself how my team has improved in the past interval: how my team has improved in becoming a team, how my team has improved in doing things, how my team has improved in becoming a super team, how each member of my team has improved himself/herself, how did I improve myself for my team, how did I improve myself for myself...

If I am not at least thinking about that, I am just a programmer with special attributions!

Secondly, I realized that nothing can improve out there in the comfort zone. If I'm leaving you in your comfort zone, and I stay in mine, we might be more comfortable with each other, but we won't in any way progress in anything.

So If I don't have the guts to challenge somebody or myself out of his/her/mine comfort zone, I am just a programmer with special attributions!

Thirdly, I realized that I can easily become an impediment for my team. Yes mister Scrum master, you can easily become an impediment for your team! If somebody comes to you complaining about the WiFi in the meeting room and you don't ask him "what will you do about it?" but just forward the question, you're on the right track in becoming impediment.

Fourthly, I realized that broken window theory doesn't apply just to failed unit tests but to any practice you would like to have in your team. Skip a code review once, and code review will become optional, skip a retrospective, and all the retrospectives will become optional or nice to have, just break the window and everybody will know it's save whatever they want.

So if you have an hour, enjoy the movie, it contains also other cool stuff: Code Leaders and Beautiful Teams

The guy's site is pretty helpful too: 5whys.com












Friday, July 17, 2009

Peopleware:Productive Projects and Teams: Book Review






The Book


Peopleware:Productive Projects and Teams by
Tom DeMarco and Timothy Lister.


The Review

Like any other Software Engineering bible, the book is present everywhere: as reference in a large number of technical books, as reference in various articles, mentioned by fellow programmers and project managers, with fragments quoted in blogs and read in group readings, everywhere!

'Teamicide' did it! For me, it was the drop that filled the glass: another term from the quoted book that well describe acts I see around me. Next week I had the book in my hands.

The book came at the right time: after being part of a large variety of teams, after the PMI Project Management course, after the CMMI training, after seeing the "Scrum" steps my corporation takes towards Agile adoption.

What did I want to learn?

More about growing super productive teams and teamicide: what glues the team, what can destroy it?

More about project management, DeMarco & Lister's views on software engineering and project management.


What did I learn?

Learn is not a good word here, realize - works better.

1. Realized why I disliked sets of measures that I saw put in place in the environments I was part of. Defensive management measure set: mistrust, the Big M. Methodology, Laetrile.

2. Without any study in process control theory, DeMarco and Lister reach the same set of conclusions as Schwaber and Beedle: the management of indeterministic processes through Big M. Methodologies is doomed to fail. Excellent examples and comparations in this book: work-to-rule australian strike analogies, etc.

3. Realized why my former manager seemed to me so lucky. Having a strong team knowing what to do, with good moral and good accomplishments, feeling superior to the neighboring "regular" teams, the best of the best, was not an accident. His "Open Kimono" management approach, together with his active involvement in recruitment and contract negotiation phases - simply gave the right results: a super-productive team!
The general perception though was that he did nothing, all the good things just came on - sad but true!

4. Coding Wars: their scope and success criterias. I want to organize a session in my current company : if a fishing contest can be organized by my company, why not a coding one!. Tested the waters around here and it seems that a lot of people are interested in the topic - maybe after hollidays (Octomber) - we will run the first coding marathon in Eastern Europe!

5. Hawthorn Effect: give your team small potatoes to play with, challange them, celebrate with them, life is prety boring otherwise. Did I also mention that their productivity will reach the sky?! No, I'm not creating another Laetrile - there are good chances that the productivity will raise a little, but the important aspect is that the fun is guaranteed.

6. We are not working on High Tech Projects, we are not working on High Tech Projects, we are not working High Tech at all: all our problems are sociological in nature! Will I remember this?!
Will you realize this?!


In Summary

Sometimes you are allowed to take decisions that will affect your working environment: hire, buy a training, adjust office space, choose between technologies, set personal objectives, ...

It's good to have this book read at that moment. You might not be aware of your mistakes at that time!

If you are annoyed by a set of measures you see in your envronment and you don't know why, try to find the explanation here! You might find here a Plain English explanation and at least you'll know why you are upset!

If you think that nothing can be done in your case or your organization, that death is comming, use this book as a shoulder to cry on or as an ally to change the world!

Hmmm, the good Summary - after re-reading the book. The first read was just drink from firehose!