Projects and Plans
In addition to capturing ideas, the Quiker platform also provides the Projects section, which concentrates all the management and monitoring of projects created in the hub.
This section was structured to centralize the execution of initiatives that evolved from the strategic to the operational field. Here, projects are no longer just approved proposals and start to be organized, planned and monitored in a structured way, allowing greater control over deadlines, responsible parties, deliveries and results.
In the Projects Section, users will find a complete environment for planning, organizing and monitoring activities, with different views that facilitate management according to the need for analysis. It is possible to monitor assigned tasks, view all registered projects, structure schedules, manage those responsible and ensure that each stage is aligned with the defined objectives.
Depending on the access profile, the user will be able to view only the projects to which they are linked or have a global view of all projects registered in the hub. This guarantees both individual autonomy and strategic control for managers and administrators.
In a practical way, this section represents the space where the strategy materializes into concrete deliveries, promoting more clarity, organization and efficiency in the conduct of projects within the platform.
Accessing the Projects section
When accessing the Projects section, the user will have access to all projects linked to an Active Cycle. To learn how to set up a planning cycle, visit the First Steps page
In this section, the user will be able to view projects both in **list **format and in a Gantt Chart, in which projects will be displayed according to their current progress level.
In the list format, project information will be presented in tabs, including:
-
Project code and title
-
ID tag category
-
Responsible for the project
-
Status and progress
-
Start date and end date
-
Budget and registered earnings
-
Actions, with two options:
- View: allows the user to view the complete details of the project;
- OKRs: allows you to view the OKRs registered for that project.
Using the diagram, it is possible:
- Monitor the status of each project in real time;
- Quickly identify delays or bottlenecks;
- Monitor deadlines and deliveries visually;
- Support the prioritization of actions and direction of teams.
When accessing or creating a project, the user immediately sees the main information located at the top of the screen, which is: person responsible for the project, category, start and end dates and a bar that indicates general progress. This data is the same as what appears on the project diagram and offers a quick view of the current status.
Summary SectionThe Summary section presents a consolidated and strategic view of the project, bringing together the main information necessary for its monitoring. There, the user can view data related to the planned and realized budget, estimated or achieved gains, defined objectives and other indicators relevant to management.
In addition, the section has a space dedicated to recording meeting minutes, allowing you to document decisions, alignments, progress and important updates throughout the project’s execution.
In this way, the Summary functions as a central point of consultation, concentrating the essential indicators and records to guarantee organization, transparency and control over the progress of the project.
Objectives Area
The section also has a section for registering and linking OKRs that are most related to the registered projects.
When accessing the Objectives area, the platform displays a pop-up that allows you to create new OKRs. At this stage, the user can register strategic objectives and their respective key results, as long as the necessary indicators have already been previously configured on the platform. For detailed guidance on this configuration, see the Getting Started page.
It is important to highlight that the objectives registered in the Project Objectives section are macro objectives, with a broader and more strategic nature. They cover a wider set of criteria and can even be used in different projects that share similar purposes. In this way, they function as general guidelines that guarantee the project’s alignment with the organization’s strategic goals.
When editing an objective, the user can define a name and description, clearly detailing what will be measured or tracked throughout the project. This definition is essential to ensure strategic alignment and common understanding between those involved.
Furthermore, it is possible to register Key Results, which will be used to monitor and update progress during project execution. For a Key Result to be configured correctly, an indicator must have already been previously registered on the platform, as it will serve as a measurement basis.
By linking an existing objective to a project, this project is also monitored in the Strategic Goals dashboards. In this area, the user can use the associated OKR as a filter, viewing all projects connected to the same strategic objective.
This structure allows for a consolidated and strategic analysis, making it possible to monitor gains and expenses both individually, per project, and in a grouped manner, considering all projects linked to the same objective.
**Monitoring Area **Within the Follow-up section, the user can record discussions, decisions and updates related to the development of the project, ensuring that all relevant information is documented for future reference. In this space, it is possible to define the date on which the meeting or update took place, describe the topics discussed and record essential data for building the project history.
When selecting the “+” button, the platform will display a pop-up with the fields necessary to create a new record. In this mode, the user can enter the date corresponding to the meeting or update and enter all information relevant to the monitoring carried out.
It is important to highlight that monitoring records are visible exclusively within the project itself. In other words, it is not possible to view these updates in other sections or tabs on the platform. They remain centralized in the Follow-up section, located in the Summary tab of the project, ensuring organization and context to the information recorded.
Teams Section
The Teams tab is intended for managing the members involved in the project, allowing you to organize who participates and what level of responsibility each user is.
When selecting the “Add first member” button, the platform will display a pop-up in which it will be possible to choose the users who will join the project team. The selection is made from the list of users who have access to the Strategic Module.
In addition to including members, the user can define the permission level for each member, according to the role they will play in the project.
- The Responsible profile has full access, being able to view, edit and manage all project information.
- The Employee profile can make changes and updates, actively contributing to the execution and evolution of activities.
- The Observer profile has access only for viewing, and can monitor the progress of the project without permission to make edits.
It is important to highlight that each project can only have one Responsible. If a new user is defined for this role, the replacement occurs automatically. For the Collaborator and Observer profiles, there is no quantity limit, allowing the project to have as many participants as necessary.
Project Scope
The Scope section is intended for the link between the project and an initiative previously registered on the platform. Initially, this area appears empty and starts to be filled from the moment an initiative is associated with the project.
The tab allows the user to formally connect the project to its original initiative, ensuring traceability from idea submission to project execution and completion. This link makes it possible to track, record and update progress based on the information originally submitted.To carry out this association, the user must access the Relationships section, where they can select an initiative already registered in the hub. After linking, the project scope is automatically filled with the data entered in the initiative application form, ensuring consistency and alignment between proposal and execution.
Furthermore, in this same section, it is possible to link the project to one or more strategic OKRs, through the Strategic Objectives area, strengthening the project’s alignment with organizational goals and allowing it to be monitored within the platform’s strategic perspective.
Schedule Section
The Schedule tab is responsible for planning and monitoring the activities necessary for the development of the project. Here, the user can create tasks, define execution periods, establish dependencies between activities and choose between a list or Gantt chart view, ensuring structured management of time and deliveries.
In list mode, it is possible to rearrange the order of tasks, update the status, adjust the percentage of completion, edit dates and create subtasks, allowing detailed control of execution. In the Gantt view, the user can adjust the duration of tasks directly through the graph bars, in addition to switching between monthly and weekly views and using “presentation mode” for an expanded view of the schedule.
To add a new task, simply select the “New Task” button, which will open a pop-up to define the name, description, start and end dates, status, which can be _not started, in progress, completed, delayed or paused, _and percentage of progress. In the same form, the “Task Dependencies” section allows you to link the activity to other existing tasks, organizing the logical sequence of the project and ensuring coherence in the execution flow.
The Sprint functionality makes it possible to transform the task into a Kanban item. When marking the task as a Sprint, it becomes part of the Backlog, where specific subtasks can be created to enable its execution. When selecting “Add new item to Sprint”, a modal is displayed to fill in the information for the new item. In the “Type” section, the user can choose between Task, Story or Bug. The Task option is recommended for operational organization in the Kanban format, while History and Bug are more used by teams that work with product development.
It is also possible to associate the task with an Epic, which represents a high-level objective composed of a broad set of activities, generally distributed across multiple Sprints. To create a new epic, you need to access the Backlog tab, select the “+” button in the Epics section and define the title, description and identification color. Once configured, the epic can be linked to Sprint tasks and will be displayed as a label in Kanban, in the Boards section, facilitating the strategic and visual organization of deliveries.In addition to planning activities, the Schedule section also allows recording hours worked in each registered task. The user can indicate the time dedicated to activities, ensuring greater control over the effort used in the project. This record contributes to productivity analyses, monitoring the team’s workload and identifying possible deviations between the estimated time and the time actually executed. In this way, the schedule stops being just a planning tool and starts to also act as an instrument for operational control and project performance management. The Schedule tab is responsible for planning and monitoring the activities necessary for the development of the project. Here, the user can create tasks, define execution periods, establish dependencies between activities and choose between a list or Gantt chart view, ensuring structured management of time and deliveries.
In list mode, it is possible to rearrange the order of tasks, update the status, adjust the percentage of completion, edit dates and create subtasks, allowing detailed control of execution. In the Gantt view, the user can adjust the duration of tasks directly through the graph bars, in addition to switching between monthly and weekly views and using “presentation mode” for an expanded view of the schedule.
To add a new task, simply select the “New Task” button, which will open a pop-up to define the name, description, start and end dates, status, which can be _not started, in progress, completed, delayed or paused, _and percentage of progress. In the same form, the “Task Dependencies” section allows you to link the activity to other existing tasks, organizing the logical sequence of the project and ensuring coherence in the execution flow.
The Sprint functionality makes it possible to transform the task into a Kanban item. When marking the task as a Sprint, it becomes part of the Backlog, where specific subtasks can be created to enable its execution. When selecting “Add new item to Sprint”, a modal is displayed to fill in the information for the new item. In the “Type” section, the user can choose between Task, Story or Bug. The Task option is recommended for operational organization in the Kanban format, while History and Bug are more used by teams that work with product development.
It is also possible to associate the task with an Epic, which represents a high-level objective composed of a broad set of activities, generally distributed across multiple Sprints. To create a new epic, you need to access the Backlog tab, select the “+” button in the Epics section and define the title, description and identification color. Once configured, the epic can be linked to Sprint tasks and will be displayed as a label in Kanban, in the Boards section, facilitating the strategic and visual organization of deliveries.
Backlog SectionThe Backlog tab concentrates the tasks related to the development of the project and organizes the items that will be executed within the Sprints. For this functionality to be used correctly, Sprints must have been previously configured in the Schedule tab.
When selecting the “Add new item to Sprint” button, the user will see a modal with the fields necessary to create the activity. At this point, it will be possible to define the type of the item — Task, Story or Bug — describe the activity, establish status, priority, target Sprint and person responsible for execution. This structure allows you to clearly segment development, ensuring traceability and organization of the workflow.
The Task option is recommended for operational organization and assignment of specific activities to team members, working as direct support for Kanban. The History and Bug options are most used by teams that work with product development, allowing them to organize features and corrections in a structured way.
In the Epic section, the user can create and link an epic to the task. The epic represents a high-level objective, composed of a broad set of activities that can be distributed across multiple stories over multiple Sprints. To create a new epic, you need to access the Backlog tab itself and, in the corresponding section, select the “+” button, defining the title, description and identification color.
After creation, the epic can be associated with any new task within the Sprint. When accessing the Tables section, the user will see the task in Kanban with the epic tag already linked, facilitating the strategic identification of deliveries and visual monitoring of the project’s development.
Frame Section
In this section, the user can view, organize and move tasks between the board categories, in addition to completing Sprints when necessary.
To add a task to the Sprint, you must previously create it in the Backlog section. After registration, the task will be available in the Board section, where the user can organize it according to its update status, moving it between the stages of the flow.
The user can also customize the naming of the status steps. To do this, simply select the gear icon in the top right corner. When you open the new settings section, you will be able to rename existing steps or add new statuses as needed.
When opening this new section, the user will be able to define a display name for the new status, in addition to selecting the type of status to which it refers, alternating between: new, in progress and completed.
The user will also be free to change the display color of the new follow-up status, customizing their view as needed.
At the end of a Sprint, the user will be able to end activities in the project using the Complete Sprint button. After carrying out this action, the user will be unable to perform any movement or editing in the status of tasks linked to the completed Sprint.However, if necessary, the user can reopen the Sprint by selecting the “Reopen Sprint” button, reestablishing the possibility of making the desired edits or movements.
Budget Section
The Budget area allows you to record the initial value predicted for the project and the actual value used.
To do this, the user uses the “New Launch” button, filling in the modal with the necessary information.
When accessing the modal, the user will be able to register the name of the new release and categorize it through the “Category” section. For the category to be available at the time of registration, the corresponding indicator must have been previously registered in the Settings section of the platform.
After registering the category, when exporting the Budget spreadsheet, the user will be able to filter the information directly through the Category tab, allowing the analysis of expenses segmented by each registered category.
Furthermore, the user will be able to determine the date on which the budget was made, and can monitor or update this information at any time. You can then fill in the planned value and realized value fields; however, if the amount actually realized is not yet available, the user can record it later.
This data feeds into the Overview section or Strategic Goals, where it is possible to monitor the project’s financial behavior over time.
In the Strategic Goals section, the user will be able to view the budget and gains generated by the project to date. It will also be possible to analyze one or more projects linked to the same OKR, allowing you to individually evaluate the gains and expenses of each associated project.
On the other hand, in the Overview section, the user will be able to view the earnings and expenses of all projects linked to the same call, obtaining a consolidated and global view.
Earnings Section
In the Gains tab, the user records and quantifies the benefits generated by the project during its execution.
To add a new Gain, the user must select the “Add Gain” button, where a modal is displayed to fill in the relevant information.
In this section, the user can register the name of the Gain being registered, and can also relate it to a Gain Indicator, which can be configured in the Settings section, in the Indicators tab.
Registering Indicators will allow, just like in the Budget section, the user to filter the gains related to that indicator, thus being able to carry out analyzes and generate significant insights.
When recording a win, the value in the section will be updated, providing an overview of your total winnings to date.
Just like the budget, recorded gains are consolidated in the Overview, allowing a complete analysis of project results.
However, just like the Budgets section, the Overview dashboard will present the general Earnings of all projects that were linked to the same call.