How do I manage a small dev team with a large number of small projects
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
You need something like Trac or TFS.
xacc.ide
IronScheme - 1.0 RC 1 - out now!
((λ (x) `(,x ',x)) '(λ (x) `(,x ',x))) The Scheme Programming Language – Fourth Edition -
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
John Oxley wrote:
4. Is there a bug tracking system that is *quick* to setup new projects in?
We use BugTracker.net[^] which can handle many projects and yes you can link subversion revisions to bug fixes (although we don't so I can't comment on how well it works, but it is a feature). Although you have to be an admin on the system to create a new project. You can assign bugs to individuals, and there are custom views that show things like "only open bugs assigned to me". Although it does support "tasks" and allotting time to those "tasks" I suspect you would be better off with a more dedicated project management system for this part of your management. I believe something like TFS might combine all of this into one but it's expensive. (and you're already using subversion)
John Oxley wrote:
5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project?
I'd say it's somewhere in the middle. A new project requires a XML node in the config.xml file with the project details, the location of the build script, test scripts, etc. A change to the config.xml does require a service restart (there is supposed to be a workaround by placing the config.xml source control and in it's own project that triggers a restart every time it changes - but it doesn't seem to work all the time for us). If you have a standard template for a ccnet project, I suppose it's just a quick copy paste and a change of the details. In theory, as it's all nice readable XML, you could write a little GUI app that managed it.
Simon
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
TFS seems to be an excellent fit. The only question is the price of TFS. It is pretty expensive.
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
- Keep a log of who has what tasks, the expected duration and notes about delays/problems. 2) Allocate new work to the person with the least on at anytime, this will hopefully allow for over-runs to be minimised. 3) Use Unit Billing. If a Worker has 8 hours work a day, then that is 32 Quarter hour units. Each person keeps a schedule of how long the spend on each account. There is allowances for Admin time and meetings etc, but always attempt at least 75% billable. Remember that 1 minute into a 15 min period is chargable at 15 mins! 4) Pass - But a weekly gathering and general forum where problems are discussed is useful. 5) Pass. Also... 6) Have a Bonus Scheme that when someone completes in early and under budget they get points. As each person hits their 100 points (or whatever), there is a company booze and curry. 7) Motivate by praise rather than fear, more productive. 8) Never promise more than you know you can deliver, and if you have to, then charge more. 9) Delegate!!!!!!! 10) See 9 especially when it is something complicated. Pick the expert in that particular area. 11) encourage staff to converse about each others projects, they may be room for self help, or both may be doing a similar thing. Double the charge for the same amount of work! Hope this helps
------------------------------------ To eat well in England, you should have a breakfast three times a day. W. Somerset Maugham 1925
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
Team System seems to be precisely what you need, particularly if you combine it with the Scrum For Team System process template... 3 x caveats 1: Very Expensive - though the investment WILL be returned. 2: An absolute PIG to set up...I can't stress this enough - READ AND FOLLOW the docs...yes, that means read before you try anything! It's not just a "double click an exe and next next next" type deal... 3: Can be a pig to administer, and the tools / platform don't exactly help. Have to say though, I absolutely LOVE VSTS - it's turned us from a fairly haphazard company into more of a streamlined Dev Factory...
C# has already designed away most of the tedium of C++.
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
Take a look at unfuddle. There is a free plan to let you get the feel of it, and you can scale up from there. Very cheap, as these things go. It supports subversion and git.
Best wishes, Hans
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
It's been a while (about 20 years) but one of the best tools I've used for managing multiple small projects was called WBS. Although you don't bill for new development, you do have to keep track of what it costs to do each job just to ensure that your license fees are in line with reality. Work Breakdown Structure uses job numbers to track hours spent on a project, and used correctly, helps to track what each part of the job actually costs in manhours. It does require some up front effort on your part, however. Someone has to take the initiative to break each job into parts and assign each part a number, ie: 123.456.001 Conceptual Design (customer 123, project 456, task 001) 123.456.002 Detail Design (task 002) 123.456.003 Module Testing (task 003) 123.456.004 Integration (task 004) 123.456.005 Validation (task 005) and so on. You can simplify it by keeping track of customers and the project numbers assigned to them separately with a spreadsheet, or expand it to identify and track smaller bits of the project. Project workers report the time spent on each task via time sheets - no need to get too anal on this, 15 to 30 minute increments is probably fine enough detail for your use. Each task should be allocated a number of manhours to complete based on past experience, and prgress can be reported by manhours consumed, or estimated time to complete, reported at intervals that are appropriate for the task. Over time, this data will be useful in improving your estimating skills, as you review variances between estimated and actual manhours for each task. A spreadsheet that lists each worker and the hours spent on each task will be useful for determining who is doing what and for which jobs. Another that shows percent completion for each task will be useful for determining when each project will be complete. These values can be acumulated into the customer/job spreadsheet for reporting status to customers and internal management. Assigning tasks to individuals is more complex, as the jobs need to be matched to employee skills. That is a judgement call on your part - critical to success, and impossible to teach. Good luck, especially if your have employees who love doing tasks that they have no talent for doing. Bug tracking is simple; keep a folder for each module and put little slips of paper in it describing each bug. Write "Fixed" on the slip when the problem is solved. As for fancy tools to make it easier, I've used several, and none are worth a damn. They make pretty pictures and repor
-
TFS seems to be an excellent fit. The only question is the price of TFS. It is pretty expensive.
I'd be surprised at anyone who uses TFS and actually pays for it. I bet the majority of people who use it have an MS partnership or some other deal where they get the software for free. Most of what it does is available in free tools - the main thing you get with TFS is better integration.
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
Hmmm...this might help: http://www.ayanova.com Then again it might not, but I do know people using it in conjunction with svn for that kind of scenario.
"Creating your own blog is about as easy as creating your own urine, and you're about as likely to find someone else interested in it." -- Lore Sjöberg
-
I'd recommend this myself, sewtting up projects is easy, and the newreporting at least looks fancy. I don't know how it handles 50 something projects, though.
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server -
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
We used EZ-Task at my last job. It's web-based.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
Take a look at OnTime by Axosoft. It's a great tool for exactly what ypu're doing. Single user is free.
Everything makes sense in someone's mind
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
Oh you only need TFS 2010 that's it
-
Take a look at OnTime by Axosoft. It's a great tool for exactly what ypu're doing. Single user is free.
Everything makes sense in someone's mind
It's funny that you should mention it here. I checked it out and on their website, the first option in the drop down box for "How did you hear about AxoSoft?" is "CodeProject". But the name does seem familiar so I guess their have an advertisement deal with CP.
-
Take a look at OnTime by Axosoft. It's a great tool for exactly what ypu're doing. Single user is free.
Everything makes sense in someone's mind
Yep, i second OnTime. Compare editions: http://www.axosoft.com/ontime/try_ontime_free[^] There is an limited feature Express Edition which is free as well as the single-user-free Professional Edition. If you are moving to medium enterprise though, a few hundred bucks shouldn't be a problem for the full version.
-
Oh you only need TFS 2010 that's it
try www.SigmaProDraconis.com they say they can do it for about $150 but i couldnt set it up.
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
Open source vTigerCRM + Add On Module for project management (lean and mean for small teams: project name, customer + operations/task list - assign to whomever, let them enter progress. Done Deal. Free, open source, change it if you need to. dotProject is awesome also but has almost too much for a team not wanting to get bogged in admin stuff to much. Works for us - 14 consultants strong, lots of projects, tasks, itty bitty ones, spread out (multiple folks participating) etc... If you need version control etc - take notice of the other posts - svn is decent.. but for the project management bits: accountability is our main thing "Who is doing what? Is it done yet?" are the main questions asked around here. --Jason
Know way too many languages... master of none!
-
I'm running a dev team of 4 (me included) that is in a somewhat unusual situation. We have a large number of active projects (~50). However the projects are generally fairly small, i.e. 3 weeks from start to finish. We use SVN for source control and currently store all notes, bugs etc in text files in a /doc directory of the svn project. To keep track of the projects and what we're all working on, we have a shared spreadsheet with Client, Project, Developer etc. All the projects are maintained, bug fixes and feature requests do come up, but we're coping at the moment. Our company is going through the transition from small business where everyone knows what everyone else is doing up to a medium enterprise where we need structure in order to know what is going on. Since I've been moved from lead developer to Manager (capital M important) the challenges I'm facing (management and technical) are: 1. Who is doing what and when will it be done? 2. Who is giving us work and how do I allocate it? 3. How do I keep track of billing the work to our clients? Dev time for new products is not chargeable because there is a license fee. Bug fixes are not chargeable, but feature requests are on either a Time and Materials or whatever I feel like. 4. Is there a bug tracking system that is *quick* to setup new projects in? Preferably one that I can link commits from subversion into. 5. I haven't looked at CruiseControl or the like, but is it quick and easy to setup a new project? I haven't been able to find anything on how to manage a team in these circumstances. Can anyone here help me blunder a little less disastrously and slightly more quickly through the management responsibilities that come up on a day to day basis.
Dalek Dave gave you some good advice and probably more important than which software to use for testing, although that is critic to your development process. You situation sounds very similar to one I was in 5 or so years ago... I was also the owner of the business so had a vested interest in coming in on time, budget, etc, etc... Ask yourself how important you are to the development team and development process and more importantly can the team do without you and your skills. If you are critical to the development team and enjoy development then dont bother taking on all the project management yourself. Hire a specialised project manager who does this for a living and work closesly with him from a technical perspective. If this is not an option then you can remove yourself as part of the development team, in terms of billing, in your forecasts since managing projects and clients (especially clients) is a full time (and then some) job. If on the other hand you are happy to move into this type of role (which I did and went back 2 yrs later) then hire yourself another lead developer or hand over lead tech to someone in the team who can handle it and hire another developer (you can then deal with him to keep yourself in teh loop). By all means do not try and do both especially if you growing an moving into more projects. This can only lead to proejct failure or/and unhappy clients because you didnt make them feel wanted.. I guess I didnt answer some of your questions but if you hire a project manager who specilises in development projects he will be able to give you more information relevent to your situation since he will be able to analyse your current state.. Best of luck!!!
-
I'd be surprised at anyone who uses TFS and actually pays for it. I bet the majority of people who use it have an MS partnership or some other deal where they get the software for free. Most of what it does is available in free tools - the main thing you get with TFS is better integration.