Craft.io

A product persons product tool.

Opmerkingen: I've been able to mostly live inside of one tool when working with my team. That pays for itself.

Pluspunten:

- RAPID data entry - if you have an idea of your first stories the views used allow you to rapidly write, press enter create a new story, and create another. This is actually massively time saving. - One stop shop - you can go from ideation to planning to delivery using Craft. It's what actually drew me to the product itself. - Picture support - pictures are supported in card view, so people at a glance can see what you're actually working on. - Idea Dump - you can quickly go from random thoughts to actual user stories in seconds - Fields - you can even add story points, effort, custom fields to help plan and prioritise.

Minpunten:

- Sometimes it's not accurate when it comes to who edited a story/item. This can cause quite the problem for paper trails. - Zappier support is flaky at best.

Good process sharing

Opmerkingen: The benefit is to keep everybody on the same page with a clear sprint backlog and clear milestone.

Pluspunten:

The way it allows us to share the Product Development process with ease along with the team. Coming from a similar product (Product Board) the learning curve has been short. I would recommend to small remote teams in their early stages of development.

Minpunten:

Not always easy to browse through, requires more effort than necessary to find items that haven't been properly tagged.

Overwogen alternatieven: Jira

Redenen om voor Craft.io te kiezen: This year

Redenen om over te stappen op Craft.io: Not so many alternatives are so specific for Product Management for Agile teams.

Buggy software

Opmerkingen: Helps with agile software development using Scrum approach.

Pluspunten:

In overall it's still a usable product. The developer needs to focus on fixing the bugs to improve overall usability. Also, you need to have a fast computer to run it. Running this thing on an old mac is a nightmare.

Minpunten:

Plenty of bugs and poor usability features. 1. Assigning a story to somebody will move the current swimlane to the first swimlane. 2. Assigning a story to somebody will move the ticket to the top of the swimlane. 3. A “Command+click” (on Mac) on a ticket in a swimlane does not open the ticket in a new tab. 4. Unable to post links with ampersands in the URL in comments. 5. Permalinks stop randomly working and bring to a different view.

Craft Review

Opmerkingen: I think craft is a wonderful, all in one solution for product teams. I love it and wouldn't go back to any other software for this purpose.

Pluspunten:

I really like the way craft is structured, and the different views it gives me to organise and work on my backlog items. Craft has made life so much easier and more organised for me and my team. Starting with the roadmap where it forces me to thin in terms of goals and initiatives, and moving on to the backlog where it gives me a very helpful workflow view to take stories through a proper process, and finally the list view which I use the most to work on my stories.

Minpunten:

JIRA integration is painful and prone to introduce confusion since it needs to be manually pushed to JIRA from craft, but works live the other way round. Also while I find it quite intuitive, new users find it particularly difficult to navigate round craft unless given some training. Also the strategy section in editor could be better designed, so that goals etc are not just floating text fields but had more of a concrete hierarchy. Otherwise they get difficult to manage beyond a point.

Supports the entire product management life cycle with a rich and easy to use interface

Opmerkingen: I need a tool to track documents and workflow associated with product management. This tool does that very well.

Pluspunten:

- Allows me to capture all the documents I need from 1) feature prioritization, 2) discovery, 3) design, 4) User testing all in one place. (Also supports implementation but we still use Pivotal Tracker for that.) - Very natural feeling interface, particularly once you learn how the story attributes (theme, epic, story type, version, sprint, team, and worker) work in the interface. - Allows stories to be assigned to different teams (and sprints for each team) for different stages of development (prioritization, discovery, design, user testing, etc.) is awesome - The kanban boards are well designed and implemented

Minpunten:

- It's still an early stage product so some of the features are incomplete and I occasionally run into bugs. That said, they are really responsive with bug fixes and feature requests. - Some features I would like, for instance, having kanban boards contain stories and tasks from multiple products, aren't yet available. (It's on the roadmap) - The roadmap diagram feature is weak. (It's slated for improvement.)