...
This is a directory of the core LiteFarm development team. We’ve outlined working hours, who can help with what, and the best way to get in contact with each person. Please actively reference this if you’ve got a problem and you’re not sure who to talk to.
Name | Role | Availability (PT) | I can help you… | Preferred Method of Communication |
|---|---|---|---|---|
Kevin Cussen | Product Manager | M - Fr: 9AM - 5PM; 8PM - 11PM (as needed) On paternity leave portions of June - Dec 2023:  |
|
|
Tech Lead | Beginning Oct 1 2023 | |||
Design Lead | Monday - Friday 2am - 7am > 9.30am - 12.30pm (Fridays to be confirmed on a case by case) |
|
| |
Farmer Success Manager | M - F: 5:00 AM - 2 PM Graduate school calendar (days when I will be OOO):
|
|
| |
Manual Quality Assurance Engineer | M - F: 5 AM - 1PM |
|
| |
Fullstack Engineer II | M - F: 8AM - 4PM |
|
| |
Fullstack Engineer I + | M - F: 6 AM - 2PM |
|
| |
Fullstack Engineer I | M - F: 7:30 AM - 3:30 PM |
|
| |
Hannah Wittman | Professor at the Centre for Sustainable Food Systems | By appointment (via email) |
|
|
Scrum Team
...
Coming soon…
Extended Team
...
Coming soon…
Sprint Flow
Standard sprint “rituals” (AKA meetings)
...
Here’s the list of tools you’re likely to use, including descriptions, where you can access them, and whom you should speak with to get access (if you don’t have it).
Tool | Description | To Access.. | Administrator(s) |
|---|---|---|---|
Slack | Primary communication tool |
| |
Jira | Tool for running stories and communicating about stories. Our sprint workflow is described here: JIRA workflow | https://lite-farm.atlassian.net/secure/RapidBoard.jspa?rapidView=1&projectKey=LF |
|
Confluence | Confluence is where we document overarching guidance documents. Guidance documents describe the “spirit” or “rules” of something within the app without getting into individual screens, endpoints, etc. |
| |
Github | Where our code lives |
| |
Git | Distributed version control system |
| |
Figma | Tool for building and sharing UI | View-only access will be embedded into Jira stories |
|
productboard | Roadmap | https://portal.productboard.com/litefarm/1-product-portal/tabs/2-planned |
|
LucidChart | Tool for creating flows | View-only access will be embedded into Jira stories |
|
Digital Ocean | Tool to host the production and integration environments | https://beta.litefarm.org https://app.litefarm.org |
|
Github Actions | The CI/CD process for LiteFarm |
| |
LastPass | Tool for sharing credentials |
| |
Zoho | LiteFarm CRM | N/A |
|
Communications best practices
We’re a distributed team, so communications are both super-important to getting work done and maintaining a strong team culture. These are a few best practices we can recommend!
Tool | Description | Do | Don’t |
|---|---|---|---|
Slack | We use Slack for 90% of our team communication. It’s nice for discussing topics or jumping on a quick call. If you’re not a pro today, you will be soon! |
|
|
Jira | Jira is where we keep track of stories from sprint to sprint. Conversations specific to a particular story should take place on that story in the comments. |
| |
Confluence | Confluence is where we document overarching guidance documents as well as information that is helpful for anyone interested in LiteFarm. The majority of Confluence is open to the public. |
|
|
Zoom | All our sprint rituals take place on Zoom so they can be easily scheduled. Kevin and David have a full Zoom account. Otherwise, Slack is probably easier. | ||
Email is best for communications that will eventually exit the team, e.g. a question about payroll where we’ll need to cc an HR person. |
| ||
Is someone out of the office, you can try WhatsApping them |
|
First Week Reading List
These documents will prove useful in helping your orientate
...