The Roles and Tasks for ITA Leaders
-------
# Please DO NOT Edit #
-------
As per ITA General Policy and Roadmap: https:/
Each Board:
(1) Founders Board
(2) Technical Board (Phase 3 - http://
(3) Team Leaders Board
Should have different level of tasks and authority.
This blueprint will explain in details the authority and tasks of each board.
==========
Founders Board
==========
Introduction:
-------------------
This is the board of the founders of ITA Team. This is the highest level of authority within ITA Team/Community. Without their final approval, any decision no matter who has taken it is invalid.
This board should consist of:
• *A Must* - Founder 1 of ITA Team
• *A Must* - Founder 2 of ITA Team
• *Optional* - Co-Founder 1 of ITA Team
• *Optional* - Co-Founder 2 of ITA Team
All the other boards report directly to the Founders/
Tasks/Authority:
-------
1- Final Approval for any decision to be made within ITA Team.
2- Planning and Management.
3- Help and Support The Team Leaders Board.
4- Host Meetings with The Team Leaders Board.
5- In charge of NEW Team Leaders Recruitment.
Founders should NOT do:
-------
1- Dealing directly with members - this is HR Sub-Team task
2- Interfere technically with the projects of any Sub-Team. Founders can offer advice and can interfere ONLY if they have the required experience and skills needed but if they don't have any kind of skills and/or experience with a certain area, they should NOT be involved. Example: If a founder does not know anything about programming, he should not be involved. THIS HAS NOTHING TO DO WIT APPROVAL. We're talking about the technical involvement.
3- Doing someone's else job. That said, each and everyone (including the founders themselves) has specific task. It is NOT allowed for anyone to do an extra added tasks - this is just unfair.
4- Explaining in details each and everything. Founders of ITA are not School Teachers. They are volunteers and they do have real life and tons of stuff to worry about. That said, ITA Founders should NOT explain each and everything in details - specially during meetings - everyone must READ and learn and ONLY ASK if in doubt. NO MORE courses during the meetings.
5- Never ever speak as they represent themselves. ITA Founders represent ITA and they should speak/talk/write as such. Each and every communications must be done via ITA Channels.
6- Dictatorship and VIP. Yes, founders are the highest authority but they're not gods, they are humans. We're a team of democracy. Most if not all the decisions must be made by taking the vote of Founders + Team Leaders + Technical Board (Phase 3 - not yet done).
=============
Team Leaders Board
=============
Introduction:
-------------------
Reports directly to The Founders/
This board should consist of:
• Team Leaders of Each Sub-Team
Very Important Notes:
1 Number of Team Leaders depends on the fields/areas that ITA Team/Community will cover
and have.
2 Each Team Leader has a sub-team under the umbrella of ITA Team and that sub-team is
part of the bigger team, that is ITA Team.
3 Each Team Leader is in charge of recruiting members to his/her team.
Tasks/Authority
-------
1- Lead Their Sub-Team.
2- Organize and manage their projects.
3- Recruit new members to their team.
4- Take the final approval from the founders (report to the founders).
5- Participate with votes as members of Team Leaders Board.
6- They're free to organize themselves as they see fit.
Team Leaders should NOT do:
-------
1- ANY of the Founders' Tasks above.
2- Interfere with someone's else job.
3- Never ever speak as they represent themselves. ITA Team Leaders represent ITA and they should speak/talk/write as such. Each and every communications must be done via ITA Channels.
-------
# Please DO NOT Edit #
-------
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Essential
- Drafter:
- <Geek/>
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Review
- Series goal:
- None
- Implementation:
-
Informational
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
[iRQLinux]
due to the differences in opinions on different tasks and projects, the result is either weak or didn't gain the acceptance of the majority. That said, I propose to add one more task to the leadership board and I mean here Founders + Team Leaders and this task is simple: Quality Assurance/Control on anything that has our name. Such as Graphics, E-Learning Materials, Other Projects, etc.
The idea is super simple: before we publish anything on Facebook or any other channel, we need - we as Founders + TLs - to agree that the project that will be published is good and gains the acceptance of most of us. If that didn't happen, it means something is wrong and the concerned Sub-Team need to re-check its work. If most of us will vote YES for that project, most likely it will be accepted by others.
We're people (humans) with different opinions. Being on the same team does NOT mean we must have the very same opinion. We could agree on a vision but highly disagree on an opinion.
That is all. Everyone (Founders + TLs) vote for any work that will be published BEFORE publishing it.
-------
Work Items
Work items:
(1) Adding one more task to Founders + TLs - QA Task - we examine, check and vote for anything before publishing it to the public areas - to be discussed with ITA Leaders : TODO
Dependency tree
* Blueprints in grey have been implemented.
