Follow

is looking at project management software. It's all nice and flashy, but nothing seems actually useful. I want hierarchical tasks, I don't really see the point in Kanban, I want sync across all devices and web, I want FAST and I want lightweight. Hierarchical progress indication would be nice, too. quire.io comes closest to what I want, if it were open source I'd change two, three things and selfhost.

But why is this so hard? Do people actually use bloaty, slow software and are productive with it?

Quire really looks nice so far. Apparently it also has a decent offline mode. However, the connection to their servers got slow all of a sudden.

@TabascoEye Gerade mal etwas durchgeklickt. Sehr überladen. (Wir haben derzeit OpenProject, das ist auch voller Clutter und langsam und so... sehe gerade nicht so sehr, was Agantty da wesentlich besser macht :) Scheint aber an dem Gantt-Modell zu liegen, das glaube ich zu rigide für meine Vorstellung ist)

@Xjs
I've never successfully used software for project management. :( The Gannt model appeals to me, but applications seem to take it too seriously until it becomes an exercise in extreme manual data linkage manipulation. I want more simplistic but automated linkages, such as 'if there is a meeting, there is also a followup revision' or 'all lecture have pre-reading'.

My counterbrain, who thinks very much like I do, ended up implementing their own hand-coded system just to be able to do a loose 'x deps on y' model with back-propagation, but it was never suitable for prime time. I think most of this stuff is truly only good for generating reports to describe project state to management, not for actual work.

Nose to grindstone, I typically work out of physical notebooks or easily reordered nested lists, because stuff is always changing. For a while I used 'all day' tasks to back-propagate (the useful part of Gannt) in google calendar since it allows drag/drop.

I've also been tempted to borrow the milestone/ticket model from software development, since continually evolving issues under multiple attempts at resolution, potentially executing simultaneously, are my norm when something really serious is going on. It's far less frustrating to embody that in tickets than to have to wipe out slews of tasks every time a different approach needs to be taken.

@Xjs
It occurs to me that the ticket model also readily extends to projects that require stringent record keeping regarding liability/responsibility/legality. Which, unfortunately, I've occasionally seen mine morph into without warning.

@feonixrift I seem to have come to similar conclusions. I craved nested lists that somehow also have properties of tickets from software development. (Mind you, right now I'm a software developer after all.) The thing I found somehow tries to provide this, by giving me nested lists whose entries can individually be shoved in Kanban-style boards, assigned, tagged, moved and reordered, and, most importantly, resolved.

@feonixrift Now I'm almost as flexible as with my paper notebook, with the benefit of having it sync across my work computer, my »phone« (i. e. portrait-oriented pocket computer) and whatnot; and items being collapsible (on paper, I might have used physical pages though). — Some things I miss, though (let's see how interested the developers are in my ideas): Adding prose notes in between, and linking/modeling dependency apart from »is parent/child of« (but that already gets me quite far).

Sign in to participate in the conversation
chaos.social

chaos.social - because anarchy is much more fun with friends.
chaos.social is a small Mastodon instance for and by the Chaos community surrounding the Chaos Computer Club. We provide a small community space - Be excellent to each other, and have a look at what that means around here.
Follow @ordnung for low-traffic instance-related updates.
The primary instance languages are German and English.