Let’s take a practical example on how you set-up things in Nektion. In this example we have a product with new commercial releases coming once per quarter. There are teams doing the development that can vary between releases and that do their work in sprints. From a product management standpoint it is key to manage which features go into a release, whereas the teams work on stories that are completed in a sprint. In this example we want to set-up the following views:
- A view with the Features that have been added to the product and to what stories they are split to
- A product kanban view where we can create new features and move them from new to validation to next up to development to done
- A list view where we can prioritize our next up features
- A roadmap timeline where we can show different features will be ready and in which release
- A view to see the content of a release
- A view for teams to see their backlog, the stories and their parent Features
- A list view for teams to prioritize their stories
- A sprint board for managing the state (Not Started, In Development, Done) of the stories
At this point it is also worth noting the difference between item/relation types and items/relations. Product is an item type, but iPhone and iPad could be the names of two items of the type Product. We could have the relation type called Product has Release that is used to create one relation between iPhone and Release 2020 and another between iPhone and Release 2021. When we define a model, we define item types and relation types, when we use the views we create items and relations. From here on, when we refer to concepts in Nektion, we will write them in italics.
Creating a practice account
Even if you have an existing Nektion account, it can be useful to create a practice account to go through this tutorial. To sign up for it, go here. Alternatively, you can just read the tutorial.