refs #148: Refinement of new sections.

content/organization/accountabilities.md

@@ -62,9 +62,21 @@ Project-related accountabilities are described in terms of their ownership, prac
 
 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.
 
+Different models are available based on the delivery area.
+
+### Development area
+
 * [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).
+
+### Platform area
+
+`TO BE DONE`
+
+### Digital Strategy area
+
+`TO BE DONE`

content/organization/operations.md

@@ -76,14 +76,18 @@ Being appointed a project role means **you earned the company's and teammates' t
 These roles are not mutually exclusive, even if covering all at the same time is usually unfeasible, and not all projects need all of these roles to be clearly appointed.  
 To better understand the relation between seniority level and project roles in terms of professional growth, visit the section on [career advancement](/working-at-sparkfabrik/career-advancement).
 
+#### Development area
+
+In development projects, we recognize the following project roles.
+
 * **Analyst**: Analysts are great when it comes to mapping a domain, fathoming complexity, and expressing it in a clear, rational, understandable form. Analysts may not always have a solution at hand but for sure they know when a need is fulfilled or a problem is solved. If need be, analysts' skills make for great product owners.
 * **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
+#### Interactions between development 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.
 

content/resources/projectroles-acc-analyst.md

@@ -41,5 +41,5 @@ They must comprehensively analyze and manage client requests throughout the proj
 
 ## Interactions
 
-Please, visit the [Interactions between project roles](/organization/operations#interactions-between-project-roles) section.
+Please, visit the [Interactions between project roles](/organization/operations#interactions-between-development-project-roles) section.
 

content/resources/projectroles-acc-architect.md

@@ -34,14 +34,12 @@ Small projects with limited technical complexity may not require a dedicated Sol
 * Conducts (delegating at their discretion) technical reviews of work (code-reviews, etc)
 * Ensures the establishment of DevOps practices
 
-## Interactions
-
-Please, visit the [Interactions between project roles](/organization/operations#interactions-between-project-roles) section.
-
-
-
 ## Concrete outputs
 
 * Technical documentation for project architecture and ADRs (Architecture Decision Records)
 * Initial solution stub with the team
 * Technical implementation
+
+## Interactions
+
+Please, visit the [Interactions between project roles](/organization/operations#interactions-between-development-project-roles) section.

content/resources/projectroles-acc-team-leader.md

@@ -40,4 +40,4 @@ They ensure that the technical project documentation is kept complete and releva
 
 ## Interactions
 
-Please, visit the [Interactions between project roles](/organization/operations#interactions-between-project-roles) section.
+Please, visit the [Interactions between project roles](/organization/operations#interactions-between-development-project-roles) section.