Work items make Kitemaker unique and will improve how your team collaborates together. The right way to think of a work item is to represent a deliverable to your customers. That can be an experiment, a customer problem, a feature, a bug fix, or something else. It all depends on how you think about your deliverables.
The work item will then be a collaborative space for the team members to understand the context, figure out what to build, and work together to get things shipped.
The work item has three main parts; theĀ description, theĀ activity feed, and theĀ metadata.
TheĀ descriptionĀ is a document to share why this work item is essential (we encourage you to share the background and maybe links to customer feedback and user research). The rich description functionality lets you share what you plan to build, like the spec, and share resources like Figma designs, images, and other files and assets.
The description is also the place to break the work item into smaller tasks using todos. Be sure to @-mention people on the tasks. The number of tasks and the number of completed tasks will be visible on the board.
TheĀ activity feedĀ is a chronological list of activities and discussions related to the work item. It are a great place to have product discussions - what you plan to deliver, questions about how things are supposed to work, and updates on progress.
If you enable our integrations, you will also see activities from other tools in Kitemaker. They offer a great way to help everyone working on the delivery keep track of relevant discussions and activities across design, engineering, and chat tools.
In addition, there are several ways to organize and manage your workflow usingĀ metadata. There are labels, roadmaps, statuses, impact, effort, and more.
Read more about the specific features of work items below:
