[Chicago] requirements tracking in python

Chris McAvoy chris.mcavoy at gmail.com
Thu Jan 24 17:32:10 CET 2008

Trac is pretty great.  You can get creative with tickets.  In general  
though, it sounds like your whole crew needs to evaluate your  
development methodologies...figure out what works, and stick with  
it.  That usually requires a bunch of buy in from a bunch of people  
who don't like to buy in, but if you get it all lined up, it might  
make things easier than finding a magical software package that fixes  

Look into "Scrum."


On Jan 24, 2008, at 10:22 AM, sheila miguez wrote:

> Does anyone here know of a tool in python for handling requirements  
> tracking?
> (I have deja vu, have I already asked this?)
> I think django would be a good fit, you could end up with a view for
> the requirements doc, and views for traceability reports (and so on
> and so forth, want to hear me babble ideas? scm integration would be
> really cool link data to the src code? tie in comment tags (in
> whatever language you are documenting))
> At work I am driven crazy by the mish-mash of ways people pass on
> requirements to me. I end up making charts on the wiki from their
> requirements to my srs to my model -- this does not scale!
> no, this is not overkill, yes it helps -- do you want a team to get to
> the integration phase of a project only to find that they forgot to
> implement a requirement?!
> arg.
> -- 
> sheila
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> http://mail.python.org/mailman/listinfo/chicago

More information about the Chicago mailing list