Welcome to the B01LER team! 👋 We are thrilled to have you on board. This "Get Started" guide is designed to make your onboarding process smooth and enjoyable and to learn about all the neccessary organizational aspects. Whether you're a seasoned professional or a newcomer, we've got you covered. Let's dive in and unleash the potential of B01LER together!
Everything you need to know as a contributor is documented in the CONTRIBUTING.md.
Also make sure to read the README, have a look at Storybook and the Getting Started page in the Figma file, if you need more information about the product.
To become a member of the Core Team, please get in contact with one of the Core Team leads first. You can find a list of the leads in the team overview. Currently you can only become a member of the Core Team if you are working at Accenture. You should also be able to join most of the regular meetings.
- Lars Erbach (Lead)
- Yik Cun Chung
- Christian Hoffmann (Lead, absent)
- Barkley Taylor
- Ang Sherpa
- Thorben Hartmann (Lead, community leader)
All B01LER team meetings are in our B01LER Core calendar. The only exception is the B01LER Monthly, which is part of the B01LER calendar.
Regular meetings should be attended by every active team member that is avaiable. Optional meetings are optional and everyone can choose to join or not. We also have some paused meetings, which we are currently not facilitating but might will reactivate in the future.
| Meeting Name | When | Who | Why |
|---|---|---|---|
| B01LER Daily | Mondays, Wednesdays, & Fridays | Complete B01LER Core Team | Updating eachother |
| B01LER Marketing Bi-Weekly | Every other Monday | B01LER Leadership (and/or stand-ins) | Discuss and decide on general marketing topics |
| B01LER Dev Lead Touchpoint | Thursdays | Dev & Product & Project Management Leads, everyone from the B01LER Core Team that wants to join | Discussing and deciding on dev issues or topcis that recently came up |
| B01LER Monthly | Last Thursday of a month | Product & Project Management Lead, everyone at Accenture who wants to join | Giving an update, answering questions and sometimes deep dives into specific topics |
| Meeting Name | When | Who | Why |
|---|---|---|---|
| B01LER Pair Programming Hour | Fridays | Everyone from the B01LER (Dev) Core Team that wants to join | Collaborate and learn from each other by tackling coding challanges together |
| B01LER Open Door | Mondays & Wednesdays | Everyone from the B01LER (Dev) Core Team that wants to join | Giving guidance and/or answering questions about issues junior devs are working on |
| Meeting Name | When | Who | Why |
|---|---|---|---|
| B01LER Refinement | Every 2nd Thursday (When there is no Planning) | Complete B01LER Core Team | Refining issues for upcomming iterations |
| B01LER Pre-Planning | Thursdays | B01LER Leadership (and/or stand-ins) | Discuss objectives and prepare a set of issues to finish int he next iteration |
| B01LER Planning | Every 2nd Thursday (When there is no Refinement) | Complete B01LER Core Team | Celebrate outcome of the last iteration, present outcome of the pre-planning |
| B01LER Retro | Every 4th Thursday (After Planning) | Complete B01LER Core Team | Looking back at the last two iterations to improve things in the future |
| B01LER Design Review | Every Tuesday and Thursday | B01LER Design Lead and every team member that needs a design review | Getting approval from design for code implementations |
| B01LER Weekly Checkup | Mondays | B01LER Leadership (and/or stand-ins) | Discuss and decide on general product topics and check the roadmap |
Here is a list of all our communicataion channels including mailing lists and what we are using them for.
| Tool | Channel | Usage |
|---|---|---|
| Slack | #boiler-core | Team internal; Main communication channel, used for general questions, things to share and to inform the team about absences |
| Slack | #boiler-dev | Team internal; Used for dev-topics, that are only affecting devs, like open pull requests or generald technical decisions |
| Slack | #boiler | External (everyone at Accenture can join); Used for announcements and community building |
| Teams | B01LER General | External (everyone at Accenture can join); Used for announcements and community building |
| Teams | B01LER Monthly | External (everyone at Accenture can join); Used for the B01LER Monthly to share the agenda and meeting notes |
| Mailing List | boiler@accenture.com | Contact Mail for everyone outside of accenture to contact the team, reaches team leaders and stand-ins |
| Mailing List | boiler.community@accenture.com | Contact Mail for everyone outside of accenture to address violations to the code of conduct, reaches community leaders |
| Mailing List | boiler.security@accenture.com | Contact Mail for everyone outside of accenture to report security vulnerabilities, reaches team leaders and dev stand-in lead |
| Mailing List | boiler.dev.notifications@accenture.com | Mailing list to receive notifications from dev services like GitHub or Render, reaches developers and Product & Project lead |
Here is a checklist with all the accesses that new colleages need when working in the B01LER project. Every entry has a description on how to recieve access and a whom to contact.
- GitHub - Access to the deven-org and the b01ler team can be provided by an any of the team leads or other org-owners. Access to the deven-org also results in access to the B01LER Project.
- Figma - Everyone with an Accenture email address should be able to view the B01LER DS Figma team after joining the Accenture Global Figma organisation. Select "Use single sign-on" in the login and enter your Accenture-Mail to join the organisation. For Editing rights or when encountering problems, contact the design lead, design lead stand-in or the Product & Project Management lead.
- Outlook groups - Access to the B01LER Core and the B01LER Outlook group can be provided by any of the leads or stand-ins. With the invite, new colleagues will also be added to the B01LER Teams channel.
- Slack channels - All Slack channels are open to join for anyone in the song-asg.slack org and everyone already on the channels can add new members, to get access to the org, a UHD ticket has to be created.
- Mailing lists - Access to the mailing lists can be provided by the product & project management lead and stand-in.
- Parabol - Access to Parabol team can be provided by the product & project management lead.
Here is a checklist for project management to follow when onboarding a new colleage.
- WBS Authorization - to book hours on the projects WBS, new colleagues need to be authorized first. Authorization can be requested by the controlling team.
- Project forecast - new colleagues need to be added to the project forecast by the product & project management lead.
- Pennyworth - the product & project management lead needs to add new colleagues to the planning in pennyworth.
For further support you can always reach out to Thorben Hartmann or any of the other team leads via Slack. Another way is to reach out to our community leaders. Instructions on when and how to contact community leaders can be found in our Code of Conduct.
Here you can find some useful links:
- GitHub project - This is where we are managing our work. Basically it is better view of all the issues in the repository. Here you can find all our boards, our backlogs and our roadmaps. The documentation of all this can be found in the side-panel.
- Figma file - This is the main Figma file. Here you can find all the component designs and all the design tokens via the Tokens Studio plugin.
- README - In case you have not read the README, you should catch up soon. From here all other
documentation. From here the most important files in the
/docsfolder are linked, which you should check out as well. - One Note - In the B01LER Core One Note you can find meeting notes from regular meetings like planning, refinement and weekly checkups, as well as meeting notes from all other team internal meetings.
- Parabol - Parabol is used for retrospectives. Here you can see an overview of all actions that were defined in a previous retro.