Jump to content

Project Management - software scheduling


Skeptical

Recommended Posts

How do you guys figure out the delivery schedule when managing a project? Do you sit down and write down every single feature/task, then estimate the number of hours for them all and enter them into the software?

 

I tried using Trac, and the problem is that I am forced to use due dates as opposed to # of hours needed to complete. I think the latter is better because programmers often jump around when developing software, and it's hard to decide way early on what date the start something and what date it should end.

 

Any ideas?

Link to comment
Share on other sites

Typically we do not assign a specific feature/task a due date.  Instead we roll these into releases. 

 

So release 0.2a might look like:

Feature: Update XML parser.  (Add namespace support)

Feature: Add client side form validation.

Bug fix #12

Bug fix #13

Bug fix #14

etc...

 

Release date 2/15/2007.

 

We have our own proprietary project management software.  But I hear that dot project is pretty decent as far as open source solutions go.

 

Best,

 

Patrick

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.