Sprint Retro Notes
08-23-24
Things that are going well
Switching from geekbot to in person standups has been amazing
Akshat mockup for rafiki
Brennen crushing tickets and mentoring Nisarg and Diksha
Mikah working on trip in Africa
Automated testing with cypress
Ideas for improvement
READMEs
Code review → would be good to be at Ted’s level
Mono repo discussion Monday
07-26-2024
Things that are going well
Work with Diksha is going great
Intern team + Adam
Android app team
Vyshnavi images updates
Adam and Ted working together and PR review
Akshat working on Africa tool
Documentation in general
Breakouts after standups
Github automations
Ideas for improvement
Doc meeting reminder
Change story points 5 half week, 8 3/4 week, 13 week
Double issues in feedback
Issue templates redo
Github issue labels
07-12-2024
Things that are going well
Pipeline demo
Vyshnavi
Crushing tickets
Recent deployment
PR review
Trevor figuring out the multipart body
Trevor + Ravi communication and working together
Timelines
Organization of the team
Ideas for improvement
Standups are getting big
Breakouts after standups
Make standups 20 minutes
Change story points 5 half week, 8 3/4 week, 13 week
Github projects automation, especially auto add to project
Double issues in feedback
06-28-24
Notes
Once a ticket becomes scoped, assign story points
Vyshnavi agrees on having sprints being helpful
Things that are going well
As the teams getting bigger we’re having more communication
Roadmaps
Release meetings
User history
Documentation meeting
Cypress testing
Design work from game theory
Ideas for improvement
Not skipping releases, more
Should we set it up as blue green? → probably not
Automation of GitHub project
Board changes
Getting rid of sprints?
Cancel Friday meeting
05-31-24
Things that are going well
Code review for seed calc
Trevor taking on new databases
New android team
DST board restructuring
People in person in the lab
User history is going well
Documentation
Design work from game theory
Ideas for improvement
Design session for user history
Documentation
04-12-24
Things that are going well
Trevor jumping back into things after being gone for a week
The teammates being happy to hop on a call for help
DRIVES project
Seed calc stuff coming along well
Vyshnavi being autonomous and great
Brennen crushing it
Ideas for improvement
Sending messages to dst-dev
Using threads
Update geekbot to just asked if you’re blocked
Ncalc user history, new biomass model
04-01-24
Things that are going well
Intern onboarding
Add them to sprint retros and story point meetings during summer
California trip
Hire Soumya
User history API is great
Documentation meeting
Vyshnavi doing well
Ideas for improvement
Making sure we check over future work and reaching out earlier if needed
03-15-24
Things that are going well
Ted work on the BenchBot
Vyshnavi onboarding
Trevor management
In person tour of the PSB
WordPress and interns with Adam
In person standups, sticking to 15 mins
As a team we are improving and growing well
Ideas for improvement
Slackbot
Documentation, peer review
Anything to be improved on Trevor’s documentation. Maybe we can add a few documentation link sin the README
DB schema in whimsical needs updating
Next friday 3pm documentation meeting, every 4 weeks
Make a list of tools and where to go in onboarding space
Onboarding landing page could be a table of contents, if you want code onboarding click here. Add categories and link out to other pages. Adam will make table of contents page
Tuesday intern meeting merge into standup
API monitoring → Prometheus → we can expose endpoints like a crawler to auto detect metric endpoit
03-01-24
Things that are going well
Hiring and interviews
Vyshnavi did great on the coding challenge, and with feedback
Vyshnavi had a great time talking in the interviews and is interested in the tech stack
Wp-engine migration
Adam working with ameya
Seeding
Fun in interviews when we were all there
Ideas for improvement
1:30 Tuesdays, Thursdays
02/16/24
Things that are going well
Hiring
Communication, WordPress, Threads
Ideas for improvement
Slackbot
Tuesday / Thursdays 2pm → in person geekbot m / w / f
Curves and graphs from story points
02/02/24
Things that are going well
Ted working on bench bot
Trevor’s demo of seedcalc
Communication between everyone on the team
Ideas for improvement
Geekbot daily
No prs merged within 24 hours of a release
Questions
Airtable data for ncalc
Example data gets pulled from Airtable
Maybe should be pulled from airtable
11-21-23
Questions
Route for getting drainage classes
Things that are going well
Ted crushed a bunch of issues
Trevor's SDK is awesome
Time off planning
Threads
Ideas for improvement
Geekbot → set to 1pm instead of 12pm
Patch notes for seeding rate calculator
Story points assessment at the end of the year
11-10-23
Things that are going well
Threads
Ideas for improvement
Not letting threads get super old
Fix geekbot release meeting wednesday
Having a whole team meeting/get together
10-27-23
Things that are going well
dst-dev channel
styling changes
Release and patch notes
Ideas for improvement
More shared components
Ant design maybe → no grid support for accessibility (ted note)
10-13-23
Things that are going well
Ted working on the selector
Release meeting → went well
Front end styling updates
Patch notes
Story pints
Ideas for improvement
Labels
Add automation for
Bug
Feature
Documentation
Add GSAP slideshow for modernizing front end animations
Iframe out of confluence page or use api to embed in tool
09-29-23
Things that are going well
All of Kevin’s hard work
SCCC data pull
Using dst-dev as the main source of communication instead of 1 on 1
Ideas for improvement
Deployments
Defining clear release schedule
Having a running list of patch notes
https://precision-sustainable-ag.atlassian.net/wiki/spaces/DEV/pages/276987912 document to discuss
09-15-23
Things that are going well
User history is going great
Everybody is doing geekbot
Bit meeting and user history meetings went well
Ideas for improvement
Story points
Fibonacci sequence of number of days
A metric of necessity
Tracking in github
User impact and story points
Velocity 1, 2, 3, 5, 8 → higher = longer
SP → customer impact
Monday 2pm meeting for points and priorities
All communication in slack channels instead of one on one, small group. This way the whole team can contribute to the conversation and the choices are documented
Write requirement documents for projects
Define timelines documents
Get better about code review, Mikah is a bottleneck
Milad and trevor for PRs