Stefano, In many ways I agree with you, but I still believe that som summary information reported in a status file, along with a record of the decisions needed, made and outstanding, will help *you* to do the things you want to without frightening everyone else ;-)
If we can agree on a standard workflow/usage of JIRA I would prefer it over a status file to be committed in svn. Often I update JIRA when I have no other access than http and I can't commit so I use that spare time to update/reorganize JIRA.
I don't think the two things are really the same, and I don't think you would be expected to replace your use of JIRA with the status file, which is more (IMO) of a summary of what the plan is, than a detailed record of every task.
Briefly: I'm +1 to increase the usage of JIRA also for our roadmap/status tracking. -0 on the introduction of a status file in svn.
Ok, I'll take this on board. d --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
