HDA10 Project Management
New feature introduced in HDA10 starting from Build 10.0.169 concerns project management; the correct use of the function requires the activation of the licensed projects module.
The project management module allows the entire team to move with flexibility, organize all deadlines, files and conversations in one place, always being aligned.
The configuration / modification / management of the projects is located under the menu item 'Project Management'.
The 'Projects' section represents their management interface from which it is possible to have an overview and apply any search filters.
Through appropriate 'New', 'Delete' and 'Other Commands' buttons it is possible to create new projects, delete existing ones or clone them.
As for tickets, it is possible to customize the fields related to the inbox, apply filters and through the export button create and share excel sheets with the relative search filters applied.
By default HDA offers the following project types: Development Project, Legal / Mandatory, Maintenance / Update.
However, it is possible to create different ones, associating any custom fields and configuring precise status workflows with respect to the type.
The creation therefore requires the mandatory compilation of the 'Description' field, the possible association of a custom table created ad hoc with respect to the type, the association of a Workflow of States, mandatory setting of the State to active or not and possible compilation of the Notes field where for example the resource can find useful information with respect to the type of project and its use…
The creation/association of a customized table will make certain characteristic fields available for a specific type of project.
The 'Reset Cache' button will actually make the new fields thus created/modified visible to the operators.
Below is an example of characteristic fields associated with the customized table with the possibility of creating them from scratch or deleting them.
The creation of a new characteristic field requires the mandatory compilation of the 'Name' and 'Description' fields, the Type of characteristic (eg Text, Data, CheckBox, Attachment ...) and possible configuration of the visibility permissions of the same (modifiable, only reading, visible or hidden to users…).
Project status management is the same as ticket status.
By default, the system already provides the most common statuses that a project can take, allowing any new modification or creation.
However, the creation, modification, cloning or deletion of the same are possible through special buttons.
Each State requires the mandatory compilation of the Description field, Type, if active or not (usable) and any Notes. The Code field represents the actual State assumed by the project at the Application/DB level.
The configuration of the state workflows presents a new simplified interface for choosing the different destination states.
The inbox allows to have evidence of all the available workflows reporting their description, any notes and status.
For a given Workflow it will therefore be possible to define which states are allowed or not available.
After selecting them and using the 'Select' button it will be possible to load the different states possible for that particular workflow.
The configuration section will then allow you to define the various 'start' and 'end' states (workflows) that the project can take.
Leaving the starting status empty, the selected destination status will be used as the initial status of the workflow.
As shown in the image below when loading 'New Workflow Detail' for each state (starting) it will be possible to enter one or more Destination States.
For example, the 'In execution' status will have two possible Arrival States: Completed and Suspended.
Project priority management is the same as that already defined for tickets.
By default HDA already offers priorities that can be modified or allows its creation by filling Description, Status and any Notes.
Through the appropriate 'New' button it will be possible to create new ones by filling in the Description, Active and any Notes field.
The risks section allows you to define the different degree of risk by attributing to each risk the actual probability in percentage that this occurs.
The correct configuration involves filling in the Description and Status fields and the possible compilation of the Probability and related Notes.
The Budget section allows you to define the budget available for a specific period of time, establishing a 'predicted value' of cost and relative overview of actual costs and remaining budget.
On the budget detail page, the fields relating to the validity of the budget, the description/title and any notes must therefore be filled out. Furthermore, the creation information of the same will be tracked; creation/modification date and resource that performed the activity. The presence of a histogram will allow to constantly monitor the ratio between the expected budget value and the actual costs incurred.
In the Attachments section any supporting documentation may be added and in the Costs section it will be possible to have a list of the actual costs incurred. We will see later how to load the costs in the project detail.
Project User Roles
It is then possible to define the various actors who will take part in the project through the special section 'Project User Roles'; the different role will allow the user to inherit certain permissions.
For example, the Project Manager, unlike the Developer, will have default access to cost items, available budgets.
Permissions and Permissions Cost
For the project entity it will be possible to define what are the generic permissions related to the different user groups; for example the creation or modification of the same, the possibility of cloning/deleting records and establishing any permits related to costs. Therefore certain cost items will be visible only to certain users or groups.
It will therefore be sufficient to drag the interested groups/users from the 'Available Groups' section to the 'Selected Groups' section and determine which permits to make available or not.
Project creation Example
Now let's see what are the various steps for a correct project creation. After choosing the Type of project it will be necessary first of all to define a Title of the same, the Status, any Description, Start/End Date, Priority and Risk. Insert any internal project reference (or applicant for it) and, in the Financial Section, Budget and Job Order available. The Budget (like the Order) is transversal to one or more projects.
In the relative cost section it will be possible to have an overview of all the cost items and information related for example to the billing date, the estimated value upon completion...
Below is an example of loading a cost item: Title, Reference Budget, Cost Type, Invoice Date. In order to correctly monitor the presence of an initial (estimated) value, current value (costs actually incurred at a certain date) and Estimated Cost at Completion (variable during project execution).
In the project detail, through the initial overview section, it will always be possible to keep the cost trend under control. This is also thanks to the presence of a cost distribution matrix in the various quarters of the year.
The section on the scheduled activities will give evidence of the various types of activities envisaged by the project with relative assignment to the group or to the single resource. The following is an example of a scheduled task upload with a definition of the expected effort:
Finally, in the planner section, it will be possible to have a real-time update of the progress percentage of the various tasks with the detail of the group or resource to which the activity is assigned and the estimated timing and relative effort.