I came across something disturbing recently and I want to get my two cents on the table because this isn’t the first time it’s come up. Several components in the project I’m assigned to store various configuration attributes in text files. Whether they’re name-value (properties) files or XML data, this is a good choice because it allows the customization of application behavior without code changes or redeployment … if you do it properly.
Continue reading
Tag Archives: architecture
Agile Project/Issue Management
The dev shop I manage really has no choice but to be agile. With lightning-fast changes in priorities, there’s no room for wholesale planning beyong a couple weeks out. What’s missing, however, are the tools to make this all work.
Sure we do the best we can with JIRA (a fantastic traditional bug tracker) and MS Project (a not-so-fantastic project management tool), but there doesn’t seem to be a good selection of tools to mimick an agile team.
I want creamy visual objects that represent features which can be moved between developers. I want a view of each developer’s workload for the next week, month and year. I want to know in 10sec what’s going out when, and which tasks are the limiting factor.
The closest thing I’ve found is VersionOne, and I haven’t had a chance to fully evaluate it yet. If anyone has any clues, I’m all ears.