Live data from Hacker News

Wekan: An open-source Trello-like kanban

wekan.github.io

81–90 of 96 posts

Re: Wekan: An open-source Trello-like kanban

#82
post #74

Has anyone here had success with a personal kanban board? Considering it for myself, even if it isn't the intended use case.

Yeah, I find myself starting new things all the time and never finishing most of them. I've used a WIP limit to try to force myself to finish or explicitly dump projects.

Re: Wekan: An open-source Trello-like kanban

#83
post #32
post #4

I thought for a second my touchpad just broke. Might want to make the landing page look less like there's content down the fold …

And actually there is... For me the image is cut at about one third down the way, and I can't scroll to see the rest.

You can also go into browser dev tools and untick "overflow: hidden" on the body element css

Re: Wekan: An open-source Trello-like kanban

#84

If you want to do Kanban right, double down on making it possible to design actual Kanban workflows. Pretty ticket UI with checklists and GIFs must be secondary to this goal. Things that most actual Kanban flows have that no one has built into a decent product[0]: - Nested columns in lanes - Rows for class-of-service - WIP limits (per lane, per column, and per class-of-service) - Sub-boards for meta issues The actual…

Kanboard has it all

It has rows and WIP limits, but does it have the rest?

Re: Wekan: An open-source Trello-like kanban

#85

If you want to do Kanban right, double down on making it possible to design actual Kanban workflows. Pretty ticket UI with checklists and GIFs must be secondary to this goal. Things that most actual Kanban flows have that no one has built into a decent product[0]: - Nested columns in lanes - Rows for class-of-service - WIP limits (per lane, per column, and per class-of-service) - Sub-boards for meta issues The actual…

To be honest, Wekan is a pretty weak implementation of Kanban: - No Search (https://github.com/wekan/wekan/issues/552) - No WIP limits (https://github.com/wekan/wekan/issues/783) - No Swimlanes (https://github.com/wekan/wekan/issues/955)

It's a bummer because in the current state, Wekan doesn't really provide much real management value. I really wanted to use it for Kanban, because it's one of the flagship applications of the fantastic Sandstorm cloud platform (https://sandstorm.io), to introduce some colleagues to both concepts at the same time... but I guess I will only show them about the later.

Well at least it implements subtasks (checklists)!

Re: Wekan: An open-source Trello-like kanban

#86

If you want to do Kanban right, double down on making it possible to design actual Kanban workflows. Pretty ticket UI with checklists and GIFs must be secondary to this goal. Things that most actual Kanban flows have that no one has built into a decent product[0]: - Nested columns in lanes - Rows for class-of-service - WIP limits (per lane, per column, and per class-of-service) - Sub-boards for meta issues The actual…

I find rows counterproductive; they make it less obvious how full the board is, and don't help make better decisions. By all means sort each column in priority order so that people picking up a new task know which to pick up first; that's a lot less intrusive and covers the important use case.

Likewise sub-boards and meta-issues. If we're doing agile properly then each card represents a user-facing deliverable. Allowing meta-issues encourages doing the wrong thing.

Limiting work in progress I've achieved by having people assign themselves to cards, and questioning those who are on multiple cards. In the cases where we're violating our work-in-progress limit, I'd rather have the board reflect reality than not.

Re: Wekan: An open-source Trello-like kanban

#88

Earlier quoted context omitted.

Maybe YouTrack from JetBrains, these folks got some things right.

Except UX as a whole.

Like most of their IDEs, it's not about UX but about features. And on that point, they have done a lot!

Having used it for some projects as an alternative to JIRA, Trello, GitLab boards, and a few others that I tried, I think it's not perfect, quite hard to use for non-tech users, but much better than most of the alternatives.

The number of details/settings available is great compared to Trello or GitLab. The pricing/hosting is great compared to JIRA. The non-tech usability is much better in JIRA and Trello, but for a tech team, it has many small things/shortcuts like ones you already use in their IDEs which is really great.

There are hundreds of tools like this, and I tried maybe 20 or 30 of them; the thing is, there is no perfect tool out there, and there won't be as use cases for such a tool can be extremely different! YouTrack gets a lot of points right for a tech team from my experience though.

Re: Wekan: An open-source Trello-like kanban

#89
post #85

If you want to do Kanban right, double down on making it possible to design actual Kanban workflows. Pretty ticket UI with checklists and GIFs must be secondary to this goal. Things that most actual Kanban flows have that no one has built into a decent product[0]: - Nested columns in lanes - Rows for class-of-service - WIP limits (per lane, per column, and per class-of-service) - Sub-boards for meta issues The actual…

To be honest, Wekan is a pretty weak implementation of Kanban: - No Search ( https://github.com/wekan/wekan/issues/552 ) - No WIP limits ( https://github.com/wekan/wekan/issues/783 ) - No Swimlanes ( https://github.com/wekan/wekan/issues/955 ) It's a bummer because in the current state, Wekan doesn't really provide much real management value. I really wanted to use it for Kanban, because it's one of the flagship appl…

Hi, I'm current maintainer of Wekan.

Yes, Wekan does not have those features yet. Anyway, Wekan is being actively developed and features added. Wekan is friendly community driven project and welcomes all contributions.

Some have commented on Wekan GitHub issues that they prefer to use Wekan, because some others project management tools are overkill, or don't have the same usability as Wekan. It depends on use case.

Post reply on HN