monday dev vs. StoriesOnBoard

If you do web programming, code integration with your remote team, and/or software development that requires real-time monitoring of development progress, monday dev is an excellent tool for this. Like its base platform, Monday.com, monday dev is developed and attempts to integrate into a very "new era" organizational system of digital whiteboards, only now focused more on productivity and helping developers to be comfortable in remote work.

Incentivized

It's a great end-to-end tool from ideation through prototyping to maintenance. The Jira integration makes backlog management efforless for Jira users.

• Tracking
• Changing Status
• Backlog

Incentivized

• Individualization of maps, annotations and colors.
• Clear display depending on the situation (hiding stories).
• Handling of the cards in case of changes.
• The possibility to change content directly in the overview (title, annotation, color).

• More customization in automated tasks
• Ability to send visual snapshots of reports and dashboards
• Integrated reports from dashboards in dev and work management

• Integration for NextGen projects

We are very likely to renew, because it has been really useful

Incentivized

While monday dev is an excellent ally to organize and work in harmony with your team, there are still certain important aspects that need to be improved. They are minor, but if corrected, they will help improve the user experience when using it.

Incentivized

StoriesOnBoard works really well; all features are well thought through. It could look a bit fresher, although the new updated dashboard is already much better than it was.

Our experience with Monday dev support has been good

Incentivized

Monday is better than Jobber, as it gives you a place to see where all the jobs are and what the current status is. Everyone in the company can go to and see that view. It's not dependent on the status of the employee. Excel is much more technical and requires much more work to set up.

Incentivized

Miro: The handling in Miro was not comfortable enough. Easy Agile User Story Maps for Jira: The integration with Jira was a great idea, but the handling on the map was not good. Also, there were only 2 layers, which made it very difficult to define the cards.

• We can more easily grab the KPIs for our quarterly reviews.
• There are no automatic charts or reports I can pull for the quarter. Everything is manually gathered.
• Doesn't give us job costing.

Incentivized

• StoriesOnBoard (and story mapping in general) creates a low-cost visual method of aligning on high-level business and technical requirements early in a project and provides an ongoing reference as the project progresses. Having this alignment is critical for the later stages of the project.