views:

104

answers:

5

Recently I've been hired by a small startup. My managers are both new to software business and I was wondering if is there a good book to recommend them. The book must explain well how to manage various development methodologies (cascade, agile, scrum, etc..), version control, how to effectively track bugs and how to set up support and everything. They are not devs so I was wondering if is there something appropriate around.

Any ideas?

+1  A: 

Rapid Development by Steve McConnell.

alt text

This is a good high-level introduction to most of the topics you mentioned.

YWE
A: 

If your managers cannot -- right now -- actually develop software, you're going to struggle. Software development is remarkably hard. Someone who has not done it may never be able to understand how hard it is.

Even an experienced manager -- with out-of-date technical skills -- can become a liability. The Java programmers hate hearing a manager complaining that "When we did this in COBOL it only took two weeks. What's your problem?"

If your managers don't actually get the technology first, then the management will be largely impossible. Sorting out what developers are struggling with. Understanding a status report. Determining the consequences of an "in-scope/out-of-score" decision is very, very hard without some technical background.

I'd suggest that they learn to code, test, debug and put into production -- by themselves -- before turning them loose on staff.

I'd suggest you find an architect to work with them and make sure they can actually do development before they try to manage development.

You can hope the get up to speed, but your startup may fail before they learn enough.

You can absolutely assure they get up to speed by asking them to build something that actually works. Not talk about building it. Or review someone else's case study on building it. But build.

S.Lott
That's a bit hopeful, no? I've worked for a number of excellent managers who had no technical knowledge, but were very good managers. Management and development are two different things - you don't need to know how to develop to manage.
Paddy
@Paddy: You've been very lucky. I've never worked with a manager that (a) didn't get the technology and (b) succeeded. All the successful projects have been with managers who at least understood what was really going on.
S.Lott
@S Lott - What you need is somebody good at handling all the requests from outside who is prepared to trust his/her technical staff to not screw them over. It's a two way street. Conversely, I've yet to meet a developer turned manager who is really good at that.
Paddy
I had a discussion with the director of HR for a Fortune 100 company in the USA who was in charge of a software project for a while, and she noted that technical people tended to make poor managers because the skills behind solving people problems are different from technical problems. I don't think your'e wrong, though, about the technology - it's important, especially in a startup where the lines of communication are so short, it's probably critical that you have the tech knowledge among the upper level staff. Cuz a fortune-100 company != a startup. So I guess I agree.
sheepsimulator
Also, I don't think that because someone is technical, they _can't_ be managers. There are folks where that works. But it's hard(er) to find.
sheepsimulator
Your answer points out many true things. But you don't seem to understand that THIS IS THE SITUATION. We can't hire others and hey... HAVE YOU HAVE SEEN A MANAGER OF A BIG COMPANY being able to code? Where have you been working? You don't even recommend a book. Thumb down for you.
gotch4
People that only say the situation is wrong and don't actually propose much, like you do, make me freak out. I would never hire somebody like you.
gotch4
@gotch4: I thought I proposed a very specific thing to build management skills. I suggested that the managers actually build something so that they would know what software development was about. It sounded very, very specific to me. What more should I have said?
S.Lott
@gotch4: "HAVE YOU HAVE SEEN A MANAGER OF A BIG COMPANY being able to code?" Yes. Not well. But they could code and they already know what software development was. They would fail a number of quality checks, but they could develop something that worked. They understood the pain and complexity.
S.Lott
A: 

I would recommend "Software Engineering" by I. Sommerville (selected chapters of course). http://books.google.com/books?id=fIJQAAAAMAAJ

@S. Lott: it might be hard, but not impossible.

bsuv
+1  A: 

If they're new to software, I'd recommend The Mythical Man-Month by Brooks, and Peopleware by de Marco and Lister. They don't cover what you're asking for, but understanding what's in those books is much more important for a software manager than the details of the software process. Besides, they're short and easy to read.

David Thornley
+1  A: 

The Software Project Survival Guide by Steve McConnell. It's basically a trimmed down version of Rapid Development (bullet points instead of paragraphs), so he might get through it a little easier. That being said, Rapid Development is still a good suggestion.

Dorrene Brown

related questions