How do I manage a small dev team with a large number of small projects
-
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.
Am in a similar postion, currently we are using this dotproject, covers 90% of our management requirements and is open source.
-
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.
hehe! i don`t know
-
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.
http://www.redmine.org It's a true multi-user Project Management System, it integrates bug and task tracking, versioning and integration with code repository. It features time tracking, wiki project documentation, mailing, reporting, many plugins such as Requirements Management, Risk Management, Peer Code Review, etc.... oh, it's FOSS... I'm surprised nobody mentioned Redmine (so far)... Eric