5 ms·

flow has some features that AgileZen lacks such as: * Detailed metrics: You can filter by user, user group, or task type. * You can go back in time and see how

flow has some features that AgileZen lacks such as: * Detailed metrics: You can filter by user, user group, or task type. * You can go back in time and see how your board looked like anytime in the past. * Multiple users can be assigned to a task. * Search everything posted on your board including comments.

javery 16y ago
To be fair it doesn't look like flow has sub-tasks, custom kanban lanes, or attachments.. all of which AgileZen does have. I think the biggest difference though is that AgileZen has a very polished and nice looking UI and flow definitely needs some work in that department. You can't underestimate how important that is with an application I am going to be using all day.
- aycangulez 16y ago
  flow does support custom lanes. Subtasks are not supported on purpose. They limit the effectiveness of Work In Progress (WIP) limits and reduce visibility. For my take on subtasks, please refer to http://flow.io/finding-the-right-task-size-in-kanban.html http://flow.io/finding-the-right-task-size-in-kanban.html Could you tell me which areas of flow's UI needs work?
  - javery 16y ago
    I find sub-tasks to be extremely useful, it lets me keep my story cards at the right level for other stakeholders but also lets me add in the detail I need. Without them I end up using some other task list app for the details. The top bar has 2 lines of text and takes up 20% of the screen. Cards take up a set amount of space so half by board is white space instead of being filled with cards. I don't understand the Calendar or why I would want to see it all the time, if I wanted to see the past state of the board it would be fairly rare (if ever). Then just the general styling, AgileZen is very polished and clean and flow looks like an app I would have designed. :) (that's why I pay a designer)
  - cwilson 16y ago
    I tend to agree with javery. The UI needs polish. Your homepage could use some as well; as it is now there isn't anything that wows me and I wouldn't use this over AgileZen (although I currently do not even use that, the only Kanban system I am using is physical and I use Pivotal Tracker for everything else because it's free and awesome). UI and design are more important then you think. I don't care about features unless they are so disruptive and innovative that I just have to have them. Saying you have X, Y, & Z isn't really appealing to me. Competitors can easily add features but they can't easily build a better overall experience. Experience is a balance of UI, UX, general design aesthetic, and yes features. The keyword there is balance. It seems you are currently focused on features and none of the other stuff. Are you working with a good designer on this project or is it just developers?
    - aycangulez 16y ago
      I completely agree that features are not everything, and the overall experience is more important. In fact, I don't have any plans to implement subtasks (at least the way AgileZen did it) because I believe they are counterproductive. The user experience design is mine. Looking at the comments here, I see that some like the design and some not. Interesting divide.

javery 16y ago

To be fair it doesn't look like flow has sub-tasks, custom kanban lanes, or attachments.. all of which AgileZen does have. I think the biggest difference though is that AgileZen has a very polished and nice looking UI and flow definitely needs some work in that department. You can't underestimate how important that is with an application I am going to be using all day.

aycangulez 16y ago
flow does support custom lanes. Subtasks are not supported on purpose. They limit the effectiveness of Work In Progress (WIP) limits and reduce visibility. For my take on subtasks, please refer to http://flow.io/finding-the-right-task-size-in-kanban.html http://flow.io/finding-the-right-task-size-in-kanban.html Could you tell me which areas of flow's UI needs work?
- javery 16y ago
  I find sub-tasks to be extremely useful, it lets me keep my story cards at the right level for other stakeholders but also lets me add in the detail I need. Without them I end up using some other task list app for the details. The top bar has 2 lines of text and takes up 20% of the screen. Cards take up a set amount of space so half by board is white space instead of being filled with cards. I don't understand the Calendar or why I would want to see it all the time, if I wanted to see the past state of the board it would be fairly rare (if ever). Then just the general styling, AgileZen is very polished and clean and flow looks like an app I would have designed. :) (that's why I pay a designer)
- cwilson 16y ago
  I tend to agree with javery. The UI needs polish. Your homepage could use some as well; as it is now there isn't anything that wows me and I wouldn't use this over AgileZen (although I currently do not even use that, the only Kanban system I am using is physical and I use Pivotal Tracker for everything else because it's free and awesome). UI and design are more important then you think. I don't care about features unless they are so disruptive and innovative that I just have to have them. Saying you have X, Y, & Z isn't really appealing to me. Competitors can easily add features but they can't easily build a better overall experience. Experience is a balance of UI, UX, general design aesthetic, and yes features. The keyword there is balance. It seems you are currently focused on features and none of the other stuff. Are you working with a good designer on this project or is it just developers?
  - aycangulez 16y ago
    I completely agree that features are not everything, and the overall experience is more important. In fact, I don't have any plans to implement subtasks (at least the way AgileZen did it) because I believe they are counterproductive. The user experience design is mine. Looking at the comments here, I see that some like the design and some not. Interesting divide.