Wir helfen Unternehmen seit 17 Jahren,
bessere Software zu finden
CardBoard
Was ist CardBoard?
CardBoard ist eine führende Anwendung zur Abbildung von Nutzergeschichten. Arbeite mit deinem Team in Echtzeit zusammen, selbst wenn es auf der ganzen Welt verteilt ist. Nutzerfreundlich und hilft dem Team, Produkte zu entwickeln, die Kund*innen lieben.
Synchronisiere deine Boards mit Tools wie Jira, Trello, Azure DevOps, VersionOne und Pivotal Tracker. Deine Boards bleiben immer auf dem neuesten Stand, wenn du eine Änderung vornimmst.
Entdecke, was du bisher verpasst hast, und probiere CardBoard aus.
Wer verwendet CardBoard?
Cloudbasierte Projektplanungslösung, die Unternehmen bei der Verwaltung von Projekten, Einladungen, der Abbildung von Nutzergeschichten und mehr mithilfe von Echtzeitzusammenarbeit, Tracking-Tools und einem visuellen Dashboard unterstützt.
Du bist nicht sicher, ob CardBoard das Richtige ist?
Mit einer beliebten Alternative vergleichen
CardBoard
Weitere gute Alternativen zu CardBoard
Bewertungen über CardBoard
The easy way to Story Mapping
Kommentare: It's a useful tool which gets the job done. You sign up, and create a board without even thinking about the functions. It's that easy. Especially after they updated the interface. Keep in mind the tool is more in the freeform category - you can place anything anywhere in a grid - it won't require you to put specific things in specific slots. The drawback of it is that while it is comfortable, it can't fully integrate with task/issue tracking tools.
Vorteile:
While working with paper and stickies is the most quick tool to adopt, sometimes a digital one is required, as it provides certain benefits (quick editing; sharing; remote collaboration). I liked that it required zero learning for the basics. I just did the storymaps without a hitch, no wondering how I can do this or that. Of course, it provides some advanced functionality, but for the pure, basic, stickies-on-the-wall, experience, you there isn't a learning curve. Just plug and do.
Nachteile:
The free version is said to work like the GitHub model - all boards are public. Everyone can see them and browse them. So far so good. However, unlike GitHub where you can use one of several ways to get your repository to other people (sharing a link, inviting them, telling them the name of the repo...) I didn't find any of it here. I could not share the free board to my colleagues (even for viewing). There is a workaround with exporting, which can get the job done. I understand this is their business model, but then the site should not describe it working as GitHub's public repos, as it, in practice, differs as an end result.
CardBoard
Kommentare: I stumbled upon CardBoard a long time ago (2011) when I wanted an easy way to capture a Story Map. I really liked how easy it was to drop cards, move them around, and add some comments. The Team really enjoyed the look and feel of it. It did what we wanted and nothing more. I'm not a heavy user of it, but when I do need to put together a Story Map, CardBoard is what I turn to.
Vorteile:
The simplicity of the tool, it provided me with what I wanted and did not over complicate it with features I did not need.
Nachteile:
The export to excel option was pretty messy, but then again why export it? What I wanted was a way to capture the full board visually to put into a document or communication, to show the overall Story Map (which I could not get in screen shots) I realize I could provide a link to the board for people to access and see the actual Map, but sometimes you just want a picture of it to support a communication.
Good idea, missing features, buggy
Kommentare:
- Bad and Good
- The central idea of the board is nice
- Everything around seems to have been donc in a rush
- Management of teams are just a mess
- The idea a public boards, not searchable, messy . .. give you just a bad image
- Not intuitive (except for the cards management)
Vorteile:
- The idea - The fact that their is not real alternative to the product (not saying it's a good product, just not worst than competition) - Easy to use and simple - The journey feature
Nachteile:
- Buggy - The pricing model - Missing at least a crucial features: descent printing (what do you think teams do with a Story Map) - When you move things cards do not reorganized as expected and we end to have to move many cards across the screen. I should not be forced to think in advance what to enter first to avoid delating and moving things around after.
Antwort von CardBoard
vor 6 Jahren
Your feedback is greatly appreciated!
Cardboardit for developing roadmaps and communicating with stakeholders
Kommentare: The tool is great for presenting the roadmap to leadership, stakeholders, and Engineers. I would highly recommend it, however, would also suggest getting enough licences for all folks on your team due to the limited export capabilities.
Vorteile:
The application is intuitive and it's very easy to demonstrate the importance of technical debt to stakeholders.
Nachteile:
The export capability is limited. The description of the cards can not be exported without printing each card individually. The board view PDF export is not as user friendly/aesthetically pleasing as the actual application. Stakeholders are asking for PDF exports, however, I hesitate to share due to the aforementioned reasons.
Good but with some hiccups
Kommentare: I found the software quite useful for basic storyboarding and brainstorming new projects. Unfortunately, due to the limitations of the JIRA integration and the nature of the work I'm doing, it just wasn't useful for anything other than large/complicated projects that need a fair amount of planning and it could only be used in the initial stages. Once I had the list of story "slugs" it was better to manually migrate the list over to JIRA and cease using Cardboard.
Vorteile:
I quite liked the intuitive interface and ease of storyboarding things.
Nachteile:
The JIRA integration left something to be desired. The software did not do a good job of informing me of what it would do when I synced the two. It was also not clear to me that this was not a constant sync. Changes in one product were not automatically migrated over to the other. This was especially problematic because later syncs of the stories and epics caused duplicates of the previously synchronized items to appear because the system did not identify previously sync'd stories.
