refs #148: WIP on the project roles new section.

sparkfabrik · Oct 19, 2023 · bc66893 · bc66893
1 parent e5a6f53
commit bc66893
Show file tree

Hide file tree

Showing 8 changed files with 102 additions and 2 deletions.
diff --git a/content/organization/accountabilities.md b/content/organization/accountabilities.md
@@ -55,3 +55,16 @@ As you gain [seniority](/organization/operations#seniority-levels) and possibly
 ### Digital Strategy area
 
 `TO BE DONE`
+
+## Project-roles accountabilities
+
+Project-related accountabilities are described in terms of their ownership, practical tasks and expected observable outputs.
+
+The accent is on practices because these roles are ofter taken up by developers, engineers, designers and in general by colleagues with a technical expertise. Also, this model does not conflict with the shared and seniority-related accountabilites listed above.
+
+* [Analyst](/resources/projectroles-acc-analyst)
+* [Architect](/resources/projectroles-acc-architect)
+* [Team Leader](/resources/projectroles-acc-team-leader)
+* [Project Manager](/resources/projectroles-acc-project-manager)
+
+Learn [how these roles collaborate and interact](/organization/operations#interactions-between-project-roles).
diff --git a/content/organization/company-role-acc-supporter.md b/content/organization/company-role-acc-supporter.md
diff --git a/content/organization/governance.md b/content/organization/governance.md
@@ -9,7 +9,7 @@ The executive board is in charge of the strategy and business planning of the co
 The current board is composed of company founders, with the following duties.
 
 * **Stefano Mainardi**: CEO - Responsible for the overall progress of the company. Praised for success, and held responsible for setbacks.
-* **Paolo Pustorino**: Head of HR - Responsible for workforce training, development, management, recruitment, rewarding, compliance and ethos.
 * **Marco Giacomassi**: CFO - Oversees the company's financials. Responsible for budgeting, accounting, reporting, forecasting and investing.
 * **Paolo Mainardi**: CTO - Oversees the company's technology. Works to ensure that technology-related decisions align with business goals.
 * **Alessio Piazza**: COO - Oversees the company's day-to-day operations, sourcing, process control, resource allocation and activity planning.
+* **Paolo Pustorino**: Head of HR - Responsible for workforce training, development, management, recruitment, rewarding, compliance and ethos.
diff --git a/content/organization/operations.md b/content/organization/operations.md
@@ -62,7 +62,7 @@ We recognize three levels of professional skills, each with its salary bracket,
 * **Practitioner Cloud Engineer**: people at this level are skilled at and proficient with a bunch of different cloud technologies and have absorbed our methodology. They can mentor newcomers as well as developers and are autonomous in their work.
 * **Architect Cloud Engineer**: experienced professionals with diverse exposure across various cloud platforms and technologies. They can take on complex projects independently, engaging with the client and coordinating the work of their colleagues.
 
-Learn more about [each level's accountabilities](/organization/accountabilities) and how we evaluate people's seniority level.
+Learn more about [each level's accountabilities](/organization/accountabilities#seniority-related-accountabilities) and how we evaluate people's seniority level.
 
 #### Digital Strategy Area
 
@@ -80,3 +80,36 @@ To better understand the relation between seniority level and project roles in t
 * **Architect**: Architects describe the best possible solution to a framed problem. They are great decision-makers, understand the long-term implications of technical choices, know how to quickly probe, understand and adapt and always grasp the big picture.
 * **Team Leader**: Team Leaders excel at enabling teams, coordinating efforts, and ensuring project milestones are met. Focused on the outcomes, they drive, motivate, and keep the team committed to the project's success. They ask hard questions, suggests alternative paths, and apply a good deal of common sense to risk management.
 * **Project Manager**: Project Managers make things work. They coach, measure, look ahead, warn, and ultimately support people to give their best, removing obstacles, and improving their processes and procedures. In SparkFabrik people are never managed - work is. So Project Managers govern but never rule.
+
+Learn more about [each role's accountabilities](/organization/accountabilities#project-roles-accountabilities) and how we evaluate their outcome.
+
+#### Interactions between project roles
+
+To prevent overlap in problem-solving and avoid the bystander syndrome (stuff that can wreck projects and interpersonal relationships alike) we've provided a RACI <sup><a href="#fn1">1</a></sup> table below that clarifies roles and responsibilities throughout the project's various phases.
+
+In applying this clear information to your daily work, always keep in mind that effective teamwork and communication are essential for the success of our initiatives.
+
+
+| Activity / Role                                     | Team Leader | PM | Solution Architect | Analyst | CTO | COO |
+|-----------------------------------------------------|:-----------:|:--:|:------------------:|:-------:|:---:|:---:|
+| Pre-sales estimates                                 |      C      |  A |          R         |    R    |  C  |  I  |
+| Initial analysis                                    |      C      |  I |          C         |   AR    |  I  |     |
+| Epic/Milestone Mapping and Project plan             |      R      |  A |          C         |    R    |     |  C  |
+| Functional requirements and backlog population      |      R      |  C |          C         |    A    |     |     |
+| Definition of the work team                         |      I      |  R |          C         |    I    |  C  |  A  |
+| Week/sprint planning                                |      A      |  C |          R         |    C    |     |     |
+| Coordination of team activities                     |      A      |  C |          R         |    C    |     |     |
+| Drafting technical documentation                    |      A      |    |          R         |    C    |  I  |     |
+| Retrospectives and corrective actions               |      A      |  C |          R         |    R    |  I  |  I  |
+| Iteration events (plan, review, etc)                |      A      |  C |          R         |    R    |     |     |
+| Customer communications                             |      R      |  A |          C         |    R    |  I  |  I  |
+| Monitoring and evaluating progress                  |      R      |  A |          C         |    C    |     |  I  |
+| Coordination of external dependencies (other teams) |      C      |  R |          I         |    I    |  C  |  A  |
+| Definition of the solution                          |      C      |  I |        AR          |    C    |  C  |     |
+| Compliance with best practices                      |      R      |    |          A         |         |  C  |     |
+| Smoke-Testing e QA                                  |      R      |  I |          R         |    A    |     |     |
+| Technical rebuilding                                |      I      |  R |          A         |         |     |     |
+
+---
+
+<small><a name="fn1">1</a>: For sake of clarity, read the table as follows: **Responsible**: who's practically performing the task or decision. **Accountable**: the _single_ person held responsible for the outcome (you can call them "owner"). **Consulted**: People that MUST be consulted for information or validation before completing the task or decision. **Informed**: People that should be kept in the loop about that task or decision.</small>
diff --git a/content/resources/projectroles-acc-analyst.md b/content/resources/projectroles-acc-analyst.md
@@ -0,0 +1,5 @@
+/*
+Title: Ownsership - Analyst
+Description: Ownerships of an Analyst on SparkFabrik's projects
+Sort: 200
+*/
diff --git a/content/resources/projectroles-acc-architect.md b/content/resources/projectroles-acc-architect.md
@@ -0,0 +1,5 @@
+/*
+Title: Ownsership - Architect
+Description: Ownerships of an Architect on SparkFabrik's projects
+Sort: 210
+*/
diff --git a/content/resources/projectroles-acc-project-manager.md b/content/resources/projectroles-acc-project-manager.md
@@ -0,0 +1,5 @@
+/*
+Title: Ownsership - Project Manager
+Description: Ownerships of a Project Manager on SparkFabrik's projects
+Sort: 230
+*/
diff --git a/content/resources/projectroles-acc-team-leader.md b/content/resources/projectroles-acc-team-leader.md
@@ -0,0 +1,39 @@
+/*
+Title: Ownsership - Team Leader
+Description: Ownerships of a Team Leader on SparkFabrik's projects
+Sort: 220
+*/
+
+Team Leaders excel at enabling teams, coordinating efforts, and ensuring project milestones are met. Focused on the outcomes, they drive, motivate, and keep the team committed to the project success. They ask hard questions, suggests alternative paths and apply a good deal of common sense to risk management.
+
+They are responsible for the overall coordination of the teams, for directing the planning of single iterations so that they meet project milestones, for adhering to estimates, as well as for team motivation and morale, especially when they tend toward isolation.
+
+They define the recurring events in the production flow (planning, review, retrospectives) in agreement with the [Project Managers](/resources/projectroles-acc-project-manager) and are accountable for implementing corrective actions identified during the retrospective phase.
+
+They ensure that the technical project documentation is kept complete and relevant, even taking direct action in its preparation when required.
+
+## Ownership
+
+* Week/sprint planning
+* Coordination of team activities
+* Drafting technical documentation
+* Retrospectives and corrective actions
+* Iteration events (plan, review, etc)
+* Team motivation
+
+## Practical tasks
+
+* Makes themselves available to Solution Architects and the Team during estimation processes.
+* Collaborates with the Project Manager in drafting the project plan (epics and milestones).
+* Leads detailed planning during iterations.
+* Supports the Project Manager in meeting deadlines and delivering the content defined during the planning phase.
+* Supports presale estimates.
+* Collaborates with the Analyst in drafting functional requirements and refining the project backlog.
+* Oversees those customer communications that are necessary for operations.
+
+## Concrete outputs
+
+* Iteration planning
+* Technical documentation
+* Reporting of team and business events operational decisions, including calls with customers and minutes of agreed actions
+* Clear, updated and representative project board of the status of the activities