Practice areas are a self-organized group oriented around a specific practice or craft - oriented towards learning, continuous improvement and cross-pollination of ideas and best practice across the company.
Practice areas that provide client services also work across departments and delivery to develop, market, sell, deliver and grow a set of related services and build the team that delivers those services.
It is important to note that practice areas may overlap in places, and that client projects can often be served by more than one practice area during the course of delivery. Similarly team members may work across multiple practice areas, even in a single day.
Each client facing practice area is identified by a unique 2 character code - this is used to identify practice area work in Harvest and other tools.
Each area has one or two Practice Area leads. The lead is responsible for guiding the collaborative creation of vision, strategy and goals of the practice area, supporting departments and people planning.
Each practice area has a Slack channel - key materials such as Trello boards, strategic planning documents, roadmaps etc should be pinned in each Slack channel.
Practice area meetings should be added to the main "CivicActions" calendar for visibility - see the calendar for the latest schedule and feel free to copy the event to your calendar if you would like.
|DevSecOps||DV||Owen Barton & Fen Labalme||#devsecops||Biweekly|
|Diversity, Equity & Inclusion||Rotating||#dei-ops||Weekly (Ops), Monthly (Brownbag)|
|Education Services||ES||Chianti Lomax||#eduservices|
|Open Data||OD||Kim Davidson||#opendata|
|Quality Assurance||QA||Eric Napier||#engineering-qa||Biweekly|
|Support & Helpdesk||SP||Ero Gray||#helpdesk|
|User Experience||UX||Shira Kates||#ux||Weekly (Ops), Weekly (Brownbag)|