Tutorial #3: Details of Agilefant's Concept Model





The interactive transcript could not be loaded.



Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Jul 15, 2014

In this video, Jennifer explains Agilefant's concept model. Read the script below!
Hi, my name is Jennifer, and in this video we will go over Agilefant's concept model. This model is the result of a decade of scientific research with top Finnish companies.

Unlike most agile tools, Agilefant strives to support agile, while being as methodology agnostic as possible. Agilefant adapts to your organization and ways of working, and thus supports your transformation towards becoming more agile

In Agilefant, products are the main place for storing information, so when getting started, one of the first things we need to do is to create a product. If customer-specific projects are an important part of your business, you may want to represent your customers as products in Agilefant.

Next, we need to create a team, assign some users to it, and give the team access to the product.

Then, let's add some user stories to our product. Work in Agilefant is carried out using projects, and these projects can be further structured with iterations

Projects and iterations are planned by moving user stories from the product level to the projects and iterations in question. If we have multiple teams working on a project, we will need to create an iteration for each of these teams.

Or, if we have a single team working on multiple projects, create a standalone iteration. These standalone iterations can include work from different products and projects.

We can even have multiple projects, each having multiple teams and their own iterations to make a single product go forward.

Individual people can also belong to multiple teams - and likewise any individual can work for as many different projects, iterations or stories as necessary.

While Agilefant has the power to support very large development organizations, we don't have to use all of this power.

If we don't need projects, we can simply work on stories from different products using standalone iterations.

Or, if we don't need iterations in a certain project, we don't have to use them. We can even use Agilefant simply for tracking individual standalone iterations, with no need to create products or projects.

Unlike most so-called agile tools, Agilefant also allows for true iterative refinement of requirements, by means of hierarchical story structures.

For example, an epic, too big to fit into a single project, can be broken down into smaller stories, called "features", the most important of which are then planned into a project.

And if these features are too big to fit into an iteration, we can further break them down into smaller stories.

In Agilefant, we don't have to "fix" stories to a certain level in advance - as Epics, Features or Stories - but rather can do the breakdown as we go along. If a particular story proves to be too big for an iteration, Agilefant can simply split the story, keeping the completed part of the story and its done tasks in the original iteration, and moving the new sibling story, containing the not-done tasks, into the new iteration.

Thanks for watching, and Full Power!


When autoplay is enabled, a suggested video will automatically play next.

Up next

to add this to Watch Later

Add to

Loading playlists...