On Dec 21, 2007 10:45 PM, Roy Martin <[EMAIL PROTECTED]> wrote: *Project/Programmer Velocity* I read this quite some time ago in the extreme programmer series but never took it to heart... you should! Basically determine how many productive hours you get from you or your developers each week. If you don't know take what you think you do and divide it by three (in the book). Because you'll have a million other things come up. Then plan your milestones accordingly. review at the end of each one, and readjust your tickets (or stories) accordingly.
Sounds very SCRUM like; Do you practice SCRUM? Reason I ask is I've been looking for a tool that tracks Burn downs in a sprint and while Jira works (I am guessing Trac would work similar) I was wondering if there was a better tool or if Trac offers something better than Jira. I am mostly looking at the reporting side of things. Since according to my company SVN is just now mature enough I haven't used SVN/Trac on large projects so I very well could be missing large chunks of functionality in Trac. Adam Haskell --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
