If you’re already in a position where you are managing developer(s) and or designer(s), then you are probably already acting as a project manager in some capacity and so are familiar with some of the tools and processes I’m going to talk about. I’d like to expand on some concepts that you have already started to lay the groundwork for.
And for the individuals who don’t have any kind of formal project management layer in place in your design/dev processes, I’d like to suggest that you add on. It’s not as easy or as clear-cut, but I believe will provide many important benefits to your sanity, as well as the end product you deliver to your clients.
Asking the right questions. I think that project management starts with asking the right questions.Asking the right questions. The nature of our work as consultants is that everything is very custom. We’re not making cheesburgers or pre-manufactured homes, so there is always an element of re-inventing the wheel. However, to the degree that we can encapsulate our experience with certain prototypes of common projects and common problems and solutions, we will be able to effectively and easily roll out project after project without major bugs, client miscommunications, or other headaches.
I suggest that you start working on a list of common questions for your client. They will inevitably come to you with some kind of vague question or problem that needs to be solved, and it is your job to turn that into a very specific project spec. You’re not going to remember all the issues or gotchas you’ve ever run into in every project, especially in the moment that you’re discussing this project with your client, so it’s important to have a reference to help you out. By asking them the right questions about their project, you are well on your way to scoping a well-defined project that you will be very likely to complete to their satisfaction.
Priorities. Let’s assume that you have a fairly well-defined project scope at this point and you are now beginning to delve into the details and painful minutia that inevitably comprise every project you’ll ever work on. It’s important to note here that every project has a project manager! You may not see yourself as that, but I can guarantee you your client probably does - there are of course exceptions especially if you find yourself working with larger agencies. However, your client is expecting you to properly detail the scope even if they’re vague, follow up with them even if they are lagging behind on their deliverables, and ensure the overall quality of the project. That, my friend, is project management.
There is a form tool for tracking the priorities and dependencies in a project called a gantt chart. This can be overkill for smaller projects. However, you will need some technique to line up all the various tasks that comprise your project, both action items for the client, and those for yourself, and figure out the dependencies for these. Basically, you need to make sure you have everything you’ll need to complete the project up front! And that is easier said than done!
Follow-up. One of the next important pieces of the puzzle is continuing to follow up with the client to ensure they are getting you everything you need - I find that many times this comes down to approvals. It’s unbelievable how much time you can actually spend hunting down an “OK looks good” from a client. So you will need to be dilligent, because the client will somehow always magically expect you to do this - even though you could say it’s probly not strictly speaking in your job description. ![]()
Popularity: 12% [?]
5 Responses
Chaitanya Sagar
April 2nd, 2008 at 12:24 am
1Programmer’s mind, this blog is fabulous. You are doing a good thing by focussing on topics that elevate a programmer into a project manager and a consultant. Good luck.
Charles Adler
April 2nd, 2008 at 12:42 pm
2Kalen, great starter post on Project Management. I’ve spent the better part of 10 years as a Designer & Strategist working with a variety of Project Managers. As with any role, it’s down to the individual, but you’ve definitely found the common traits that define what makes a good project manager.
The most identifiable to me, and honestly, most critical, now as a client, and previously as a consultant, is follow-up. Keep communication going constantly, and keep your clients and your team on their toes. Never get into a situation in which the client (or team) is approaching you asking what is going on or what to do. The moment that happens, you’ve failed.
I’ve always professed that the role of the project manager is to keep the team heading in the right direction. A Shepard you might say (I’ve heard Project Management described as “herding cats”, which can be so true at times). But beyond that, a cheerleader, keeping the team motivated.
Some of the very best project managers I’ve worked with have brought some mix of these traits to their job.
kalen_jordan
April 2nd, 2008 at 9:08 pm
3Charles, really appreciate your seasoned insight on this topic. Absolutely agree, when the client starts wondering what’s going on, its a huge red flag. And while its easy to justify a hundred ways why they should know where things are at, or why they need to be better at getting their deliverables to you, etc. - the bottom line is that *you* need to take responsibility and make sure it gets done.
Tactical Tips for Managing Your Subcontractors by Programmer’s MInd
April 3rd, 2008 at 9:23 pm
4[…] them to be available whenever you need them. They should do their best to be available, but you are the project manager - you need to plan for worst […]
Video Summary for Saturday, April 5, 2008 by Programmer’s MInd
April 5th, 2008 at 3:27 pm
5[…] The Role of Project Management […]
RSS feed for comments on this post · TrackBack URI
Leave a reply
Nuggest of Wisdom
Let's Socialize
Visit our sponsors!
VIDEO: Week in Review
Week of Sat, April 5 in Review
Categories
Blogroll
Most Popular in April, 2008
Programmer’s Mind is proudly powered by WordPress - BloggingPro theme by: Design Disease