Main Terms and Settings
This is a certain product (service) that you create. This may be a one–time project or ongoing work of the support and improvement for an existing product (for example, support and development of a website, applications, integrated marketing, property management services, etc.)
The project contains a list of user stories and issues. They can come from your customers, employees, buyers, your website visitors and other interested parties who are somehow connected with this product.
Execution (delivery) of the project is carried out iteratively and incrementally, that is, delivered in parts at regular intervals (sprints). At the same time, each new iteration carries an increment of the product—a tangible and valuable result for the customer and interested parties. It can be an implementation of a new function that can be already used, or development of a prototype and so on.
- Title (1)—contains the name of your product or the purpose of the project.
- Project prefix (2) (or the project key) is a character–letter code that will be assigned to each issue, which allows you to identify which project it belongs to.
Please note that: This field must be unique—there cannot be 2 projects with the same key.
- Description (3)—contains the basic information about the Project.
- Workflow (4)—a set of stages that the issue goes through in your project before being considered complete. By default, there are 2 workflows in the system: standard and simplified. Read more about them below.
- Project lead (5) or Product Owner—an employee who needs to know the market, how a product or service is being produced, and customer needs. He or she should be a connection between business, clients, stakeholders (a wide range of persons related to the enterprise) and the project team that creates it. The main role of Product Owner is the management of the issues’ list (backlog of the product), their compilation and prioritization.
- The project team (6) are employees of your company who will work on the issues and deliver the product to the customers.
- Issue types (7) are the building blocks of any Flowlu project. An issue can be a story, an error, a task. For more detailed information, please continue reading this article.
Overview of Issues
The issue is a specific requirement for the product that should be performed (or should not, depending on the Project lead decision).
There are different types of Issues. By default, the following types are available in the system:
- Story (the user story) is a requirement for a product or service answering the question: "Someone needs something for something."
- Task – measured and final target. It can be the internal tasks of the team, which is purely technical, not having any direct value for the customer.
- Bug – a defect, remark on the product, which must be eliminated.
- Type (1)—field for selecting a type of issue;
- Title (2)—a brief summary of the essence of the issue;
- Priority (3)—reflects the importance, urgency of an issue for the customer and product;
- Low—if the issue is not performed, nothing bad will happen, the business will not be harmed, and the client army will not come to your doors with pitchforks and torches, demanding to extradite your head;
- Average—issue must be performed in working order, set by default, its completion or non–completion affects the product and the business as a whole, but it does not have any urgency;
- High—issue must be completed (defect corrected) in priority order. Ignoring the tasks in this status will lead to significant consequences for the business, the project, or will lower customer loyalty. You can increase the priority to a high level, for example, when several clients repeatedly refer to the same defect;
- Critical—applies mainly to bugs. The task with this priority should be completed as soon as possible, as it is of critical importance for the project, business and can significantly affect the project if it is ignored. Such tasks should be included in the current iteration, even if work on it is already underway (we will talk about iterations later).
- Blocker—the highest priority, defect or error that must be eliminated immediately, otherwise the consequences will be catastrophic.
- The estimate of labour costs (4)—a numerical expression in conventional units (story points, parrots, human–days, etc.) of the effort required to accomplish this task. On the basis of this number, the owner of the product understands what will be the cost of implementing this task for the team. We recommend using this ratio: 1 story point is 4 working hours.
- Assignee (5)—a member of the team who will perform this issue;
- Description (6) —detailed description of issue or error, how it should be performed or reproduced, can contain photos, videos, screenshots, files;
- Category (7)—what summarizes several requirements into one large block. For example, the main page of the website, the facade of the house, the database, etc.
- Sprint (8)—an iteration, the time period in which this issue will be performed.
- Tags (9)—keywords that will help you to find and understand the context of the given issue faster.
- Links (10)—connections of this issue with others. Links can be one–way (clone, duplicate) or two–way, when task # 1 blocks task # 2. Accordingly, task # 2 is blocked by task # 1.
For example, you can not register on the website until you start the browser, so the registration task on the website is blocked by the task of launching the browser, and the task of launching the browser blocks the registration on the website. Links will help to build relationships between tasks and their relationship to each other. You can specify arbitrary links in the module settings.
Workflow is the sequence of stages that the task in your project goes through before it is considered to be completed. By default, there are 2 preset types of processes: standard and simplified. The stages are displayed on the Agile board in the form of columns.
A set of stages in the Standard Workflow:
- To do—what needs to be done, the queue of tasks within the sprint;
- In workflow—the task is being performed;
- Done—the task is completed by the executor, but verification or testing is needed;
- Accepted—the task is completed, the function is ready to use;
A set of stages in the Simplified workflow:
- To do.
- In progress.
Statuses of Stages
There are the global statuses which are set in Flowlu by default and assigned to each stage. The statuses have different colour coding, which, respectively, are linked to the stages. Colour bars allow you to quickly assess the progress of work since there can be a lot of stages, but the number of statuses is always unchanged.
There are 4 global statuses in Flowlu:
- To do—the blue colour-coding. Corresponds to all the stages, at which at the given moment the work on the task is not being performed;
- In process—yellow colour coding. Corresponds to all stages where work is being performed on the task;
- Awaiting approval—purple colour coding. Corresponds to the stages of waiting for verification, testing, etc.;
- Done—green colour coding. At the stage with this status, the task is considered completed. We do not recommend creating more than one stage with this status.
Global statuses in backlog
Global statuses on the Agile board
This is an entity that summarizes a group of issues. Allows you to categorize issues in the project according to certain characteristics and belongings.
List of requirements for the project (product). The requirements are in accordance with the priority of their implementation. The backlog is regularly being reviewed, getting filled and re-evaluated by the product owner and the team.
This is the main Scrum working tool along with the issues. It is an iteration of the delivery part of your project (product increment), which has clear time and scope limits (depends on the team's efficiency and performance). In the principles of Scrum, the sprint has a duration of 2 to 4 weeks, and its deadline cannot be changed after it starts.