Date: Thu, 28 Mar 2024 13:31:36 +0000 (UTC) Message-ID: <1347584407.137.1711632696710@bf9bd9df42d3> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_136_630326868.1711632696710" ------=_Part_136_630326868.1711632696710 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
All things that the company undertakes can be thought of as an "Activity= ". Building the app for our customer SummitLynx is an Activity. Opening an = office in Zagreb is an Activity. Building our corporate identity is an Acti= vity. Doing our office interior is an Activity. Even ongoing things like ac= counting can be thought of as an Activity.
Each Activity must be bootstrapped before it can begin. Activity&nb= sp;require a Team (people), need an AL (Activity Lead), a set of goal, budg= et, etc. This guide describes how Activities should be bootstrapped.
Anyone can propose an Activity.
Activities must be approved by a Clan/School Leader before they can star= t.
Customer project Activities must be approved by the HoP. Typically, it w= ill be the Sales Clan that will bring in a customer project and submit it t= o the HoP for approval.
Internal projects must be approved by Management.
All Activities must have clearly defined Roles at the start including th= e AL: Activity Lead, key stakeholders and the= Team members' individual roles. Not all Activities will have a PM, know th= e difference between Activity Lead vs PM= .
However, all customer facing projects must have a PM involved, even if t= hey're not the AL.
Every project containing software development must have a designated&nbs= p;TL: Tech Lead.
Every project containing design must have a designated DL: Design Lead.
At the beginning of every project, the process that will be followed mus= t be announced and explained to all members of the Team by the AL.
If you need people for your project (the usual case), then you must requ= est resources from the Clan leaders, e.g
From CEO for: CRO, CTO, Hod, HoP, HoF, HoM, HoHR, OM
From HoP for: PM, Eng, Des, QA
From CRO for: AE
etc.
The source of truth for this is the Clan Roster here: /wiki/s= paces/9RPBK/pages/431849991.
You cannot go directly to an Engineer, Designer, etc. and ask them to do= something for you. Regardless of whether you're the CEO, or whoever, and r= egardless if you just want something quick (e.g. an estimate for a project)= . Please stick to this to protect people's sanity. For example, if you're t= he CRO and you regularly need time from Engineers for estimation, then ask = the leader of their clan (Engineers are in the Product Clan so that would b= e the HoP) to grant you a recurring block of e.g. 5h/week.
Resources can be requested decisively (I definitely need them), or provi= sionally (if the project gets signed, then I will need them, otherwise not)= . Support both.
Sometimes people outside of the PM Group will manage projects. If that's= you, then you're the AL: Activity Lead = and you assume all those responsibilities.
If it's your first time being the AL, ask for an intro into the basics f= rom the HoP.