Project overview

Updated 2 months ago by Abhiram

What is a project?

Projects in Kissflow are geared toward value stream mapping. It consists of multiple steps that usually happen every time. When an item is created on a Kanban board, it starts on the left side and is moved by members through each step until it is completed. There are additional visualizations called List and Matrix that allow you to slice and dice your project data in real time.

You can create views based on a subset of all the project data to have better context while working. This is ideal for teams inside teams. Projects are great for flows that require more human involvement and where coordination and collaboration are more important than control.

Common use cases for projects

An example of a project might be in releasing a new feature for your software product. It requires you to have sufficient control over your value stream, ensure proper resource management, and involves individual steps such as research, requirements gathering, scope identification, the definition of goals, and deadlines for your project. As a product owner, you can create a software development project, but have unique views for the developers, designers, product managers, and testing teams.

You can create steps that must be completed to take an item to completion. Members can create items and move them along the Kanban in a linear progression from start to end. Project managers can then group, sort, and filter items using a list visualization to get an overview of the project and identify roadblocks and dependencies before they occur. Further, they can also perform resource balancing and reallocation using the Matrix visualization.

Here are other common use cases for projects:

  • Engineering project plan
  • Software and system deployment
  • Creative asset and content development
  • Campaign management
  • Webpage creation
  • Ad campaign creation

When a project is the best flow

Projects are ideal to use when you have events that require value stream mapping with a fixed starting and stopping point and multiple predictable tasks to get done. Projects require more flexibility in moving items than processes because items move more fluidly. Unlike case systems, where the sequence of cases is unpredictable, every item in a project must go through a predictable series of steps before it is considered finished. Projects put human workers in complete control as they move items to different steps on their own.


How did we do?