4 ms·
Wow. I hate JIRA but this article gets it completely backwards. Having small-scale tickets that you actually finish is the very essence of agile - limiting work
by lmm 8y ago
Wow. I hate JIRA but this article gets it completely backwards. Having small-scale tickets that you actually finish is the very essence of agile - limiting work in progress, defining "what done looks like" in a customer-facing way for tasks that each last at most two weeks. Ignoring the "wider vision" is the best way to produce software that actually solves people's problems instead of beautiful n-tier architecture that doesn't do anything anyone wanted.
JIRA is heavy and slow - it's model of limited transitions is fundamentally flawed, encouraging micromanagement and making mistakes hard to undo. But a lightweight board that you push tickets through - the famous "kanban" - is a great way to develop software (I've had a lot of success with Trello, though I fear it's only a matter of time before Atlassian bloats it into JIRAness).
- jimnotgym 8y agoI agree with you about Trello, but even better than that is paper-cards on a wall. Trello adds unlimited wall space and a distributed wall. If you don't have lots of remote workers, and the wall is big enough, then use it. There is something wonderfully tactile about chatting in front of a real kanban wall when working out priorities. At the next checkpoint/sprint meeting, you can physically add cards to your backlog. Physically push things up the priority list. I love it! I like 5×3 index cards better than post-it notes..
- KaiserPro 8y agoThe problem with trello is linking tickets intelligently is hard. The concept of epic/subtasks is missing. So if a ticket becomes to big, and you want to keep the history while breaking it up, requires a boat load of copy/paste. Also, there is a trend to have a physical board with tickets, as well as a trello board. This was fashionable amongst the scrum masters at previous large employer. It was universally hates as we had to spend loads of time playing with physical cards, then try and copy the state into the ticketing system. Its was annoying and a massive waste of time for everyone. Especially as it didn't encourage people to write the work they've done on the ticket, to allow it to be taken up by someone new.
- jimnotgym 8y ago> Also, there is a trend to have a physical board with tickets, as well as a trello board. Oh no! This sounds like a horrible idea! Two sources of truth, everybody trying to avoid the work of syncing them. Eek. > The problem with trello is linking tickets intelligently is hard. One way is to break any sizeable task onto it's own board. Just note on the card that it has been moved to a board of it's own. There is a logical team>board structure for this. Then you have a master board with the main building blocks on it, and then sub boards with tasks/stories on them. It is no panacea, but it can work
- Wowfunhappy 8y ago> One way is to break any sizeable task onto it's own board. Just note on the card that it has been moved to a board of it's own. There is a logical team>board structure for this. Then you have a master board with the main building blocks on it, and then sub boards with tasks/stories on them. It is no panacea, but it can work We've experimented with this type of thing in my company. In practice, we found that having multiple boards for a single project is just a bit too much to keep track of. I could see this working if Trello made it easy to quickly move between boards. This could be something as simple as a breadcrumb style path: Grandparent Board > Parent Board > Child Board, or something to that effect. Or maybe that would overcomplicate Trello, I'm not sure.
- markmark 8y agoCool, I work remotely, can you point a webcam at your wall of cards please? Also remember to record your tactile chats in front of the wall so the rest of the remote team can hear them.
- geocar 8y ago> Having small-scale tickets that you actually finish is the very essence of agile Bollocks. The "highest priority is to satisfy the customer through early and continuous delivery of valuable software." Not tickets, small or otherwise. Not tasks. It has nothing to do with two-weeks. > Ignoring the "wider vision" is the best way to produce software that actually solves people's problems I have no idea what you could possibly mean by this. Every time I've ever seen a modular development that isolates developers from the business (or from each other), I've seen brittle software, and that's assuming they get done at all. > But a lightweight board that you push tickets through - the famous "kanban" - is a great way to develop software (I've had a lot of success with Trello, though I fear it's only a matter of time before Atlassian bloats it into JIRAness). Listen, if software helps you, then great, but if your whole life is "pushing tickets", you're not doing Agile. It doesn't matter if you're using Jira or Jello. https://agilemanifesto.org/principles.html https://agilemanifesto.org/principles.html
- Klinky 8y agoThe problem with Agile is that no one is doing True Agile™, because no one can agree on what True Agile™ is.
- tootie 8y agoJIRA and Scrum are great ways to facilitate agile development but it's not bidirectional. I usually push rigid Scrum on teams if I think they lack discipline or experience. Follow the textbook until you understand why. When I'm working with smart veteran devs who know exactly why and how agile works, we can afford to be more freewheeling. I think agile is fundamentally simple. The essence is the continual improvement. How that translates into a working process (like when do I write tests and who updated the docs) are going to vary project to project.
- dvtrn 8y agoDave Thomas himself declared Agile dead a few years ago, but offers up what I think is a better definition https://www.youtube.com/watch?v=a-BOSpxYJ9M https://www.youtube.com/watch?v=a-BOSpxYJ9M
- alfalfasprout 8y agoThere's a middle ground between shipping a bunch of features and beautiful architecture that does nothing. At the end of the day, spending heavy up front time on designing great, flexible architecture lets you iterate much more quickly to ship the features people want.
- lmm 8y ago> At the end of the day, spending heavy up front time on designing great, flexible architecture lets you iterate much more quickly to ship the features people want. Not my experience. The most important way to get flexible architecture is simplicity - not having things you don't need. More often than not, architecture designed for some kind of flexibility up front turns out to impede flexibility in a different direction (which was actually what was needed) where a more naive design would have been fine.
- deleted 8y ago[deleted]
- BerislavLopac 8y agoMy favourite "agile Jira" is https://clubhouse.io/ https://clubhouse.io/
- neon_electro 8y agoWhat do you like and/or hate about it? My company is considering migrating away from Trello and I'd like to arm myself with as much information as possible on this topic.
- BerislavLopac 8y agoIt's basically a simplified Jira, with a strong focus on software development support and just the right amount of customizability.
- crwalker 8y agoJira also has the least consistent UX of any SaaS product I've used (Skype may be a close second).
- PeterisP 8y agoWhat I see in this article is a point that there's a discrepancy between goals and tasks needed to achieve these goals. If you're using JIRA for both planning features and measuring work hours spent (which many organizations are) then this brings some trouble - in an agile sprint, it makes all sense to plan that you'll do features A, B and C this week and get to D and E next week; however, it may be that by the end of the week you've spent 4 hours each to finish A, B and C and 20 hours on an infrastructure task (that's mostly done but not yet) that's needed not only for A and C but also for the next week's tasks. The detail level and task breakdown which is appropriate for planning which features you'll prioritize and do for a sprint may not be a good task breakdown for actually assigning sub-tasks for people, looking at their progress/status during a sprint, and mapping particular commits or hours worked to them. JIRA common practices sort of force those things to be the same, which may be considered harmful.
- temporallobe 8y agoI sort of agree with you but I love JIRA. Tbe problem really lies in the way people use it. It’s just another tool, and it can be used any way your organization deems necessary. Unfortunately, most orgs tend to make a religion out of it, and the Agile process becomes bastardized by abusing JIRA. Just by observation, I have concluded that management loves JIRA precisely because it allows them to micromanage (“hey Temporallobe, how are you coming with story XY-5678? I see it’s been in-progress for 3 days...”). Again, that’s not JIRA’s fault, but to use an Agile term, it’s an “enabler”.
- lmm 8y agoTools drive the way they get used, and JIRA naturally guides teams into micromanagement. Have you tried a more lightweight cards-on-board tool (like Trello)?