Re:Poor Man’s Agile: Scrum in 5 Simple Steps
by tomelders on Wednesday March 20, 2013 @08:32AM
(#5406800)
When I raise my objections to the crappy tool (Jira in this particular case), I'm greeted with an avalanche about how it's the best tool for Agile.
I absolutely can pin it on the agile community, because if you take the Agile argument away from them, they're left defending a crappy tool with no arguments at all.
Re:Poor Man’s Agile: Scrum in 5 Simple Steps
by Bjartr on Wednesday March 20, 2013 @10:30AM
(#5407434)
As a person using Jira daily in a, fortunately well done, agile environment. I must say I can see how, when used with all the bells and whistles, strictly-enforced-workflow this and work-log that, it would be unbearable, the worst interpretation of Agile used to justify creating a sacrosanct "process" and going against the very core "people over process".
As a bug-tracker shoehorned into doing double duty as a Kanban board, does Jira have rough edges? Sure.
However, used as a slightly more feature-full variant of Trello, as a wall of virtual sticky-notes, as a way to help see if the team improves over time like it should, it's pretty useful.
The moment it becomes an impediment it, well, is an impediment, and should be dealt with accordingly.
Ignoring that though, I'd say, if anything, Agile promotes using simple tools like wallboards (physical wallboards, with physical cards). I don't really think you can pin using a bad tool on the Agile community when they largely prefer not to use these tools in the first place.