How does it works?

What is that and who can work with?

This is a web applications that help teams to handle projects and tasks (work) over time.
It is designed with free software, teams, goals and big projects in minds.

Everyone can use that and work with because it's not required any special skill.
Everyone can contribute in two different ways:

Moreover, everyone can create a new project (a new idea) and share to others.

Today a lot of projects are developed by large interconnected teams. But most of them works in different areas and sometimes it's very hard to understand the point of view of others.
This is a very limiting thing because most of them cannot understand complexity of the project itself maybe, or undervalue other's work.
With this software, each member of team can cooperate and understand easily the progression of:

Understand the engine

Most of the system is based on Scrum, an agile methodology for teams, but there are functions not provided that will explain in this section with the basic method.

The most important figure in this software is the user. All works around users. They are the most important and the most exciting part.
Without them there are no teams. So you need an account and provide basic informations like email and name.
Later you are ready to join to some project or create a new one.

Important: is an open platform so default projects are open to everyone but team leaders can block access to project itself and report the user! - With great power, comes great responsibility.

A project describe your idea, so you need to be clear to others to create attentions (good images, good description...), and is composed by:


You need to think for releases like the moments in your projects when you want to have salable package. It does not have to be a complete package about your idea. You and your team should decide how many tasks include; can be 20% of the project, or the 50%. It's your choice.
You need only to set expected release date.


Describe areas of your project, most important issues and so on. Those are essential to organize tasks and helps team.


As previously mentioned, tasks are singular works that someone need to complete.
They can be organized into goals and releases and have some important attributes:


Indicate the progress of task. There are 5 status points:

  1. Backlog: your idea/work is part of project but no one considered it
  2. Release: ok, now it's one on the most important task to do but it's not the moment, we need to define better the workload and something else
  3. Sprint: now it's time to work on; the task is available to be worked
  4. In progress: someone is working over this task
  5. Done: task done

Status is a very important feature that helps a lot teams. We enhanced more this feature with approvement. When someone works over task and complete it, he need to approve a comment and explain why, so in the future you can check your history of your works with motivations.


Workload is essential to understand how much is difficult this task. Workload help teams to understand it's speed too.
Understand ideal speed is important in the Scrum methodology because helps to organize tasks during Sprints (that we will explain better later)!

Workload is a aggregation of user's votes. There is medium point calculated by the votes and rounded to the nearest one.
This set of votes is useful to calculate the standard deviation too, to understand how is aligned the team (psychologically).

Why is important the "standard deviation"?
Understand your team feelings, enhance your team value; when your team is not aligned you can't express all your team power and work together can be more difficult.


Father allow you to specify a task that you need to complete before this. So you can create a task dependence.
An example can be: before paint a wall you need to build it.


There are tasks that to be completed you need to specify some operations. This can be useful for two reasons:


All those things are organized in time with Sprints.
A sprint is a time's period set by the project founder, like one week, two weeks or more. During this period thinkers and workers should work over tasks, comment and suggest workload for tasks, and finally complete them.

Sprint it's useful to estimate your team 'speed' (mean: how many workload can be achieved this sprint?). Later, with a medium calculation of your speed you can estimate your final release date (or date of your project completion).

No much more is needed to understand how does it works this software. There are small functionalities that will be explained in the FAQ section to make this guide more readable.

And don't forget, this is Free as in freedom software, so everything is documented (in the testing platform at the moment) and source code visible on github (i don't like but at the moment we need more developers). All links are in the footer.
If you want to contribute or know more, please tell me at penguyman at stronzi dot org.

Claudio Maradonna