updated examples for new delegaton canvas format

Author: bboc

docs/delegation-canvas/example-architecture-circle.md

@@ -2,66 +2,90 @@
 
 [back to the delegation canvas guide](../s3-delegation-canvas.md)
 
-**Note:** this example was made using the older format of the delegation canvas, therefore the sections about "competencies, qualities and skills
-" is missing, and the other sections are in a slightly different order and some have a slightly different title.
 
-## 1. Primary Driver / Mission
+## 1. Primary Driver / Purpose
 
 _"As our product portfolio grows, our apps mature, and the number of developers increases, we need alignment on architecture and guidance on software craftsmanship in order to remain productive."_
 
+
 ## 2. Key Responsibilities
 
 - awareness of status quo of and creation of a vision for architecture and craftsmanship
 - lead mid- and long-term initiatives to improve architecture and craftsmanship
 - balance short-term and long-term productivity 
 
-## 3. Key Challenges
 
-- different tech stacks and codebases of varied quality
-- knowledge silos in some teams
-- some teams have 50% new hires
+## 3. Dependencies
+
+- development teams (will have to work with the output of this circle, and will provide feedback on quality of architecture decision and coaching)
+- product owners (architecture needs to be aligned to product strategy and current customer needs)
+- strategy team (strategy is a driver for architectural decisions and vision)
 
 
-## 4. Key Constraints
+## 4. External Constraints
 
 - architectural changes must not stall product releases, so product owners can veto them
 - architecture decisions can be vetoed by development teams
 - craftsmanship needs to be aligned with development teams
 
-## 5. Key Deliverables
 
-- aligned coding guidelines
-- architectural vision
+## 5. Key Challenges
+
+- different tech stacks and codebases of varied quality
+- knowledge silos in some teams
+- some teams have 50% new hires
+
+
+## 6. Key Deliverables
+
+- a mid- and long-term strategy for evolving software architecture
 - backlog for impediments relating to architectural and craftsmanship
+- high-level coding guidelines that enable software craftmanship (aligned with all development team)
 - architecture workshops with development teams
 - at least one hands-on coaching session with each team member per quarter
 
-## 6. Key Metrics
 
-- simple monthly anonymous survey on developer satisfaction with architecture (current and outlook) 
-- number of coaching sessions per month and developer
-- number of architectural issues in the backlog with severity "high" or "critical"
+## 7. Competencies, qualities and skills
+
+At least half of the circle's members must have been with the company for at least 3 years.
+
+If possible, members of the Architecture Circle should have the following expertise:
+
+- current role: software developer 
+- several years of experience developing software on a code base that is at least 5 years old
+- understanding of the relevant current architecture patterns
+- nice to have: experience in workshop design and facilitation
 
-## 7. Key Resources
+
+## 8. Key Resources
 
 - architecture team can veto new features for a product when quality of codebase is threatened
-- members of architecture team reduce their development capacity to 50%
+- members of architecture team reduce their development capacity to a minimum of 50%
 
-## 8. Evaluation
 
-- team review every quarter, with a selection of:
-    + developers
-    + product owners
-    + CTO
+## 9. Delegator Responsibilities
 
-## 9. Consumers
+Since the Architecture Circle has been formed on the initiative of the development teams, it's their responsibility to support the circle as good as they can, e.g. by
 
-- development teams
+- implementing the circle's the decisions in the absence of objections
+- raising any possible objections against the circle's decisions
+- bringing to the circles attention any relevant observations about the code base
 
-## 10. Providers
 
-- strategy team (strategy is a driver for architectural decisions and vision)
-- product owners (architecture needs to be aligned to product)
-- development teams (feedback on quality of architecture decision and coaching)
+## 10. Key Metrics 
+
+- simple monthly anonymous survey on developer satisfaction with architecture (current and outlook)  and current health of the code bases
+- number of coaching sessions per month and developer
+- number of architectural issues in the backlog with severity "high" or "critical"
+
+
+## 11. Monitoring and Evaluation
+
+A team review every quarter:
+
+-   3-5 software developers from different teams
+-   product owners
+-   CTO
+
 
 [back to the delegation canvas guide](../s3-delegation-canvas.md)

docs/delegation-canvas/example-architecture-delegate.md

@@ -2,62 +2,73 @@
 
 [back to the delegation canvas guide](../s3-delegation-canvas.md)
 
-**Note:** this example was made using the older format of the delegation canvas, therefore the sections about "competencies, qualities and skills
-" is missing, and the other sections are in a slightly different order and some have a slightly different title.
 
-## 1 Primary Driver / Mission
+## 1. Primary Driver / Purpose
 
 _"For our architecture circle to make informed and helpful decisions, its members need to maintain a connection to the daily work of developers and product owners."_
 
+
 ## 2. Key Responsibilities
 
-- contribute as full member to all activities of architecture circle
-- represent needs and interests of your team in the architecture circle, and maintain
+- contribute as full member to all activities of the architecture circle
+- represent needs and interests of your team in the architecture circle
 - inform team members about activities and decisions of architecture circle
 
 
-## 3. Key Challenges
+## 3. Dependencies
+
+- the team you represent
+- architecture circle
+
+
 
-- balance contribution to your home team and contribution to architecture circle
-- balance needs of your home team and needs of other teams
-- balance short and long term needs
+## 4. External Constraints
 
-## 4. Key Constraints
+- on average, limit your work as an architecture delegate to a maximum of 50% of your weekly capacity
 
-- on average, limit your work as an architecture delegate to 50% of your weekly capacity
 
+## 5. Key Challenges
 
+- balance contribution to your team and contribution to architecture circle
+- balance needs of your team and needs of other teams
 
-## 5. Key Deliverables
 
-- coaching sessions for developers (in your home team, and in other teams)
-- facilitation of architecture workshops in home team
+## 6. Key Deliverables
+
+- coaching sessions for developers (in your team, and in other teams)
+- facilitation of architecture workshops in your team
 - participation in activities of architecture circle
 
 
-## 6. Key Metrics
+## 7. Competencies, qualities and skills
 
-- satisfaction of developers with your coaching sessions (standard survey)
-- satisfaction of home team members with information about and representation in architecture decisions (survey)
+- 
+ 
+## 8. Key Resources
 
-## 7. Key Resources
+- max. 50% of weekly capacity 
 
-- 50% of weekly capacity 
 
+## 9. Delegator Responsibilities
 
-## 8. Evaluation
+**Note:** for this example, assume each development team selects one of their members as a delegate to the  [Architecture Circle](delegation-canvas/example-architecture-circle.md), so the delegator would be the development team.
 
-- peer review each quarter, with 2 other members of architecture circle, 2 members of home team, and two participants in coaching sessions
-- development plan needs consent from architecture circle, home circle, participants of coaching sessions
+- team members must make time for coaching sessions
+- attend meetings the Architecture Delegate sets up for reporting on the Architecture Circles work and decisions
+- make issues relating to architecture and software craftsmanship known to the Architecture Delegate
 
 
-## 9. Consumers
+## 10. Key Metrics 
 
-- developers
+- satisfaction of developers with your coaching sessions (standard survey)
+- satisfaction of members of your team with information about and representation in architecture decisions (survey)
 
-## 10. Providers
 
-- home team (for architecture and craftsmanship drivers)
-- architecture circle (for architecture backlog and decisions)
+## 11. Monitoring and Evaluation
 
-[back to the delegation canvas guide](../s3-delegation-canvas.md)
+
+- peer review each quarter, with 2 other members of architecture circle, 2 members of development team, and two developers who were participants in that delegate's coaching sessions
+- development plan needs consent from architecture circle, home circle, participants of coaching sessions
+
+
+[back to the delegation canvas guide](../s3-delegation-canvas.md)

docs/delegation-canvas/example-product-owner.md

@@ -2,61 +2,68 @@
 
 [back to the delegation canvas guide](../s3-delegation-canvas.md)
 
-**Note:** this example was made using the older format of the delegation canvas, therefore the sections about "competencies, qualities and skills
-" is missing, and the other sections are in a slightly different order and some have a slightly different title.
 
-## 1. Primary Driver / Mission
+## 1. Primary Driver / Purpose
 
 _"We need someone to focus on making our appliances valuable to both the user and the company."_
 
+
 ## 2. Key Responsibilities
 
-- create features that users actually need
+- have the development team build  features that users actually need
 - align product features with company strategy
 - release planning
 
-## 3. Key Challenges
 
-- product carries a lot of technical debt
-- hardware development makes user testing challenging
+## 3. Dependencies
+
+- hardware and software development (builds features)
+- sales team (needs to sell the software to customers)
+ - strategy team (provides a strategy board which is updated at least quarterly)
+- architecture circle (provides guidelines and consulting about software and hardware architecture)
+
 
-## 4. Key Constraints
+## 4. External Constraints
 
 - CEO has input on as well a right to veto all product decisions
 - software development team has long lead times because they work for multiple projects
-- high turnover in this position requires solid documentation of everything that might be relevant to a 
+- high turnover in this position requires solid documentation of everything that might be relevant to a successor
+
+## 5. Key Challenges
+
+- product carries a lot of technical debt
+- hardware development makes user testing challenging
+
 
-## 5. Key Deliverables
+## 6. Key Deliverables
 
 - feature roadmap for the next 12 months
 - detailed user stories and wireframes covering at least 2 months
 - documentation of user tests
 - monthly report to with CEO about new stories and updates to roadmap
 - monthly report on selected pilot customers
 
-## 6. Key Metrics
 
-- net promoter score (customers)
-- pilot customer satisfaction survey
+## 7. Competencies, qualities and skills
+
+- good grasp of agile product management and agile software development
+- at least 2 years of experience as product manager or  business analyst 
 
-## 7. Key Resources
+## 8. Key Resources
 
 - pilot customers willing to use prototypes and test versions 
 - strategy board
 
-## 8. Evaluation
 
-- peer review every 3 months, with members of hardware team, software team, sales team and CEO
+## 10. Key Metrics 
 
-## 9. Consumers
+- net promoter score (customers)
+- pilot customer satisfaction survey
 
-- hardware and software development (builds features)
-- CEO
-- sales team
- 
-## 10. Providers
 
-- strategy team (provides a strategy board which is updated at least quarterly)
-- architecture team (provides guidelines and consulting about software and hardware architecture)
+## 11. Monitoring and Evaluation
+
+- peer review every 3 months, with members of hardware team, software team, sales team and CEO
+
 
 [back to the delegation canvas guide](../s3-delegation-canvas.md)

docs/s3-delegation-canvas.md

@@ -130,9 +130,9 @@ The Delegation Game is a simple and fun activity for defining and delegating a n
 
 Here's a few examples for delegation canvases as they might appear in a digital logbook:
 
-* [architecture circle](delegation-canvas/example-architecture-circle.md)
-* [architecture delegate](delegation-canvas/example-architecture-delegate.md)
-* [product owner](delegation-canvas/example-product-owner.md)
+* [Architecture Circle](delegation-canvas/example-architecture-circle.md)
+* [Architecture Delegate](delegation-canvas/example-architecture-delegate.md)
+* [Product Owner](delegation-canvas/example-product-owner.md)
 
 
 ## Downloads