Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I'll soon be assigned a few other programmers to guide through the development process and will be in the role of the git ("Integration Manager") and generally become a project manager.

Telling the truth, I've never done anything like that. I understand that such experience comes through practice, but it wouldn't harm to read about others' experience. Perhaps you know some book or set of articles or something of that kind about the project management?

I'm interested not only in how to separate tasks and control their execution, but also in the psychological part. Say, how to inspire the developers, keep a good atmosphere in the group and "reward" / "punish" when necessary, and how to do that correctly; how to point out that some solution is not good enough without offending the team member, etc, etc.

share|improve this question

We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.

migrated from stackoverflow.com Jun 7 '11 at 21:06

This question came from our site for professional and enthusiast programmers.

1 Answer 1

up vote 3 down vote accepted

The required reading in the Process and Project Management course at my university are Steve McConnell's Rapid Development: Taming Wild Software Schedules and Software Project Survival Guide. These books focus on the more "get things done" side.

Some classic texts on people-related issues in the software community include Fred Brooks' The Mythical Man-Month and DeMarco and Lister's Peopleware: Productive Projects and Teams.

Something that I have seen lacking is good communication skills, especially when it relates to solving problems and overcoming issues. Good books here are Difficult Conversations: How to Discuss What Matters Most (my top pick in this category), Crucial Conversations: Tools for Talking When Stakes Are High, and Crucial Confrontations: Tools for Resolving broken promises, violated expectations, and bad behavior. Although I've never read them, I've been told that the books Getting to Yes: Negotiating Agreement Without Giving In and Getting Past No are good reads - these two are on my wish list.

Beyond the process and people skills, you might want to also want to become familiar with the complete software lifecycle: software requirements, architecture, design, implementation, testing, and maintenance. There are a number of other questions and resources related to books on these topics. On top of these phases of the lifecycle, you'll probably want to become more familiar with the domain that you are working in to more effectively communicate outside of your team.

share|improve this answer
Thank you for such brief answer. Thanks to all the others for their info. One more question, since you've mentioned the "complete software lifecycle" then perhaps you could recommend something in that area? –  azerIO Jun 8 '11 at 13:25
@azerIO There are few books, and no great books, that cover it all. And there are other questions about resources for those topics - I would start there. Search for books and articles on those topics. Providing a list of books on all aspects of software engineering here would be a major scope creep on the question. –  Thomas Owens Jun 8 '11 at 13:35

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.