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
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!
=== What is AGILE for UNITA? === This type of project management encourages collaboration and continuous improvement. It is referred to as an agile team. AGILE consists of dividing the project into several phases or cycles, and the various project activities are broken down into several specific, simple and prioritised actions. ==== 1. Definition of an AGILE TEAM ==== Agile teams work in a highly collaborative way, adopting the most effective communication techniques for their situation and striving to work together as closely as possible. The aim is to ensure that: * Everyone feels part of the team, moving in the same direction. * The team includes all the people needed to complete the task. An autonomous team must have the skills and knowledge needed to get the job done. Specialists may be called in if necessary. * Each team member contributes according to his/her means. The team is made up of multidisciplinary members; * The team is self-organised. The people best placed to plan and organise the work are those who actually do the work. This results in more accurate estimates, more realistic deadlines and greater team commitment to the plan; * The team maintains a steady pace; everyone works closely together, avoiding discouragement. ==== 2. Definition of an ACTION ==== # An action may be defined as the result of a breakdown of a general activity in specific and simple operations, to be executed within one month, with a clear outcome. # An action is defined and detailed by an explicit specification sheet (cf the UNITAโs project management tools) ==== 3. Definition of a CYCLE ==== # Every month (at least), the task co-leaders plan, organise and coordinate a meeting with all the members of the task: the task meeting. A cycle is defined as the period between two task meetings. During this period, the team must work on the action(s) chosen at the meeting at the start of the cycle. At the end of the cycle, the actions are reviewed at the next meeting. Based on the progress made, the team then decides what action to take next: continuation, reorientation, stopping, etc. The team implements the decisions taken on the actions in progress during the next cycle. # A week before the task meeting, the co-leaders meet to prepare for the meeting and draw up the pre-minutes. They make these pre-minutes available to the task team members. # Depending on the actions to be implemented, they may decide to divide the work into sub-groups and schedule interim meetings.
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: