Jump to content
Toggle sidebar
UNITApedia
Search
English
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Talk
Contributions
Navigation
Main Page
User Guide
Documentation
Viewpoints
Structural
Strategic
Beneficiary
Semantic
Infrastructure
Data
Beneficiaries
UNITA Participants
GEMINAE
Collectives
Agile Management Guide
Quality Management Process
Tools
What links here
Related changes
Special pages
Page information
Page values
In other languages
Editing
UNITA Agile Management Guide
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
More
Read
Edit
Edit source
View history
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Agile Tools== This section describes the main tools available for the UNITA community to adequately implement the agile project management methodology outlined in the management guide. === Open Project === [https://openproject.univ-unita.eu/login?back_url=https%3A%2F%2Fopenproject.univ-unita.eu%2F OpenProject] is the open-source project management software chosen by UNITA as its official software solution for the implementation of the agile methodology. It can be integrated as a third-party app in the Datacloud, linking files in the [https://datacloud.univ-unita.eu/ Datacloud] to project-related work and checking from the Datacloud which work packages in a project belong to certain files. ==== Who uses it ? ==== The tool has been configured according to the needs of the UNITA project. Task leaders and, where appropriate, project managers will be responsible for feeding, managing and monitoring the tool. For example, TTLs of the task 5-4 with the project manager of the university leading the task. In this case, UPPA. They will be responsible for alerting the relevant bodies and players as critical dates approach or when delays are noted. The task leaders and project managers will undergo hybrid training to learn how to use the software. All UNITA members will be able to see the progress of UNITA phase 2 through OpenProject, but they will not be able to implement the software. OpenProject will simply be an information tool and they won't receive any training. ==== How to use it ? ==== Each work package, task, activity, and action will be implemented in the tool according to the criteria defined in the agile table. Each task leader and co-leader will be responsible for feeding the tool. They will enter all the information concerning: * The start and end dates of the task, activity, action, etc. * Expected deliverables * Milestones * A description of the actions and activities To do this, they will use: * The UNITA 2 project * The general UNITA 2 glove and the gloves per [[Structural_Viewpoint|WP, Task]] * The minutes of the various meetings ([[Governance Board|GB]], [[Management Committee|MC]], [[Structural_Viewpoint|WP]], [[Task Team Members|TT]], etc.) * Any useful information '''Example:''' Once all the information has been entered, everybody can monitor the progress of the project in real time using the tool and its various views. The role of the project managers will be to monitor the progress of the project and to warn of any delays. ==== Project views ==== OpenProject allows different visualizations of the actions into which a project is broken down. From a classical Gantt view, which is appropriate to check deadlines and interdependencies, to a Kanban board, more fitted to the agile approach, each view offers different, complementary insights to the project managers and project team. '''Here is an example of these views:''' # Agile board view (Kanban board) # List view # Gantt view === Agile Document Templates === ==== Specification Action Sheet ==== * '''What''': This specification sheet provides a precise definition of the action. Every member of UNITA knows the ins and outs of the action. * '''Completed by who''': The Task Team Leaders * '''When''': The specification sheet must be drawn up before starting the action. ==== Models for Pre-minutes and Minutes of the Task Meeting ==== * '''What''': ** Each meeting must be prepared, in the form of pre-minutes. ** Minutes must be taken of each meeting. * '''Completed by who''': The leaders of the meeting. * '''How''': A template, in Word format, for taking minutes of meetings is available on the Datacloud. This template follows the guidelines of the AGILE method. === The RASCI Responsibility Matrix === '''The RASCI''' The Responsibility Matrix is a double-entry table which shows: * In the rows: the different phases and activities. * In the columns: the various actors involved. The specific roles attributed to the various actors involved in the same phase are shown at the intersection. For each activity, it is not possible to indicate more than one '''Responsible''' and more than one '''Accountable'''. Rather, it is necessary to subdivide the identified activity until it is possible to trace the role '''R''' and '''A''' to one and only one of the actors involved in the process. {| class="wikitable" ! RASCI !! Description |- | '''R''' || Responsible |- | '''A''' || Accountable |- | '''S''' || Supports |- | '''C''' || Consulted |- | '''I''' || Informed |} The roles that can be assigned for each activity are: * '''Responsible''' β defines the person responsible for completing the activity. The abbreviation '''R''' must be assigned to a single subject. Having more than one person responsible for the same task increases ambiguity and the chances that the work will not be done correctly. * '''Accountable''' β the person or persons responsible for supervising and approving the work being performed. This is usually a high-level person within the organization. The abbreviation '''A''' must also be assigned to a single subject. * '''Supportive''' β the person or persons who provide operational support to carry out the activity. * '''Consulted''' β are the subjects who must be consulted in order to obtain useful information for completing tasks or for improving the quality of the work itself. Communication with these subjects takes on a bidirectional nature in order to ensure proper follow-up. * '''Informed''' β is the class of people who do not need to be actively involved in the project, but who nevertheless have an interest in its execution and must be kept informed. The use of this tool is effective because it prevents the duplication of activities. Furthermore, the tasks between the actors are formalized in a clear and objective way. === Tools on Datacloud === '''Files''' : It is recommended that each task leader creates a shared folder in the task folder, where files upload will be possible. This will avoid email attachments. '''Talk''' : It is recommended that each task leader creates a discussion using the Datacloud '''TALK''' tool. This will avoid numerous email exchanges that can be difficult to follow. '''Collectives''' : This tool lets you create shared and collaborative documents online. More tools on the Datacloud guide: [https://datacloud.univ-unita.eu/index.php/apps/collectives/Datacloud guide]
Summary:
Please note that all contributions to UNITApedia are considered to be released under the Creative Commons Zero (public domain) (see
UNITApedia:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Debug data: