Project
The platform supports waterfall project management and Agile project management approaches and methodologies.
Waterfall
Kanban
The platform supports waterfall project plans using Gantt chart, Burndown and Burnup structure.
Gantt
Burndown
Burnup
The platform supports Agile projects using product backlogs, storyboards, kanban boards, and the support of periodic iterative reviews and retrospectives. The customer can create active boards/workspaces or lanes depending their project management business rules. Including all revies and retrospectives can be managed using PI Plannings
PI Planning
Kanban Board
The platform can manage a single project and multiple projects related to a single program. The customer will define and create Product with related Epic, Feature and Story, after can link with project Kanban or Waterfall
The platform can include business cases, program or project charters, and project requirements. All information can be included as attachment for each project, program or card (task), or as Objective to be managed including all risk assessment.
Attachment on Cards
Product/Program
Risks
Program and project risks can be recorded, assessed, and managed. When customer create new product/program can add risk assessment and edit for add more information or create new one later.
Project changes can be recorded, assessed, authorized, and managed. They are linked with Change Management Process
The progress of projects can be monitored, managed, and reported against defined project milestones and status dates. Project risks can be adjusted based on the milestone and completion date status. Stakeholder notification based on date and status-related risks and issues, missed thresholds, can be triggered using Kanban Metrics / Gantt and with transitions parameters, each task or bundle of can trigger different automations like, emails, whatsapp message, deployments (CI-CD), etc.
Gantt
Cost Metrics
General Metrics
Project budgets can be established and tracked, enabling the reporting of the actual spend and allocation of the budget throughout the life of a project, and breaking these costs down by cost type. On Project Management the customer can define each cost type on Costs screen and set for each task, Type and Value. After in metrics report can check total costs defined by type.
Creating Costs Type
Setting Costs type and value for each project/card
Tracking Costs
Expected deliverables, benefits, return on investment, and other quantifiable results of the project can be documented. On project total cost the ROI, Benefits can be documented.
Actual deliverables, realized benefits, an actual return on investment, and other actual results of the project can be documented and reported in comparison to the expected results. Customer can define the planned costs, capacity and ROI for each project and check the project status/health.
Set up Project information
Costs and Hours
Capacity Metrics
Costs Metrics
Minimal viable product deliverables for Agile projects, at the end of each iteration, can be documented automatically via history log and from project/iteration using comments and attachments.
History Log
Comments
Projects can be classified as successful or not, based on multiple elements defined by the client using Gantt, BurnUp, burndown information, Costs and Capacity Metrics and ROI/Benefities report.
All project information (Tasks, hours Status and Logs can be exported)
Post-project reviews based on the end condition of a project can be triggered, and the results of the post-project review can be documented using transitions for create a Request for post-project review and stored or not in Knowledge base.
Projects and programs can be linked or related to one or more services, both active services as well as services or service initiatives in the service portfolio pipeline, on project screen, customer can link services with projects, product or program.
New IT asset records can be created, and existing IT asset records can be updated, as well as services and components as a result of the project, relating to the project. Using transitions, after project end, actions can be triggered for create a new release, change or request for update IT Assets or components.
From Change
From Release
A project or program record can be linked or related to other records. The relationship between these records can be defined. All project can be triggered automatically from all platform process using workflow automation, or after finish a project or just a task (kanban card) using transitions, the project can create or update any process on platform or external platforms.
Transacition: The customer can define what will be the behavior when someone move a card from/to specific lane
After can select specific rules such as Permissions (who can move cards, settings like “self-assign and autofill (date fields) and rules
On rules, choose the desired automation
And the workflow will be triggerd and execute the defined automation
From Change
From Release
From Request
From a specific Task
Organizational change management (OCM) elements can be included within the life cycle of a projec, linked with change process can use both methods and all information requested will be available on change form.
The platform links projects to personnel resource availability using API external integration and/or automatic transactions.
The platform links projects to purchase orders using API external integration and/or automatic transactions.
The platform links projects to contracts/vendors using API external integration and/or automatic transactions.
The platform links projects to cost/financial/billing and invoice information using API external integration and/or automatic transactions or linked with Financial Process, apportionments tab.
