willi-dev · August 24, 2022 02:14 · Feb 22, 2019 · Feb 22, 2019 · Feb 22, 2019 · Feb 22, 2019
diff --git a/team_charter.md b/team_charter.md
@@ -50,7 +50,7 @@ As a collective of frontend engineers, our responsibilities will overlap greatly
 - Code review
 - Debugging/fixing issues and features
 
-However, as areas of expertise are made available, lead roles will be assigned accordingly. If you see an opportunity for role assignment, consult with the team manager. Currently lead roles are:
+However, as areas of expertise open up, lead roles will be assigned accordingly. If you see an opportunity for role assignment, consult with the team manager. Currently lead roles are:
 
 ##### Corey
 

diff --git a/team_charter.md b/team_charter.md
@@ -1,5 +1,7 @@
 # Team charter
 
+Contained within this charter is an outline of expectations and guidelines for members of the frontend team. This is an open, collaborative document.
+
 - [Background](#background)
 - [Mission and objectives](#mission-and-objectives)
 - [Resources](#resources)

diff --git a/team_charter.md b/team_charter.md
@@ -9,7 +9,7 @@
 
 ## Background
 
-Long ago, ReCharge was made up of a small team of passionate, innovative hackers. As the customer base grew (and their woes), they recognized the importance of hiring experienced professionals who excelled in specific areas of expertise.
+In the beginning, ReCharge was made up of a small team of passionate, innovative hackers. As the customer base grew (and their woes), they recognized the importance of hiring experienced professionals who excelled in specific areas of expertise.
 
 Looking to make the greatest, quickest impact on their growth, they decided that their first important hire would be in frontend.
 

diff --git a/team_charter.md b/team_charter.md
@@ -1,4 +1,4 @@
-# Frontend team charter
+# Team charter
 
 - [Background](#background)
 - [Mission and objectives](#mission-and-objectives)

diff --git a/team_charter.md b/team_charter.md
@@ -1,4 +1,4 @@
-# Team charter
+# Frontend team charter
 
 - [Background](#background)
 - [Mission and objectives](#mission-and-objectives)

diff --git a/team_charter.md b/team_charter.md
@@ -82,7 +82,7 @@ Any frontend focused PR must receive a code review from another of your frontend
 
 ##### Shared debugging/qa responsibility
 
-We have a collective responsibility to ensure bugs are fixed, or identified. The #recharge-qa channel is used by the company at large to report feature-breaking bugs. Contribute to their investigation and even resolution when possible. Communicate serious bugs to others.
+We have a collective responsibility to ensure bugs are fixed, or identified. The [#recharge-qa](https://rechargepayments.slack.com/messages/C02UT80QX/) channel is used by the company at large to report feature-breaking bugs. Contribute to their investigation and even resolution when possible. Communicate serious bugs to others.
 
 Learn to share the burden and avoid burn out.
 

diff --git a/team_charter.md b/team_charter.md
@@ -48,7 +48,7 @@ As a collective of frontend engineers, our responsibilities will overlap greatly
 - Code review
 - Debugging/fixing issues and features
 
-However, as areas of expertise are made available, lead roles will be assigned accordingly. If you see an opportunity for role assignment, consult with the team lead. Currently lead roles are:
+However, as areas of expertise are made available, lead roles will be assigned accordingly. If you see an opportunity for role assignment, consult with the team manager. Currently lead roles are:
 
 ##### Corey
 

diff --git a/team_charter.md b/team_charter.md
@@ -1,7 +1,5 @@
 # Team charter
 
-## Overview
-
 - [Background](#background)
 - [Mission and objectives](#mission-and-objectives)
 - [Resources](#resources)

diff --git a/team_charter.md b/team_charter.md
@@ -1,5 +1,7 @@
 # Team charter
 
+## Overview
+
 - [Background](#background)
 - [Mission and objectives](#mission-and-objectives)
 - [Resources](#resources)

diff --git a/team_charter.md b/team_charter.md
@@ -1,11 +1,11 @@
 # Team charter
 
-[Background](#background)
-[Mission and objectives](#mission-and-objectives)
-[Resources](#resources)
-[Roles and responsibilities](#roles-and-responsibilities)
-[Team operations](#team-operations)
-[Team member assesment](#team-member-assesment)
+- [Background](#background)
+- [Mission and objectives](#mission-and-objectives)
+- [Resources](#resources)
+- [Roles and responsibilities](#roles-and-responsibilities)
+- [Team operations](#team-operations)
+- [Team member assesment](#team-member-assesment)
 
 ## Background
 

diff --git a/team_charter.md b/team_charter.md
@@ -1,5 +1,12 @@
 # Team charter
 
+[Background](#background)
+[Mission and objectives](#mission-and-objectives)
+[Resources](#resources)
+[Roles and responsibilities](#roles-and-responsibilities)
+[Team operations](#team-operations)
+[Team member assesment](#team-member-assesment)
+
 ## Background
 
 Long ago, ReCharge was made up of a small team of passionate, innovative hackers. As the customer base grew (and their woes), they recognized the importance of hiring experienced professionals who excelled in specific areas of expertise.
@@ -14,7 +21,7 @@ Frontend is now an essential component of every squad, and our responsibilities
 
 ## Mission and objectives
 
-As a member of the frontend team, ReCharge will rely on you to help drive, deliver, and support her many features while remaining attuned to the company core values: Empathy, Ownership, and Simple Solutions.
+As a member of the frontend team, ReCharge will rely on you to help drive, deliver and support her many features while remaining attuned to the company core values: Empathy, Ownership, and Simple Solutions.
 
 ##### Some of our key objectives include:
 

diff --git a/team_charter.md b/team_charter.md
@@ -8,7 +8,7 @@ Looking to make the greatest, quickest impact on their growth, they decided that
 
 ##### Frontend today:
 
-Three years later, the frontend has become an established and growing department of passionate creators that still maintain the spirit of innovation that drove the initial growth of the company.
+Three years later, frontend has become an established and growing team of passionate creators that still maintain the spirit of innovation that drove the initial growth of the company.
 
 Frontend is now an essential component of every squad, and our responsibilities stretch far and wide over a multitude of unique and interesting projects.
 

diff --git a/team_charter.md b/team_charter.md
@@ -0,0 +1,88 @@
+# Team charter
+
+## Background
+
+Long ago, ReCharge was made up of a small team of passionate, innovative hackers. As the customer base grew (and their woes), they recognized the importance of hiring experienced professionals who excelled in specific areas of expertise.
+
+Looking to make the greatest, quickest impact on their growth, they decided that their first important hire would be in frontend.
+
+##### Frontend today:
+
+Three years later, the frontend has become an established and growing department of passionate creators that still maintain the spirit of innovation that drove the initial growth of the company.
+
+Frontend is now an essential component of every squad, and our responsibilities stretch far and wide over a multitude of unique and interesting projects.
+
+## Mission and objectives
+
+As a member of the frontend team, ReCharge will rely on you to help drive, deliver, and support her many features while remaining attuned to the company core values: Empathy, Ownership, and Simple Solutions.
+
+##### Some of our key objectives include:
+
+- Drive value through improved customer experiences
+- Creation of user interface and experience patterns
+- Application and adherence to company branding across all features
+- Support in the resolution of feature breaking bugs
+- Writing modular and readable components
+- Improving code maintainability
+- Provide assistance wherever possible to the company at large
+
+## Resources
+
+Frontend is a career in life long learning. As such, any pursuits to further your own well of knowledge or its cross-polination will be encouraged. Speak with your manager to discuss if and how ReCharge can provide assistance with any of the following:
+
+- Educational or course materials (books, tutorials, online lessons)
+- Formal training, classes
+- Conferences, team meetups
+
+## Roles and responsibilities
+
+As a collective of frontend engineers, our responsibilities will overlap greatly. You can expect the following:
+
+- Code review
+- Debugging/fixing issues and features
+
+However, as areas of expertise are made available, lead roles will be assigned accordingly. If you see an opportunity for role assignment, consult with the team lead. Currently lead roles are:
+
+##### Corey
+
+- Team processes
+- Documentation
+
+##### Roberto
+
+- Component development
+- JavaScript best practices
+
+##### Sean
+
+- Framework implementation
+
+## Team operations
+
+Although ReCharge is a quickly growing company with many systems that can and will change, you can expect a certain level of consistency in our processes. Keep in mind, this area does not cover squad operations (standups, demos, task assignment):
+
+##### Bi-weekly team meetings
+
+These meetings will be used to discuss changes in the team, upcoming projects, in-progress work, concerns about existing systems, general updates, a chance for comradiere, and anything else that excites you or you feel would be of interest to the team.
+
+##### Backlog of frontend tasks
+
+Jira will be used to maintain the growing backlog of frontend related tasks. Feel free to pull from this log or add to it. Adding tasks to your sprint should be discussed with squad project manager.
+
+##### Peer code review
+
+Any frontend focused PR must receive a code review from another of your frontend team mates. While QA does exist, we should maintain a minimum level of decorum. Meet feature, story or task requirements and test your work for obvious bugs.
+
+##### Shared debugging/qa responsibility
+
+We have a collective responsibility to ensure bugs are fixed, or identified. The #recharge-qa channel is used by the company at large to report feature-breaking bugs. Contribute to their investigation and even resolution when possible. Communicate serious bugs to others.
+
+Learn to share the burden and avoid burn out.
+
+## Team member assesment
+
+ReCharge is currently defining its processes for assesment and evaluation. That said, you can expect the following:
+
+- Weekly 1-on-1 with team manager
+- Monthly 1-on-1 with department head
+- Semi-yearly performance reviews