Professional Development at CivicActions
CivicActions recognizes the importance of individual Professional Development for all team members. We value Professional Development for a number of reasons:
- It's a win-win. Professional Development grows the depth and value of the company offerings and enhances your career opportunities too.
- Professional Development provides career mobility for each person - increasing our feeling of safety, which leads to:
- Having the courage to fail, which leads to experimentation, innovation, and learning
- Having the courage to challenge the status quo, which leads to organizational learning
- Having the courage to be vulnerable, which leads to authentic communications and connection
- Open-minded thinking, which leads to increased tolerance of others ideas and personality styles
CivicActions supports and encourages the Professional Development (prodev) of each team member by providing an annual budget of $1,200 per person to be used for prodev-related expenses. Note: If you are a part-time employee or under 30 hours/week, your budget will be prorated based on your working hours.
In addition to the $1,200 annual budget, each team member is encouraged to use a "take what you need" approach to using time for prodev pursuits during business hours, within the bounds of any billable hours goals you may have. If you need guidance on what amount of time is appropriate to spend on prodev in a given year, consult with your manager or refer to the historical data table below.
Historical Prodev Hours Spent:
|Year||Company-wide Prodev Hours Used||# People Billing Prodev Hours||Average Prodev Hours Used Per Person Annually|
*As of January 1, 2019. All data was pulled from Harvest.
In order to provide some additional structure, support and focus to the prodev efforts of individuals, 1 month long prodev sprints will be held on a regular basis. During these sprints, participants will attend scrum meetings 2 to 3 times per week to talk about their prodev progress being made and connect with others pursuing their prodev goals at the same time. The sprint will also consist of a demo or review meeting, so that team members can share what they have accomplished or learned during the sprint. A retrospective will also take place so that the prodev sprint process can be continuously improved upon.
The total time commitment for participating in a prodev sprint will vary widely depending on what topic and intensity level each participant chooses to pursue. The prodev sprint may or may not be considered a full time project depending on the circumstances.
Assignment to a prodev sprint is voluntary, and team members are encouraged to express their desire to participate to the prodev Practice Lead, Jason Heaster. Efforts will be made to group people with similar prodev goals or certification requirements. There may also be occasions where team members are asked to join prodev sprints in order to build out CivicActions overall capabilities. Once assigned to a sprint, participants' project assignment schedules will be adjusted in Forecast to allocate time for the prodev sprint during that month.
Making a Plan
Previously, CivicActions had a professional development process that included regular management review of prodev plans created on trello boards. While this isn't a required practice anymore, you are still encouraged to take responsibility for your own professional development by creating a prodev plan and setting goals for yourself. If you would like help with structuring a plan, use this trello board template as a guide or ask the prodev Practice Lead for help.
Asking a Mentor, Coach, or Peer to Help
For some people, getting input from others is an important part of the professional development process. You are encouraged to seek out other CivicActioners who you think could help you achieve your prodev goals. This may be a manager, a peer, or any person who is good at something you'd like to learn. You may even wish to seek expertise outside of CivicActions to help.
If you're asked by someone else to assist with their prodev, please make time to help them out!
We have a #prodev Slack channel for prodev-related communication.
Q: How much do I get to spend on prodev each year? A: Your budget is $1,200. If you're just starting, you'll need to wait 90 days before you gain access to your prodev budget. If you're a part-time employee or under 30 hours/week, your budget will be prorated based on your working hours. Your manager can tell you more.
Q: What kinds of stuff can I spend my prodev budget on? A: Books, courses, conferences, certifications and prodev-related travel expenses.
Q: Are there any other limits on the prodev budget? A: For spending amounts over $50, you'll need to get approval in advance. Anything under $50 can be purchased without permission as long as it supports professional development goals. Receipts and expense sheets should be submitted in the usual way through Harvest, under the "CivicActions -> Professional development" project.
Q: Do I have to spend my prodev money during a scheduled prodev sprint? A: Nope. Spend it any time you like.
Q: How can I find out how much of my yearly prodev budget has been used? A: See the summary tab of this sheet: Prodev Usage 2018
Q: What if I want to spend more money than I have budget for? A: Talk to your manager if you have prodev needs that can't be covered by your annual budget.
Q: Does my prodev budget carry over to the following year if I don't use it all? A: No. Prodev budgets are "use it or lose it", so go get busy learning something!
Q: Do I have to use my prodev hours allocation during a scheduled prodev sprint? A: Nope. Spend it any way you like. But remember that focusing your efforts during a prodev sprint can make the time spent much more effective.
Appendix and Other Info
Ways to expand/improve prodev efforts:
- How do we measure prodev progress? What would be some prodev KPI's?
- Graph: hours spent for prodev, per person
- Money invested in prodev, maybe per person? Monthly?
- Participation numbers: what percentage of the company used at least 1 hour of prodev time? This could be tracked and reported on regularly, with a goal of 100% participation annually. Number of hours annual usage target TBD.
- Would also be helpful to find historical participation percentage if the data exists to calculate it
- Monthly "state of prodev" report
- How do we set prodev goals on both an individual and company-wide level?
These prodev concepts have been retired or massively changed:
- Management regularly facilitating prodev trello board reviews - for most, this does not happen anymore.
- Trello board templates for the prodev vision boards will still be available to those that find them useful
- Previous confusion about "5% time" being shared between community participation and prodev
- The 5% time allocation is meant for community participation. While community participation and professional development are conceptually intertwined, the 5% time is meant to provide guidance for community participation only. The community participation page has been split off and moved here
The target spreadsheet containing all prodev budget requests (fed in from the request form) is located here