Sprint Retro Notes

08-23-24

Things that are going well

  1. Switching from geekbot to in person standups has been amazing

  2. Akshat mockup for rafiki

  3. Brennen crushing tickets and mentoring Nisarg and Diksha

  4. Mikah working on trip in Africa

  5. Automated testing with cypress

Ideas for improvement

  1. READMEs

  2. Code review → would be good to be at Ted’s level

  3. Mono repo discussion Monday

07-26-2024

Things that are going well

  1. Work with Diksha is going great

  2. Intern team + Adam

  3. Android app team

  4. Vyshnavi images updates

  5. Adam and Ted working together and PR review

  6. Akshat working on Africa tool

  7. Documentation in general

  8. Breakouts after standups

  9. Github automations

Ideas for improvement

  1. Doc meeting reminder

  2. Change story points 5 half week, 8 3/4 week, 13 week

  3. Double issues in feedback

  4. Issue templates redo

  5. Github issue labels

07-12-2024

Things that are going well

  1. Pipeline demo

  2. Vyshnavi

    1. Crushing tickets

    2. Recent deployment

  3. PR review

  4. Trevor figuring out the multipart body

  5. Trevor + Ravi communication and working together

  6. Timelines

  7. Organization of the team

Ideas for improvement

  1. Standups are getting big

  2. Breakouts after standups

  3. Make standups 20 minutes

  4. Change story points 5 half week, 8 3/4 week, 13 week

  5. Github projects automation, especially auto add to project

  6. Double issues in feedback

06-28-24

Notes

  1. Once a ticket becomes scoped, assign story points

  2. Vyshnavi agrees on having sprints being helpful

Things that are going well

  1. As the teams getting bigger we’re having more communication

  2. Roadmaps

  3. Release meetings

  4. User history

  5. Documentation meeting

  6. Cypress testing

  7. Design work from game theory

Ideas for improvement

  1. Not skipping releases, more

  2. Should we set it up as blue green? → probably not

  3. Automation of GitHub project

  4. Board changes

  5. Getting rid of sprints?

  6. Cancel Friday meeting

05-31-24

Things that are going well

  1. Code review for seed calc

  2. Trevor taking on new databases

  3. New android team

  4. DST board restructuring

  5. People in person in the lab

  6. User history is going well

  7. Documentation

  8. Design work from game theory

Ideas for improvement

  1. Design session for user history

  2. Documentation

04-12-24

Things that are going well

  1. Trevor jumping back into things after being gone for a week

  2. The teammates being happy to hop on a call for help

  3. DRIVES project

  4. Seed calc stuff coming along well

  5. Vyshnavi being autonomous and great

  6. Brennen crushing it

Ideas for improvement

  1. Sending messages to dst-dev

  2. Using threads

  3. Update geekbot to just asked if you’re blocked

  4. Ncalc user history, new biomass model

04-01-24

Things that are going well

  1. Intern onboarding

    1. Add them to sprint retros and story point meetings during summer

  2. California trip

  3. Hire Soumya

  4. User history API is great

  5. Documentation meeting

  6. Vyshnavi doing well

Ideas for improvement

  1. Making sure we check over future work and reaching out earlier if needed

03-15-24

Things that are going well

  1. Ted work on the BenchBot

  2. Vyshnavi onboarding

  3. Trevor management

  4. In person tour of the PSB

  5. WordPress and interns with Adam

  6. In person standups, sticking to 15 mins

  7. As a team we are improving and growing well

Ideas for improvement

  1. Slackbot

  2. Documentation, peer review

    1. Anything to be improved on Trevor’s documentation. Maybe we can add a few documentation link sin the README

    2. DB schema in whimsical needs updating

    3. Next friday 3pm documentation meeting, every 4 weeks

    4. Make a list of tools and where to go in onboarding space

    5. 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

  3. Tuesday intern meeting merge into standup

  4. API monitoring → Prometheus → we can expose endpoints like a crawler to auto detect metric endpoit

03-01-24

Things that are going well

  1. Hiring and interviews

  2. Vyshnavi did great on the coding challenge, and with feedback

  3. Vyshnavi had a great time talking in the interviews and is interested in the tech stack

  4. Wp-engine migration

  5. Adam working with ameya

  6. Seeding

  7. Fun in interviews when we were all there

Ideas for improvement

  1. 1:30 Tuesdays, Thursdays

02/16/24

Things that are going well

  1. Hiring

  2. Communication, WordPress, Threads

Ideas for improvement

  1. Slackbot

  2. Tuesday / Thursdays 2pm → in person geekbot m / w / f

  3. Curves and graphs from story points

02/02/24

Things that are going well

  1. Ted working on bench bot

  2. Trevor’s demo of seedcalc

  3. Communication between everyone on the team

Ideas for improvement

  1. Geekbot daily

  2. No prs merged within 24 hours of a release

Questions

  1. Airtable data for ncalc

  2. Example data gets pulled from Airtable

    1. Maybe should be pulled from airtable

11-21-23

Questions

  1. Route for getting drainage classes

Things that are going well

  1. Ted crushed a bunch of issues

  2. Trevor's SDK is awesome

  3. Time off planning

  4. Threads

Ideas for improvement

  1. Geekbot → set to 1pm instead of 12pm

  2. Patch notes for seeding rate calculator

  3. Story points assessment at the end of the year

11-10-23

Things that are going well

  1. Threads

Ideas for improvement

  1. Not letting threads get super old

  2. Fix geekbot release meeting wednesday

  3. Having a whole team meeting/get together

10-27-23

Things that are going well

  1. dst-dev channel

  2. styling changes

  3. Release and patch notes

Ideas for improvement

  1. More shared components

  2. Ant design maybe → no grid support for accessibility (ted note)

10-13-23

Things that are going well

  1. Ted working on the selector

  2. Release meeting → went well

  3. Front end styling updates

  4. Patch notes

  5. Story pints

Ideas for improvement

  1. Labels

    1. Add automation for

    2. Bug

    3. Feature

    4. Documentation

  2. Add GSAP slideshow for modernizing front end animations

  3. Iframe out of confluence page or use api to embed in tool

09-29-23

Things that are going well

  1. All of Kevin’s hard work

  2. SCCC data pull

  3. Using dst-dev as the main source of communication instead of 1 on 1

Ideas for improvement

  1. Deployments

    1. Defining clear release schedule

    2. Having a running list of patch notes

    3. https://precision-sustainable-ag.atlassian.net/wiki/spaces/DEV/pages/276987912 document to discuss

  2.  

09-15-23

Things that are going well

  1. User history is going great

  2. Everybody is doing geekbot

  3. Bit meeting and user history meetings went well

Ideas for improvement

  1. Story points

    1. Fibonacci sequence of number of days

    2. A metric of necessity

    3. Tracking in github

    4. User impact and story points

    5. Velocity 1, 2, 3, 5, 8 → higher = longer

    6. SP → customer impact

    7. Monday 2pm meeting for points and priorities

  2. 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

  3. Write requirement documents for projects

  4. Define timelines documents

  5. Get better about code review, Mikah is a bottleneck

    1. Milad and trevor for PRs