Mark A. Richman wrote: > What techniques and tools do you use to manage your feature backlogs? > It could be as low tech as a post-it note, TODO file in your Rails > project tree, or as high tech as a web-based collaborative tool.
Requests from the onsite customer go on index cards pinned to a cork board. In some circles this is an industry Best Practice. Using a more advanced system, such as a website, represents a failure to simplify your process. Each card has a difficulty rating in the corner - 1 to 5, representing ideal half-days. That makes estimating a week's worth of stories easier. I keep all engineering tasks in TODOs in my source, because that's usually where I am keyboarding when I think of them. I use this format: TODO must do this before this iteration (or downgrade to CONSIDER) CONSIDER this potential code improvement awaits activation energy FEATURE the client said to do this, and it should get an index card REVIEW I made a decision that I need the client to review STORYTEST this stretch of code would make for some good Cucumbering I have a rake task which searches for those - rake todo, rake feature, etc, and I frequently run this and burn-down the count of outstanding items. -- Phlip --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
