# (pre-2024) Sprint planning & retrospective notes
###### tags: sprint planning, meeting

## Sprint Planning for Sprint 23

- Demo: Chris on Excel to database connections
- argisbinding package: Chris & Eric investigate
- create followup issues for lab-level trainings

## Sprint Planning Nov 20--Dec 3
- Demo: SmartsEditor (Eric) (again)
- Nice example of software used for chemistry (compound patterns)

## Sprint Planning Nov 6--19

#### Demo: DuckDB (Renata)

- For data too large to share/fit in memory, but simple (e.g. a single .csv file)
- DuckDB let's you connect to a "database" that is just a .csv or .parquet file on the internet

## Sprint Planning October 23--November 5
- Demo
- Eric gets approval for removing some issue templates via [this PR](https://github.com/cct-datascience/.github/pull/2) and [this PR](https://github.com/cct-datascience/organization/pull/1659)
- Switch to having repo-level issues? No org-level issues
- Retain .github repo for the org-level README
- Merged two repos
- [x] Create issue to document accounts used for Globus, etc.: <https://github.com/az-digitalag/organization/issues/113>
- [x] Create issue to keep track of Makeflow work: <https://github.com/az-digitalag/organization/issues/114>

## Sprint Planning October 9--October 22
- Kristina reviews her presentation for ALVSCE Research Workshop 2023
-

## Sprint Planning September 25--October 8
- Eric demos AZMet dashboard

## Sprint Planning September 11--September 24

- Eric not here, demo next time
- Discussion about AI

## Sprint Planning August 28--September 8

- Renata's first sprint planning meeting!
- Eric will demo AZMet dashboard for next time (including GitHub actions to deploy)

## Sprint Planning August 14--August 27

- Need demo for next time
- Organizing issues in Ready and In Progress column top to bottom?

## Sprint Planning July 31--August 13

### Demo

- Chris on mockup software
- Adobe Xd (free)

### Notes

## Sprint Planning July 17--July 30

- Next time: chris demos web interface mockup software

## Sprint Planning July 3--July 16

- Demo: To get just email addresses from a copy pasted web table. Paste into BBEdit, use cmd + F, search for .*@.* to capture email addresses, click "Extract" to get them in a new window

- Need to shut down all VMs on CyVerse. Welsch is not under our control though. Need to figure out what directories need to be copied, have Chris copy them, then ask Cyverse to shut it down

## Sprint Planning June 19--July 2

- Demo: ggplot extension `esquisse`

## Sprint Planning June 02--June 18

- Updates from Kristina on Hiring
- No demo due to time constraints

## Sprint Planning May 22--June 02

- No demo due to candidate interviews

## Sprint Planning April 24--May 07

- Next demo: ask Heidi to show Hackmd stuff

## Sprint Planning April 10--April 23
Eric to demo Mastodon. Should we join, if so what server, and for what purpose? Eric to contact Tyson about a UA server.

## Sprint Planning March 27--April 09

No demo, next time do Jessica's work breakdown (also R Consortium grant template workflow from Eric?)

Still having difficulty adjusting to new board workflow where closing an issue moves it to the closed column and not the other way around

## Sprint Planning March 13-26

Next sprint demo: Jessica's work breakdown

Demo: Eric with date range issue in Shiny

Topics:
- How much automation do we want when issues are closed or moved to "Closed" column?
- Chris: close issues in sentinel-detection
- Add something to our notes about checking issues that get continually bumped to the next sprint

## Sprint Planning Feb 27-March 12

- Migrating to GH boards
- Create new issues on GitHub project board
- Go through and move or close icebox/backlog issues
- New board questions
- Do we need review/qa category on board?
- Do we need/want "Done" and "Closed"?

## Sprint Planning Feb 13--26

- Demo: Eric demo `pins` package w/ Posit Conect

### Notes

## Sprint Planning Jan 16 - 29

- Demo: Kristina and Jessica showing newest version of fish app

Todo:
- [ ] Kristina/Jessica: Make suggested updates / bug fixes to fish app

## Sprint Planning Jan 2 - Jan 15

## Sprint Planning Dec 19 - Jan 1

- Demo: Kristina showing incubator fish app work

Discussion:
- Data science pedagogy
- Reading papers, watching talks, and summarizing in blog posts, including how we would apply it
- What limits our effectiveness in teaching?

TODO:
- [ ]

## Sprint Planning Dec 5 - Dec 18

- Demo: Keaton Wilson and css in Shiny

## Sprint Planning Nov 21 - Dec 4

- Demo: David showing GitHub Codespaces

Discussion:
- What to do when no one to train in incubators?

TODO:
- [x] (Kristina and Jessica) new issue for fish incubator

## Sprint Planning Nov 7 - 20

- No demo

Review TODO:
- [x] Everyone move issues they are not working on out of Ready to Backlog channel

Discussion:

- Independent research for credit as an alternative when incubator project isn't a good fit
- Way for us to get credit for our work
- Let's discuss more next time

### TODO

- [ ] Ask David about intentions behind Darpa issue #156
- [x] Schedule Darpa meeting to figure out how to enable ED2 runs and prep MSR
- [x] David update time zone for sprint planning calendar event

## Sprint Planning Oct 23 -- Nov 6

### Notes
- Groom Ready issues by sorting oldest first
- No demo!
- Discuss RStudio/Posit Cloud
- Advantages of teaching on cloud/Binder
- Having dependencies installed
- Have skeleton / example code, data already loaded
- Not everyone has admin access on laptops to install packages (e.g. govt owned)
- Pair programming, you can poke around in student's RStudio sessions
- Disadvantages
- People having to install dependencies themselves later on to work locally
- Need to set up GitHub integration with each project
- Don't have the full "new project" dialog box
- Does UA have a license? (no) What are the limits for number of users/amount of compute?

### TODO

- [ ]

## Sprint Planning Oct 9 -- Oct 23

Demo: Eric showed `usethis` functions for setting up an R package

## Sprint Planning Sept 26 -- Oct 9

Kristina will demo API

## Sprint Planning Sept 12 -- Sept 25

Demo: Eric showed slides in Quarto and `usethis::use_course()`

### Notes
- Should we create a post-incubator project assessment to be completed as part of the wrapup?
- https://github.com/cct-datascience/organization/issues/1097

## Sprint Planning Aug 29 -- Sept 11

- [ ] **Kristina** TODO send out workshop announcement
- [ ] **Everyone** should write up a summary
- [ ] David to do a workshop on APIs Sept 28 11-1
- [ ] Jessica --> websites, Oct 26 11-1
- [x] Eric --> targets, First week of Dec 7, 11-1

Demo: Kristina and David ED2 emulator with `tidymodels`

## Sprint Planning Aug 15 -- Aug 28
Demo: Jessica's ESA talk

### Notes

- Jessica and Kristina to figure out workshop stuff
- Kristina to send out myemma next week

## Sprint Planning Aug 1 -- Aug 14

- no demo
- just Jessica and Eric

## Sprint Planning July 18 - July 31

### Demo

Targets (Eric):
- https://github.com/cct-datascience/targets-demo
- Looking for feedback on whether and how to teach workshop on this
- Definitely should teach, need to figure out best summary/context
- Would be good to wait until after fall cohort of reproducibilty short course

### Notes

## Sprint Planning July 4 - July 17

### Demo

Rainman (Jessica):

- Soil water release curves
- How to best document Shiny app?
- Fit a GAM to deal with poor performance at low water potential?

Next time Eric---`targets` package

### Notes

- Group needs to schedule:
- [x] Bridges day 2 (October 14th or September 30th)
- [x] Next quarterly review meeting---invite ARDN manager? (schedule around Bridges day 2)
- Jessica and Eric should chat about GAMs some time
- Use admin email account for Zoom for workshops?
- New CCT google drive can't share subfolder
- September workshop? (could be Eric)
- Ask Andrew in SNRE to demo app for field data entry?

## Sprint Planning June 20 - July 3
### Demo
Kristina showcasing Vmapper
Next time: Jessica + VG functions

### Notes

- [x] David and Kristina meet tomorrow to work on ARDN pipeline
- [x] First week of sprint, plan for up to 1.5 hours of code review, start with reviewing project board
- [x] Edit OSF - incubator hour under the incubator tab
- [x] Follow up with Kelli re: Sankey dashboard

## Sprint Planning June 6 - 19

### Notes

- [ ] Schedule incubator/pull request hour to start enforcing reviews of each other's work

## Sprint Planning May 23 - June 6

### TODO

* [x] BRIDGES post workshop follow up email

## Sprint Planning March 28 - April 10

### TODO

- [x] Kristina and David to meet about ICASA terms, also review events stuff
- [x] Kristina and David meet to determine next steps w/ rangeland docs
- [x] Jessica & David --> PFT Priors
- [ ] Put quarterly review meeting on calendar
- [x] David discuss funding with BRIDGES folks

### Notes

- Quarterly review meeting & Hatch Funds proposal discussion
- Split meeting into two?
- Do 1 hour proposal planning next week?
- Monday April 4
- Incubator structure programming, deadlines, informational meetings, round 1 proposals (them) vs. round 2 scope of work (us)
- Put AgBase project into complete on incubator board once Chris is done with this part
- Split proposal into proposal and scope of work; getting collaborators to do more work

## Sprint Planning March 14 - March 27

### Notes
- [x] Is AgBase a Incubator Project? It's on the board and should be removed is it isn't
- will meet w/ Fiona before Chris takes off, then move to complete
- [x] Define Proposal Stage(s) for the "C diff" proposal, and all the others
- [x] Jessica and Kristina: schedule workshop series meeting to decide on notes and assessment

## Sprint Feb 28 - March 13

### TODO

- [x] Jessica: create issue for helping Debasmita include new sites for spring forecasting

## Sprint February 14 - 27
- Lead: Kristina
- Scribe: Chris
- Timer: Jessica

### Demo - Jessica
- Demo'ed Shiny app of RainManSR data

### Notes
- Reviewed Incubator Projects
- Geobacklight was moved to backlog
- AZMet QA/QC: next step is to ask Jeremy about this; moved to backlog
- Rangeland Restoration: received an email with the data
- we should be able to perform the task (doesn't require domain expertese)
- next step is creating a planning document - complements a proposal(?)
- Reviewed current Sprint issues

### Action Items
- [x] Group: Discuss continuing with demos at start of meetings
- will continue with demos
- [x] Group: Who will demo on next Sprint Planning meeting?
- [x] Group: Talk about the Incubator Process (when, do we need to, create a planning document and how does that relate to a proposal)
- [ ] Group: Discuss what to cover when holding Sprint Planning vs. Sprint Review
- We discuss how issues are going, when do we look back over how the Sprint went (and do we do this)?
- [ ] Schedule meeting to do backlog grooming

## Sprint late Jan 2022

- Lead: David
- Scribe: Kristina
- Timer: Chris

### Notes

- First (recent) time trying sprint planning earlier in the cycle

## Sprint December 20 - January 2
- Lead: Kristina
- Scribe: Chris/Jessica

- [ ] Review old issues that should be closed but aren't
- [ ] David: Finish Organization:#710
- [ ] Move issues to Backlog and Icebox as needed
- [ ] Outreach hour - clean up issues on Zenhub board
- [ ]

## Sprint December 6 - December 19
- Lead: David
- Scribe: Jessica

Demo
- None

- [ ] Everyone review and move/close new issues

---
## Sprint November 8 - November 21
- Lead: Chris
- Scribe: Kristina

Demo

- [ ] Everyone review and move/close new issues

## Sprint October 25 - November 7

- Lead: Jessica
- Scribe: David
- Timer: Kristina

Demo: Julian exosphere next Monday

Next demo: Kristina R package

### New issues to create
- [ ] Jessica, followup for voc time series decomposition
- [ ] Jessica + Kristina to meet/plan about the Shiny app

### Follow-up discussions and meetings
- [x] Blog post tweet & plan for additional blog posts about CVPPA, Agave paper
- [x] David to make issue for next Writing Hour (added as a writing hour task)
- [ ] Everyone: move ready issues to backlog or icebox if appropriate
- [ ] David to review and Jessica to send out survey (data science makeover)

## Sprint October 11 - October 24

- Lead: Kristina
- Scribe: Jessica
- Timer: David

Demo: Kristina demo R package

Next demo: Julian exosphere

### New issues to create
- [x] Survey for Rainman data makeover (Jessica)
- [x] Followup issue for VolCal R package (Kristina)
- [x] Write up data needs/describe plan for psent3 (Jessica)

### Follow-up discussions and meetings
- [x] Teaching ESA materials starting in January spread out across 2-3 months and applying this to people's actual research projects (maybe targeting BRIDGES group?)
- great idea; will wait on survey
- Jessica reached out to Susan (SNRE) and Mery (ENVS) to gauge interest among grad students
- [x] Teach one more workshop by end of year? Maybe SQL followup one?
- David will teach about time series Dec 1
- [ ] Everyone: move ready issues to backlog or icebox if appropriate

## Sprint September 27 - October 10

- Lead: Jessica
- Scribe: Chris
- Timer: Kristina

Demo: Jessica's rangeland project figures

Next demo: Kristina demo R package - as much as what's done

### New issues to create
- [x] jessica create org. ag. figs as svg (or high res)
- [x] jessica check in w/ Rainman group about follow up / check in
- [x] Jessica Followup for PEG archiving #72

### Follow-up discussions and meetings
- [x] david: Quarterly review scheduled for October 15
- [x] What to teach for Oct workshop? - Kristina doing Rmarkdown reports, ask Tyson, Ryan, or Michael if they'd like to help; doing Oct 27
- [ ] Teaching ESA materials starting in January spread out across 2-3 months and applying this to people's actual research projects (maybe targeting BRIDGES group?)
- [ ] Teach one more workshop by end of year? Maybe SQL followup one?

## Sprint Sept 13 - Sept 26

- Lead: Chris
- Scribe: Kristina
- Timer: Jessica

Demo: David showing his and Jessica's figures for the organic farm incubator project

Next demo: Jessica's rangeland project figures

### New issues to create

- [x] Chris: revise combined incubator/office hours poster

### Issues that need to be broken up into smaller tasks

- [ ] ???

### Follow-up discussions and meetings that are proposed

- [x] David: Invite Mark Borgstrom to quarterly review meeting
- [x] David: Invite Sara Willis to quarterly review meeting
- [x] How to deal with repo ownership for incubator projects, e.g., volatility pipeline
- item for Quarterly meeting?
- [x] David and Kristina meet Monday about Brapi/ARDN

---

## Sprint August 30 - Sept 12

- Lead David
- Scribe Julian
- Timer Chris

Demo: Julian showing Exosphere workflow functionality

- [x] (whom?) Add review of incubator board to sprint review (what's the time limit on this?) 10 minutes

### New issues to create

- [x] Julian create your issues and fill out
- [x] Julian make #356 an epic and break out sub-issues. 1) coverage testing using docker 2) combine test suites
- [x] https://github.com/tyson-swetnam/cereus/issues/12

### Issues that need to be broken up into smaller tasks

- [x] Jessica and David to break up organic ag task for next sprint

### Follow-up discussions and meetings that are proposed

- [ ] Jessica and David to schedule regular working meeting on Bayesian workshop
- [x] David schedule and prepare for next quarterly
- [x] choose date: Oct 5
- [x] review process
- [x] toggl and / or epics for projects
- [x] update our process https://osf.io/tzmhp/wiki/Sprint%20Meetings/
- [x] review incubator project wiki
- [ ] Kristina, Jessica, David to meet to organize how to organize PEcAn output

## Sprint August 16 - August 29

Lead: Jessica
Timer: Kristina
Scribe: David

DEMO

- Jessica results from rangelands model incubator project
- [ ] David and Kristina meet to discuss volatility R package
- [x] Kristina put volatility code on github [issue](https://github.com/az-digitalag/organization/issues/585)

- [x] update wiki so that we look at charts on Monday
- [x] David and Jessica to follow up on pairwise comparison method
- [x] David, Jessica, Kristina to meet about DARPA phase 3 plan
- [x] David write issue - how to link WebODM outputs to DE apps (FieldImageR; GIS remote desktop)

- [x] Jessica to schedule meeting with Jeanette

## Sprint August 2 - August 15

Lead: Julian
Timer: Jessica
Scribe: David

DEMO

Julian - exosphere workflows, can be interactive like Binder
David - Proposals repo in az-digitalag, private projects with kanban boards for managing proposal led by David. Julian says each project can have its own team.

TODO

- [x] David write issue to follow up on https://github.com/az-digitalag/organization/issues/570
- https://github.com/az-digitalag/organization/issues/590 and https://github.com/az-digitalag/organization/issues/591
- [x] Jessica and David follow up about Jeanette's NCEAS workshop
- [x] Jessica to schedule meeting with David about model convergence issues

- [x] Jessica and Kristina to chat about ED2 workflows - ready for next Sprint?

## Sprint July 19-August 1
Lead: Chris
Scribe: Jessica
Timer: David

- Demo: Chris presenting data lakes

### TODO

- [x] Jessica to schedule meeting with David about model convergence issues

## Sprint July 5-18
- Lead: Kristina
- non-Lead: Jessica

TODO

## Sprint June 7-20

- Lead: Jessica
- Timer: Julian
- Scribe: David

Kristina presented her rangeland docs work / NLP w/ tidymodels

### TODO

- Jessica add issues for next sprint
- [ ] follow up to bayesian workshop
- [ ] RCN proposal
- [ ] rangeland restoration
- [x] Julian to post database of TERRAREF data
- Created issue: <https://github.com/az-digitalag/organization/issues/541>
- [ ] David create new issues to follow on https://github.com/AgPipeline/issues-and-projects/issues/470
- [ ] David schedule incubator information informational session
- [ ] David start backlog grooming and using the backlog with prioritized issues
- [ ] Send out ALVSCE survey on workshop ideas / interests to collect names and clarify needs

## Sprint 61

- Anarchy sprint meeting w/ Kristina, Chris, Jessica, and Julian
- Lead: Kristina
- Scribe: Jessica
- Timer: Chris

Demo: Jessica/Chris showed how to get a url from Dryad - less intuitive than it seems!

Reports will be done on following Monday, after sprint is over

TODO:

- [ ] Plan June workshop? Maybe Intro to Databases by Julian
> I have a lot to do before going on vacation, and I will need more time. [name=julianp-diag]
- [ ] Sounds like many folks are out in July (including Jessica, Chris, Kristina, and Julian), so maybe no July workshop

## Sprint 60: May 20 2021

- Lead Jessica (sub for Julian)
- Timer: Kristina
- Scribe: Chris

Question for group: Do we need a method for how to add and remove repos from Zenhub?
- A: Add repos until/if a problem occurs

- New sprint system adds new sprint if issue isn't closed by end of last sprint
- Decided to move this meeting to Friday's AM to work around this issue
- Our ways of tracking work that was done may change due to our migration to ZenHub sprints from Milestones

Demo: Chris drone UI
- David has questions regarding the UI vs. what CCT has put together for running CyVerse apps

TODO
- [ ] Chris to review [agpipeline/issues-and-projects#470](https://app.zenhub.com/workspaces/ua-ag-data-science-5a57a3198339f11ba1c85775/issues/agpipeline/issues-and-projects/470)
- [x] Chris or David create meeting to review ODK
- [x] Chris or David create meeting to review UI
- [ ] David to reschedule sprint meetings and writing hour
- [ ] Jessica to update OSF for new sprint meetings
- [ ] Chris: update #399 for results with Cookie Cutter
- [ ] Kristina: take care of #439 after Brapi meeting
- [ ] Everyone: review Ready issues and move as appropriate

## Sprint 59

Lead: Chris
Scribe: Kristina
Timer: Jessica

Demo: Kristina on [Binder](https://mybinder.org/)

Notes:

- Using sprints instead of milestones in Zenhub now. They basically work the same, have different icons and different drop down menus. Reports should use points, etc. from both sprints and milestones

TODO:

- [x] David: Backlog grooming (added issue)

## Sprint 58

Lead: David
Scribe: Julian
Timer: Chris

Demo: David talking about food security project

Notes:

- Using milestones for Sprint 58, and Chris will set up ZenHub sprints for Sprint 59

TODO:

- [x] Chris: Set up ZenHub sprints (create an issue for Sprint 58 to do this)
- [x] Group: Decide on name of ECSS/Incubator initiative ("Incubator")
- [ ] tweets
- [ ] about videos
- [ ] TERRA REF phytooracle workshop
- [ ] ODDPIG this Friday
- [ ] Kristina's presentation (also curate on OSF outreach)
- [ ] NEON workshop recording
- [x] Jessica: _'Bother'_ David about 2-pager

## Sprint 56

Lead: Julian
Scribe: Jessica
Timer: David

Demo:

Notes:
- Move Sprint 57 to sprint rather than milestones?
- Schedule quarterly review meeting for April 1, 8 am to 3 pm.

TODO:

- [ ] David: Followup to 378, 380
- [x] David and Jessica follow up re: Joel's data plan #381
- [ ] Team: discuss pros/cons of moving to Zenhub sprint functionality
- [ ] Julian: 3 followup issues
- [x] Sparcd
- [x] phytooracle survey (I think this might be done, will check)
- [x] TERRA REF data archiving
- [ ] Julian/Chris: More disk space on Welsch: either expand current user-data volume on Welsch, or add a new volume - we don't manage the OpenStack instance, so will need to ask CyVerse to resolve
- [ ] Julian or Kristina create followup to 328 () - review ED2 HPC vignette
- [ ] Kristina follow up w/ Tyson about automating EFI forecasts
- [ ] For #289, can David run the new temp_comparison?
- [x] Schedule meeting about USAID, David and Jessica
- [ ] David to review Chris's draft
- [x] Jessica schedule meeting with David on adding BBL params to BETY

## Sprint 55

Lead: Julian
Scribe: Chris
Timer: Kristina

Demo: Chris
- Run DPP on CyVerse
- Also updating us on current status

Notes:
- Moved Jessica's done to closed and moved remaining ones to Sprint 55
- Moved previous reviews' outstanding TODO's to this date
- Proposed: Move to automated sprints for one or two cycles to see if we like them
- BETYdb-YABA, genophenoenvo milestones were not closed when Julian tried to close the Sprint
- Kristina want to store 50+GB of data on Weslch, we will need more space on Welsch

TODO

- [x] Jessica: Plan your next sprint
- [x] Kristina: Get issue priorities from David for Sprint 55 (particularly ED2 next steps beyond forest runs)
- [x] Julian: write issues for Sprint 55
- [x] CEREUS
- [x] Julian: Create issue for reviewing Office Hours announcement
- <https://app.zenhub.com/workspaces/ua-ag-data-science-5a57a3198339f11ba1c85775/issues/az-digitalag/organization/401>
- [x] Kristina: schedule ED2 documentation meeting w/ Julian

## Sprint 54

Lead: Kristina
Scribe: Jessica
Timer: David

Demo: Kristina
- ED2
- Update pecan.xml (increase to 2 pfts)
- ED2 in files contains model-specific inputs
- section to run on HPC
- Mostly run locally until PEcAn.remote, then run on HPC, creates new folders, then copies back over to Welsch when done
- post-processing with PEcAn function to convert h5 to netcdf

Notes:
- Demo for next meeting 3/1: Chris on DPP
- In charge of office hours 2/16: 8-9 Chris, 9-10 Jessica

TODO:
- [x] Jessica sentinel detection follow up / submit PR for 258
- [x] Jessica follow up on 280
- [x] Kristina: make MSR
- [x] Schedule David + Jessica meeting on running BioCro
- [x] Schedule long writing hour for D + J + K

## Sprint 53

Lead: David
Scribe: Chris
Timer: Jessica

Demo: David
- Using music to visualize data
- Uses Sonic Pi for platform (RUBY)
- Has good help

Notes:
- David: Is the 10:00AM time OK for everyone as well as the 9:30 meeting?
- It appears OK for everyone
- We'll keep the 10:00 - 11:30 AM time
- Kristina will demo next meeting
- Demo-ing ED2

TODO:
- [x] Jessica: contact Joel regarding work item(s)?
- [x] Chris: motivate David about ODDPIG (Open Drone Data Processing Interest Group)
- [ ] David: Add ticket to review PR: issue Organization/372
- [ ] Kristina: agrees to review group-website PRs

## Sprint 52

Lead: Kristina
Scribe: Jessica
Timer: David

Demo: wait for Julian's exosphere talk

TODO:
- [x] Kristina to ask Brian and/or Ishita for a PR review/code walkthrough meeting
- [x] Jessica to meet with Kristina re: how to build on high light BioCro run to add greenhouse and outdoor treatments

## Sprint 51

Demo: Jessica logistic regression model

TODO
- [x] Update roles - remove Emily and Ryan
- [x] Kristina, Jessica, David Choose parameter for Vcmax

## Sprint 50

OYO no meetings

## Sprint 49 Review/50 Planning Dec 19

Lead: Jessica
Scribe: David
Timer: Chris

Demo: Kristina

TODO
- [x] Jessica follow up for 246
- [x] Jessica move 252 to next sprint
- [x] Kristina assign NEON PR to Jessica for review

## Sprint 48 Review/49 Planning

Dec 7 2020

Lead: Kristina
Scribe: David
Timer: Jessica

Demo: David showed [Canopy Cover app from CCT](https://data-science-clone.d232c7gv9yqi8q.amplifyapp.com/)

TODO:
- [x] david add PR reviews to next sprint
- [x] kristina - follow up w/ others on review of NEON datasets

will have
sprint 49 review on Dec 18th
sprint 50 is every person for themselves :-)
sprint 51 planning on Jan 4

## Sprint 47 Review/48 Planning

Lead: Chris
Scribe: David
Timer: Jessica

TODO:

- [x] David and Chris follow up with Rosa
- [x] Jessica Create issue to write protocols for Danforth

## Sprint 46 Review/47 Planning

An attempt at combining the two sprint meetings

**Roles**
- Leader: David
- (Self-appointed) scribe: Kristina

### Notes
- Want more demos/showing work from each person
- More meeting time dedicated to demos?
- Demos aren't always connected to what we're actually working on
- Or maybe expand each person's review to discuss more generally about what we're doing and go beyond just moving around issues
- Show what you're working on (something you're proud of from the sprint?)
- Do review before planning? Seems like lots of groups do it this way
- Use review to do planning
- Do them both on Monday one after the other, maybe with a short break between
- How much time?
- 45 minutes, short break, then 30 minutes?
- First attempt at this
- Everyone did just reviewing part, going over sprint 46 tickets and progress/challenges/etc., moving issues to closed and changing points if applicable
- Should include reviewing issue resolution comments
- Close milestone and review reports
- 15 minute break
- Everyone went over their issues for the next sprint (planning part), including number of points (check total in velocity tracking report)
- It's okay to create an issue for reviewing a pull request
- Need to decide/track times for different parts of meeting

**TODO**
- [ ] Emily: create followup issues for DPP Hackmd work #339
- [x] Jessica: ticket for adding SLA to database
- [ ] Emily & David (& Kristina): schedule meeting for walkthrough/live coding of README for terra ref data
- [x] Kristina: figure out which initial sentinel vignettes PR for Jessica to review (see Jessica's issue #217)
- [ ] Kristina: write followup ticket for review of NEON curation script #117
- [ ] Jessica: add some documentation for progress in #218, then create a followup
- [ ] David: move new issues to appropriate categories
- [ ] David: Update OSF page for new format

## Sprint 45 Review
**Roles**
- Leader: David
- Scribe: Jessica
- Timer: Kristina

**Demo**
David on agave global maps
- 4 km grid
- Simple model in NetCDF, R not necessary
- Light, ppt, and temp response parameters -> EPI (environmental productivity index)
- Run over mean monthly environmental values, too large to run on memory
- Ultimately completed with netcdf tools, much faster than R/SQLite
- Visualized with different projections
- Diff between absolute minimum and mean monthly minimum is greater at high latitudes

**TODO**
- [ ] Jessica: move issues to done/closed as they are completed

## Sprint 44 Review 2020-10-12

**Roles**

- Leader: Ryan
- Scribe: Kristina
- Timer: Emily

**Demo**
Emily on fuzzywuzzies (Python package for fuzzy matching)

**TODO**

- [x] Kristina: create issue for reviewing regional runs PR
- [x] Jessica: create new issue to replace epic
- [x] Jessica: find/recreate lost issue
- [ ] Emily: send links to what needs to be reviewed to David / assign issues for him to review any tickets in QA

## Sprint 43 Review 2020-09-28

Location today: Kristina's Zoom [Room](https://uasystem.zoom.us/my/kristinariemer)

**Roles**

- Leader: Emily
- Scribe: Kristina
- Timer: Chris

**Demo**
Kristina on regional runs/gif of biomass

**TODO**

- [x] Emily: close remaining issues for sprint 43 and create follow-up tickets
- [x] David: close/move sprint 43 issues
- [x] Chris: close/move Jacob's sprint 43 issues

## Sprint 42 Review 2020-09-14

- Leader: Chris
- Scribe: Ryan
- Timer: Emily

Demo: Ryan
Autonomous Greenhouse Seminar Notes (And fun md/atom hacks)

PDF in slack channel of notes from seminar

TODO

- [x] Kristina: Check issues and move done to closed
- [x] Jessica: Check issues and move done to closed
- [ ] Julian: break up tickets into smaller tasks

## Sprint 42

- Leader: David

## Sprint 41 Review 2020-08-31

- Leader: Kristina
- Scribe: Emily (thank you Kristina for your help)
- Timer: David

Demo: Chris
Software Testing Levels

- Unit tests
- First level
- Testing individual functions
- Integration testing
- Next level
- Testing relationships between functions
- Systems testing
- Testing bigger goals/purposes of program
- Acceptance testing
- Similar to systems testing
- Less test case drive, more production/real data driven
- What is done right before pushing to production
- Examples from transformer-plotclip repo
- Unit tests: one for failure of function and one for success
- Integration test is on a function that calls other lower level functions, to read in plot file
- System test example is making sure an entire app within a Docker file is doing what it's supposed to be
- Code coverage for how many lines of code are covered by tests (codecov.io)
- Distinguishing between different types of tests is context dependent
- Can make analogy to writing an essay

TODO
- [x] Emily: Clarify title and description of tasks for tickets overall (#260 as an example)
- [x] Emily: Prioritize creating tall format tables for Ryan (#100)
- [ ] Should David have a placeholder `Herding Cats` ticket for issues that come up during the Sprint? :cat2:
- [x] Chris: move Jacob's issues to corrrect pipeline
- [x] Ryan: close `Done` tickets when able / finger is working
- [ ] Everybody for next Sprint meeting: make sure that Sprint 41 looks like our other Sprints (velocity tracking)
- [x] Emily: Finish In-progress tickets
- [ ] Chris: Move Review / QA tickets when done

## Sprint 42 Planning 2020-08-27

- Ryan Leader
- David Scribe
- Chris Timer

Retrospective demo: Chris will present different types of testing

## Sprint 40 Review 2020-08-17

- Leader David
- Scribe Chris
- Timer Ryan

#### TODO
- [ ] David: review/update Templates and Contributing Document
- [x] Emily: finish up issues for Sprint 40
- [ ] Chris: Mark drone-makeflow as Alpha_1.0
- [x] Chris: Move/Close Sprint 39 issue that's still open
- [x] Julian: Move Sprint 40 issue to next sprint or have it broken down
- [ ] All: Review "Ready" queue for issues that are out of date, or can be moved to Backlog or Icebox
- [x] Kristina: get down to reasonable number of points for sprint 41

#### Notes
- Julian presented a way to Provide a UI for command line apps that we develop
- Answers: "How do we go from using ArgParse to parse command line arguments to a GUI"
- use Gooey to provide UI https://pypi.org/project/Gooey/
- Gooey provides widgets to make input easier to apply to UI
- Gooey uses annotations to do its magic so the original code is still in place (although modified)
- Able to use/write wrappers making use of Gooey input features: such as file picker instead of text input
- Question (David): is there a way to have a separate function for the UI that doesn't require changing an existing function? Answer: It's possible by using a separate function
- Question (Kristina):[question lost by scribe] Answer: it's possible to separate UI components to make modifications and arrangements easier
-

## Sprint 41 Planning 2020-08-13

- Leader: Chris

#### TODO

- [x] Ryan: add content discussed with David to Google Sheet
- [ ] ~~Chris: check out David's review of #174~~ (Issue number is incorrect - unable to resolve)
- [x] Julian: close multiple users issue?
- [x] David: go through Ready issues and move some to icebox

## Sprint 39 Review 2020-08-03

#### Roles

- Leader: Ryan
- Scribe: Kristina
- Timer: Emily

#### TODO (this mtg)

- [x] Kristina: get sprint points down to ~15

#### TODO (outstanding from previous mtgs)

- [x] Emily - update OSF: add notes from planning meeting
- [x] Jacob/Chris: assign and estimate issue for
- [ ] Julian: Split <https://github.com/danforthcenter/sentinel-detection/issues/152> into a follow-up issue for multiple users
- Note: The multiple user issue can wait until after ED2 is working

#### Notes

- Demo from Emily on OSF
- Each of us has profile pages
- Possible integration with citation software (Mendeley, Zotero?)
- Example project on Manatee Mortality
- Use OSF as greater source of info about our projects
- Component = a new page that is basically its own project; the symbol tags don't have any functional meeting
- Linked projects can have their own GitHub repos (limit of one repo connected?)
- Each person goes through and reviews their issues from the last sprint
- Include overall sprint, any problems encountered or anything notable
- Open up 1 or 2 issues to show issue resolution
- Discuss if points were accurate for Done issues
- We should change point estimates if they were inaccurate at this point
- Move issues to Closed
- Always have David review Zenhub reports
- Need to remind Julian to check this document for TODOs relevant to him

## Sprint 40 Planning 2020-07-30

- Leader: Kristina
- Scribe: David

#### TODO

- [x] Kristina, David & Julian: Catch up about ED2 and HPC tasks for Sprint 40

## Sprint 38 Review 2020-07-20

#### Roles

- Leader: Emily
- Scribe: David
- Timer: Chris

#### Demo?

none today - will add this to tasks to do for sprint planning

#### TODO

* [x] David update OSF
* [x] sprint planning - identify who will give demo at review
* [x] update new review/ planing protocols
* [x] at review, ea. person shares their own screen when going through their work
* [x] David: backlog grooming
drone data transformer_class issue #156
* [x] Chris create new issue for david to review 177 and 173 - sqlite databases
* [x] Chris create new issues for pipeline PR reviewers
* [x] Emily: schedule mtg w/ David to review plans / outline
* [x] Kristina: create followup issue for repo reorg PR
- [x] Emily: make link to follow up issue with NEON data
- [x] Emily: open pull request for Clemson data?? (not sure exactly what this means, but will be adding all cleaning notebooks to terra-ref repo soon - currently in my for-data-publication repo)

#### Notes

* we are trying an approach where every person reviews highlights from the last sprint and provides a quick overview of the next sprint: using the 15 minutes assigned to "Reviewing issues" - comes to <3 min per person
* Chris: forgot to set timer, so no timing - he believes he went over 3 minutes
* 6+ min, 3+ min, 3.5+ min, 1+ min, 2+ min
*

## Sprint 39 Planning 2020-07-16

#### Roles

- Leader: Kristina
- Scribe: Chris
- Timer: Ryan

#### Planning for 15 minute planning

1. According to notes [Emily posted](https://cyverse.slack.com/archives/CQAATRMCM/p1594915305002500) we continue doing what we've been doing
2. Hold meetings at 9:50 - 10:05 AZ time
3. Don't need a timer or scribe
4. Give overview of current and next sprint
5. Report exceptions (what didn't go as expected, points that were incorrect, etc)
6. Leader keeps conversations within time limits and selects who goes next
7. If people are not at meeting they need to be ready at Sprint Retro

#### What to discuss
- How current sprint is going, number of points, why items were moved, blocking factors, what don't expect to finish, ...
- How next Sprint is planned: total points, areas of interest, ...
-

---

## Sprint 37 Review 2020-07-06

#### Roles
- Leader: Emily
- Scribe: Ryan
- Timer: Kristina

#### TODO

- [x] Ryan: ask Julian about Docker deployment on Exosphere. Getting `PSOCK` errors on the DE with R library `parallel`
- [x] Chris: close #67 and create a new issue for reviewing pull requests
- [x] Chris: similar for issue #161
- [x] Kristina: create followup issue for improving OpenStack Pecan documentation
- [x] Chris: link to follow up issue ~~#26~~ #146 for TERRA-REF workbench migration
- [x] Chris: Drone pipeline issue #70 link PR or comment on/link issue resolution in issue
- [x] Chris: update issues in review/QA
- [ ] Julian: divvy up TERRA-REF data archiving between managed/scripted
- [x] Julian: push PR to pipeline-admin from local repository
- See PR 88 on admin repo
- [x] Emily/Ryan/David/Tyson: Follow up on NEON site selection

#### Notes

- Kristina demo'd using Docker on Exosphere
- Don't need an SSH key if it is stored in your keychain, you would just enter a passphrase for the server
- Documentation for running Exosphere is on the PeCaN OSF [page](https://osf.io/a4p9n/wiki/PEcAn%20Docker%20Dev%20Env%20on%20OpenStack)
- Is it possible to create a new volume? or increase VM instance RAM/CPU?
- Snapshot server image, and relaunch as a new instance with larger volume/CPU power/RAM
- Create server, choose root disk size, can be 100gb+ etc.
- Eliminates issues with install sizes

---

## Sprint 38 Planning 2020-07-06

#### Roles
- Leader: Ryan
- Scribe: Kristina
- Timer: Emily

#### TODO

- [ ] Chris: review todos from last meeting
- [ ] Jacob: add point estimate to #60
- [ ] Kristina: add everyone to quarterly meeting issue

#### Notes

- Skipped checking state of board for sprint 37 because we'll be doing sprint review within an hour

---

## Sprint 38 Review 2020-06-22

#### Demo
Ryan Using Rstudio interactively on Cyverse DE w/ GitHub integration

#### Roles
- Leader: Kristina
- Scribe: Emily
- Timer: David

#### Notes

- Chris' ticket #68 was moved to Backlog

#### TODO

- [ ] Chris & Jacob: Resolve remaining issues in Sprint 36
- [ ] Chris: Summarize decision from Issue [#69](https://github.com/AgPipeline/drone-pipeline-environment/issues/69) in the Documentation
- [ ] Chris: Comment on Issues #68 and #154 on what was done to complete tickets
- [x] David: create password to ADC to share with Kristina
- [x] David & Kristina: Discuss GSOC before Friday (6/26)
- [x] Kristina: Add details to #125
- [ ] Jacob: Why was PR for Issue #65 closed?
- [ ] Chris & Jacob: Close Issue #64 because we aren't sure
- [x] David, Kristina, & Julian: Follow up on. . . what Julian should be working on?
- [ ] Jacob: Assign points to Issues #72 and #60

## Sprint 37 Planning 2020-06-18

#### Roles
- Leader: Emily
- Scribe: David
- Timer: Chris
- Sub: Ryan

### TODO

* [x] David Add to Quarterly Review
* Revisit whether or not to change story points at Sprint Retrospective; Chris will post links to relevent guidelines
* One group's [reason](https://agilevelocity.com/why-we-dont-re-estimate-story-points/) for not changing points
* Same thoughts from [Attlassian](https://community.atlassian.com/t5/Jira-questions/Adjusting-Story-Points-during-active-sprint/qaq-p/997616)
* A [conversation](https://www.scrum.org/forum/scrum-forum/5467/updating-estimates-during-sprint) about updating estimates
* [ ] Chris to update Jacob's tasks

### Notes

* Discuss candidate for Darpa position

## Sprint 35 Review 2020-06-08

Roles:

* Leader: David
* Scribe: Chris
* Timer: Ryan

* Demo: Chris presenting pylint github action

### TODO

- [x] Emily: Link to new Mentorship documentation [ticket](https://github.com/az-digitalag/organization/issues/231) once it's created (in closed Issue [#178](https://github.com/az-digitalag/organization/issues/178))
- [x] Chris: Make sure Jacob's Sprint 35 tickets have PR links
- [ ] All: Formalize and document mechanism for closing tickets that aren't worked on (remove points? commenting? etc.)
- [x] @julianp-diag: Please complete Sprint 35 issues
- [x] All: Revisit whether or not to change story points at Sprint Retrospective; Chris will post links to relevent guidelines
* One group's [reason](https://agilevelocity.com/why-we-dont-re-estimate-story-points/) for not changing points
* Same thoughts from [Attlassian](https://community.atlassian.com/t5/Jira-questions/Adjusting-Story-Points-during-active-sprint/qaq-p/997616)
* A [conversation](https://www.scrum.org/forum/scrum-forum/5467/updating-estimates-during-sprint) about updating estimates
* An article on [common mistakes](https://medium.com/serious-scrum/12-common-mistakes-made-when-using-story-points-f0bb9212d2f7) around points
- [x] Kristina: contact Julian about running work on OpenStack machine instance
- <https://github.com/danforthcenter/sentinel-detection/issues/136>
- [x] David: document how we're assigning points into OSF documentation

### Notes

* David's Q's:
* Can different YAML files make use of previously setup environment
* Not between YAML files, can have multiple jobs in the same file using the same environment
* Can you use Docker to provide the environment?
* Yes docker can be used
* Why do packages need to be installed for Pylint?
* They need to be installed so that Pylint can resolve referenced
*

* Update protocols documentation:
* Add note that we're keeping estimates when ending Sprints (is: don't alter issues)
*

---

## Sprint 36 Planning 2020-06-08

* Leader: Chris
* Scribe: Ryan
* Timer Kristina

### TODO

- [x] Emily: Talk to David about Issues [#52](https://github.com/genophenoenvo/terraref-datasets/issues/52) and [#64](https://github.com/genophenoenvo/terraref-datasets/issues/64)
- [ ] Chris: contact Jacob about attending sprint meetings
- [ ] Chris: link drone-pipeline-environment #43 and #45 to PR
- [ ] Kristina: new ticket for actually publishing OLS blog post
- [x] Emily: New ticket for updating OSF Mentorship page, need to discuss with Kristina
- [x] Emily: Make sure you have sufficient Sprint load by EOD

### Notes

* Zenhub is misbehaving again (bad Zenhub bad), sprint 35 is M.I.A. during review of story points for Sprint 36 vs. 35
* Burndown report indicates Sprint 35 had 79 story points

---

## Sprint 34 Retrospective 2020-05-26

Roles
- Leader: Ryan
- Scribe: Kristina
- Timer: Emily

### TODO

- [x] Chris/Jacob - move issues from sprint 34 to done pipeline or to next sprint
- [x] David - add Ryan to az-digitalag, if not already
- [x] Ryan: Break up Ticket #14 into smaller subtask
- [x] Kristina (and Julian): Ticket #150 needs to be moved to another repo and discussed
> @dlebauer Which repo? And what should be discussed?
> [name=julianp-diag]
- [x] Kristina - make sure Ken has points and clear directions

### Notes

- Skipping demo because CyVerse is down
- We all need to be checking these notes before sprint meetings and resolving the TODOs
- We are *not* changing point estimates during sprint retrospective

---

## Sprint 35 Planning 2020-05-21

Present: Chris, David, Emily, Jacob (welcome!), Kristina, Ryan

Roles
- Leader: Kristina
- Scribe: Emily
- Timer: David

### TODO

- [x] Emily: finish writing new tickets
- [x] Emily: Check `done` items from Data Repo ticket
- [x] Chris: Update points for Ticket #40 as needed
- [ ] Jacob: Move Ticket #43 to next Sprint if needed
- [x] Emily & Kristina: Create Ticket for interviewing DARPA Programmer Candidate
- [x] David: Create issues for Sprint 35 as needed
- [ ] Kristina (and Julian): Ticket #150 needs to be moved to another repo and discussed
> @dlebauer Which repo? And what should be discussed?
> [name=julianp-diag]
- [ ] Everybody: Need to have a discussion about official mentorship, especially for new hires
- [x] Ryan: Break up Ticket #14 into smaller subtask
- [ ] Everybody: Need to address and document how we determine point estimate (i.e. number of points for a ticket assigned to a junior vs. senior programmer)
- [x] For Writing Hour: Address Emily's Ticket #202 (instructions for adding images to website with)
- [ ] Everybody: Please look at and clean up your Epics as needed

#### TODO - Julian

- [x] Julian: Ticket #13? Does David need to review?
> Was not sure if I should close it or submit for QA. Sent @dlebauer conversation with Sean if he wants to review. Feel free to close.
> [name=julianp-diag, time=Thu, May 21, 2020 8:51 PM]
- [ ] Julian: Action items or description for Ticket #148?
> In progress. Not sure of scope yet
> [name=julianp-diag, time=Thu, May 21, 2020 8:52 PM]
- [ ] Julian: Duplicate tickets for Architecture Discussion? Clarify descriptions as needed
> In progress. Not sure of scope yet
> [name=julianp-diag, time=Thu, May 21, 2020 8:52 PM]
- [ ] Julian (and Kristina): Ticket #150 needs to be moved to another repo and discussed
- [x] (As part of Everybody:) Please look at and clean up your Epics as needed
- [ ] (As part of Everybody:) Need to have a discussion about official mentorship, especially for new hires
- [ ] (As part of Everybody:) Need to address and document how we determine point estimate (i.e. number of points for a ticket assigned to a junior vs. senior programmer)

### Notes

- Tickets with 5 points or more _probably_ need to be broken into smaller issues (but definitely need a clear description with action items)

## Sprint 34 Planning 2020-05-11

Roles:

- Leader Emily
- Scribe David
- Timer Chris

## Sprint 33 Retrospective 2020-05-11

Roles:

- Leader Emily
- Scribe David
- Timer Chris

Presentation(s):
- David: BrAPI dev workflow (following https://github.com/terraref/brapi#how-to-set-up-a-development-environment)

### TODO

* [x] Emily resolve (close or bump to next sprint) OLS still in sprint 33
* [x] Chris review #140 and link to PR and move to done
* [x] Julian break up 5 point issues into smaller chunks
* [x] Kristina only has 8 points for next sprint

### Notes

- reminder to minimize number of repositories in zenhub - getting slow (changes also affect long term metrics)

---
## Sprint 32 Review - 2020-04-27

Present: David, Emily, Kristina, Ryan, Chris

### Roles

- Leader: Chris
- Scribe: Ryan
- Timer: Kristina

### Notes

- May need to address group efforts and point assignments, since individual points total are inflated, but helps group totals. We will use total effort points for now to better track group progress.
- Work on moving issues to done in first week of sprints.

### Demo

- Chris demoing Github action scripts
- Workflows use actions
- What do actions get you?
- Native within github, you can create tests within pull requests; similar to TravisCI
- Create folder`.github/workflows` with `.yaml` scripts
- `.yaml` sets rules for pushing changes and console output can be fed into other jobs
- `.yaml` `runs-on` defines OS
- Rules follow this definition and then workflow begins, with each block broken into `- name:`, `shell`, `run`, `id`
- `pylint` checks in demo are enforced on pull requests
- Action repositories can extend github functionality for projects, and automating actions for integration or code checks
- Docker integration is native, easing use

### TODO

- [ ] David: review sentinel detection for new biocro #118
- [x] Emily & Kristina: move incomplete OLS items to next sprint issue #136
- [x] Kristina: add link to issue #112 in sentinel detection
- [x] Kristina: add link to WIDS presention DIAG #195
- [x] Chris: make YABA ticket for plots and geometries
- [ ] David: Sort out draft for internal review data-paper; issue #13 in terraref data paper
- [x] Emily: make sure there is another ticket for remaining UA Data Repo Action Items (if not, create one)
- [x] Chris: Manually Reopen Milestone 33 in Repos
- [x] @julianp-diag: Update tickets and fill in Sprint 33

---

## Sprint 33 Planning - 2020-04-23

Present: Ryan, Chris, David, Kristina

### Roles

- Leader: Ryan
- Scribe: Kristina
- Timer: David (in Emily's stead)

### Notes

Great job all - record time!

### TODO

- [x] ~~David~~ Kristina: do OSF notes todo from last meeting
- [x] Emily & Julian: review and move sprint 32 issues if needed
- [x] Julian
- [x] David: review SQLite database, talk to Chris, close data-paper issue #1
- [x] David: create followup issue re sqlite db
- [x] Julian: create/organize issues for sprint 33
- [x] Jacob: create/organize issues for sprint 33 w/ Chris' guidance
- [x] David: create issue for Emily for merging duplicate cultivars
- [ ] Kristina: create issues for Ken; confer w/ David

## Sprint 32 Retrospective - 2020-04-13

Present: David, Kristina, Emily, Ryan, Chris

### Roles

- Leader: Kristina
- Scribe: Emily
- Timer: David

### Demo: Kristina

- WiDS Lightning Talk
- Making Data Analysis Accessible to Everyone

### Notes

- Julian's ticket #155 was moved to current sprint

### TODO

- [x] Anybody: Update OSF to include adding descriptive final comments to tickets before closing
- [x] Anybody: Update OSF for unresolved questions about tickets
- [x] How many points for group tickets? Added under [*Ticket Checklist* section](https://osf.io/tzmhp/wiki/Agile/)
- [x] Attending conferences, etc.
- [x] David: Ensure there is a ticket in current sprint to review Chris' paper
- [x] Kristina: Add notes to ticket #122 to include link to Google doc

## Sprint 32 Planning - 2020-04-09

Present: David, Emily, Ryan, Kristina

Leader: Emily
Scribe: David
Timer: ~~Ryan~~ Chris

Note: next week everyone needs to prepare for and participate in Quarterly review; also many are also attending WiDS on Friday. So sprint 32 is 2-3 days shorter.

### TODO

- [x] Kristina: create new issue for blogpost improvements ([issue](https://github.com/az-digitalag/organization/issues/197))
- [ ] Jacob: write bio for website
- [ ] Jacob: put issues in next sprint

## Sprint 30 Retrospective - 2020-03-30
Present: Chris, Emily, Kristina, Ryan

Leader: Kristina (Substitute Leader - soon to take over everything)
Scribe: Chris
Timer: Ryan

### Demo: Kristina
- BioCro model vignettes
- Written in R-Markdown but rendered into (plain) markdown
- Analysis of Setaria data

### Notes:
* Update OSFG notes to be specific re. closing tickets at Sprint Retrospective - keep in Done, Ready/QA until then

### TODO:
- [x] Chris: Make pull request for #107
- [x] Ryan: Link PR#9 to original issue
- [ ] Julian: #115 of AgPipeline, New channel to some other channel
> I'm not sure what this means.[name=julianp-diag, Thu, Apr 9, 2020 5:41 PM]
- [x] Julian: Review Sprint 31 tickets for correct priority
- [ ] David: Review New issues and move out of channel to another where applicable
- [x] Kristina: Review issues and move some to next sprint (currently overloaded)

## Sprint 31 Planning - 2020-03-26

Present: David, Julian, Emily, Chris, Kristina

Leader: Kristina
Scribe: Chris
Timer: Emily

### Notes

- [x] Improve protocols: "check that issues are in the right bin" - clarify that Done aren't supposed to be in Review/QA & vice-versa
- [x] Improve protocols: Move 5 minutes section to after 15 minutes review...

### TODO

- Gantry Pipeline
- [ ] david tag all open / gantry related tasks 'ua-gantry' and moving to icebox
- [ ] need to remove gantry-specific generalization from ag pipeline tasks
- Kristina:
- [ ] check stale PRs in brapi and tutorials issues, e.g. https://github.com/terraref/tutorials/issues 172, 177 and 229
- [ ] Talk to David about Arden project, BRAPI and TR Tutorials, and ED2
- Emily:
- [x] Update TO ticket(s) as needed
- Julian:
- [x] ~~Talk to David & Chris about what I should work on - now that things have shifted around a bit~~
- [x] Checkout the Ready queue and choose tickets
- Chris:
- [x] Flesh out Sprint 31
- [x] Talk to David about Tickets related to Open
- [x] Talk about dataset to test with, order of priority
- Ryan:
- [ ]
- David:
- [ ]

## Sprint 29 Retrospective - 2020-03-16

Present: Kristina, Emily, Ryan, Chris, David, Jacob

### Roles
* Leader: David
* Timekeeper: Chris
* Notes: Emily
* OSF Edits: Kristina

### Notes

* Ryan, be careful with the things
* Use descriptions and clear outcomes when opening tickets
* Comment when closing tickets with follow-up actions when needed
* Close / update tickets throughout the Sprint when possible (rather than on last day)
* Idea: Set deadlines for preparations before meetings?
*

### TODO

- [ ] ~~Include description for Ticket about hiring strategy~~ unclear
- [x] Julian, please make sure your tickets are updated before Sprint Planning and Retrospective meetings
> I wanted to talk to somebody first. I'll catch up with Chris today and sort it out. [name=Julian] [time=Tue, Mar 16, 2020 10:30 AM]
- [x] Update OLS Weeks 7-8 ticket with comment about follow-up ticket for Chris

## Sprint 30 Planning - 2020-03-12

Present: Kristina, Emily, Ryan, Chris

### Roles
* Notes: Ryan
* Timekeeper: Emily
* Leader: Kristina

### Notes

* Revised sprint planning notes on OSF page
* New Issues will be written up in notes
* As we write up interview questions, these should be added to the OSF page
* Template for issues
* Try to write up new issues before planning meeting so velocity checking is more accurate

### TODO
- [x] Add ticket for revising sprint review notes on OSF ([ticket #181 in organization repo](https://github.com/az-digitalag/organization/issues/181))
- [x] Update ticket #3 docker genophenoevo to next sprint
- [x] Invite Jacob to #AgData Slack Channel
- [ ] David to review GenoPhenoEnvo paper draft from last sprint
- [ ] Add interview questions to OSF page
- [ ] Add template for new issues to other repos
- [x] Create OSF milestone for 3-13-20

### New Issues to write up
- [x] Ryan: add DSF issues to zenhub
- [x] Julian: review and update sprint
- [x] Kristina:
- [x] Emily: Talk to David about issue 21 of GenoPhenoEnvo
- [ ] David: Enable other repos for Sprint 30; not all can be assigned to the sprint from zenhub
- [x] Chris: write tickets for paper draft and editing

## Sprint 28 Retrospective - 3-2-2020

Present: Emily, Ryan, David, Julian, Kristina, Chris, Sateesh

### Roles

* Notes: Emily & Julian
* Leader: David
* Timekeeper: Julian

### Notes & Wins

* Kristina writing paper on our project management! :tada:
* Emily demo: showing her Vice app for data cleaning

### TODO

- [x] Ryan's advice: Try transforming the dates after filtering
- [x] Julian: Add benchmark numbers to [issue](https://github.com/AgPipeline/issues-and-projects/issues/97)
- [Done](https://github.com/AgPipeline/issues-and-projects/issues/97#issuecomment-593546107)
- [ ] Julian: Add notes to [issue](<https://github.com/AgPipeline/issues-and-projects/issues/99>) for what's involved in clearing gantry cache server
- [ ] [Plan](https://github.com/az-digitalag/organization/issues/176) for reviewing applicants for both positions

---

## Sprint 29 Planning - 3-2-2020

Present: Emily, Ryan, David, Julian, Kristina, Chris, Sateesh

### Roles

* Notes: Emily
* Leader: David
* Timekeeper: Julian

### Notes

*

### TODO

- [x] Chris: update his tickets
- [ ] Everybody: Clarify Sprint Planning & Review notes on OSF ([issue for this](https://app.zenhub.com/workspaces/ua-ag-data-science-5a57a3198339f11ba1c85775/issues/az-digitalag/organization/173))
- [x] Emily and David to talk about metadata, automating data cleaning processes, and meeting about dashboard with Julian and Max
- [ ] Julian: add descriptions and links to the Nomad [ticket](https://github.com/AgPipeline/issues-and-projects/issues/100), how it connects to the database, etc.
- [x] Julian: say "CyVerse, CyVerse, iRODS, DataStore, CyVerse" as many times as possible
- Use IRODS as backend for minio
- [x] Julian: Add issue to move data from NCSA to TACC
- Mostly to help Sean as much as possible
- [Done](https://github.com/AgPipeline/data/issues/13)
- [ ] David:

---

## Sprint 27 Retrospective - 2-17-2020

### Roles

* Leader: Jorge
* Timekeeper: Chris
* Notes: Kristina

### TODO

* [x] Jorge: create issue to track all the PRs that still need to be merged; assign other group members so we can make sure they're merged
* [x] Julian: close #82 (include notes about discussion); open a new issue for new direction
* [ ] Ryan: populate issues for sprint 28

### Notes

* Emily: is issue #34 resolved yet? (yes)
* David to demo Roadmap at next retrospective

## Sprint 28 Planning - 2-13-2020

### Roles

* Leader: Kristina
* Timekeeper: Jorge
* Notes: David

### TODO

* [x] Ryan: describe resolution to #159 and link to genophenoenvo page
* [x] David Emily Kristina Chris: meet to discuss OLS
* [x] David and Chris: determine how to fix multipolygon requirement
* [x] David: Define ED2 singularity script issue: https://github.com/danforthcenter/sentinel-detection/issues/104
* [x] Jorge: set up meeting w/ Chris
* [x] Julian: Turn [issue 39](https://github.com/AgPipeline/issues-and-projects/issues/39) into an epic
* [ ] Create sub-tasks for [issue 39](https://github.com/AgPipeline/issues-and-projects/issues/39)
* [x] Everyone minus David: set up meeting to review OKRs for this quarter

### Notes

* David to demo Roadmap at next retrospective
* Need to review prev. todos before and during meeting
* Add slack reminders to review issues and this page

## Sprint 26 Retrospective - 2-3-2020

Present: Emily, Jorge, Julian, Kristina

### Roles
* Leader: Jorge
* Timekeeper: Julian
* Scribe: Emily

### Demo: Jorge
* Building and deploying VICE App within Discovery Environment
* RGB Plot in Jupyter Environment

### Notes
- Kristina has already met with somebody to talk about open position
- Kristina's Lightning Talk at conference went well! Yay!

### ToDo
* Jorge
- [ ] Clear documentation that image data being pulled for VICE app is included in folder
- [x] May need to clean up tickets / points for Sprint 27
- [x] New ticket for Lidar Docker image
* Ryan
- [ ] Add comments to ticket about GWAS meeting with Kent
- [x] Review Emily's notes from EML meeting for Pull Request
- [ ] Close TASSEL ticket if finished and add link
* Emily
- [ ] Review Jorge's PR for ED2 documentation
* Kristina
- [x] Review Jorge's PR for ED2 documentation
* Chris
- [x] Has new ticket been created for hyperspectral plot clippings?
- [x] Status on Issue #75 netcdf stuff? [it's a work in progress]
* David
- [x] AgPipeline/data repo?
* Julian
- [x] Are you _sure_ you want 18 points for Sprint 27?

---

## Sprint 27 Planning - 1-30-2020

#### Present
Emily, Jorge, David, Julian, Ryan, Chris

### Roles
* Leader: David
* Scribe: Emily
* Timekeeper: Julian

### Notes

* Ryan will need more memory to run TASSEL but recommends using different tool (PLINK) with help from Amanda Cooksey
* Need method that can handle missing data / cultivars
* Lots of potholes in Tucson

### ToDo

* Kristina will take care of her tickets tomorrow (1-31-2020)
* Emily and David to meet about EML / data paper
* Ryan to flesh out descriptions for tickets
* All to start using template for issues - AgPipeline and OLS templates as examples
* Julian to break [13-point issue](https://app.zenhub.com/workspaces/ua-ag-data-science-5a57a3198339f11ba1c85775/issues/agpipeline/issues-and-projects/39) into Epic
* [x] Julian to create issue for investigating best-practices & tools for centrally managed server access.
* Done - <https://github.com/az-digitalag/organization/issues/160>

---

### Demos of interest:

* Jorge w/ Jupyter notebook

---

## Sprint 25 Retrospective - 1-20-2020 (ish?)

### Roles
* Leader: Jorge
* Notes: Kristina
* Timer: Emily

### Demo: Kristina (RLadies talk)

### Notes

- David
- Projects page link didn't work, so left in done
- Chris
- Need to close #71 and open followup issue?
- 3 issues in review/QA, do they need to be moved or updated?
- Kristina
- Close DARPA ad issue?
- Julian
- Reduce number of points for this sprint to doable amounts (move to next milestone, move to backlog/icebox, prioritize issues)

## Sprint 26 Planning - 1-17-2020

Present: Emily, Chris, David, Jorge, Julian, Kristina, Ryan

### Roles
* Leader: David
* Notes: Emily
* Timer: Jorge

### Notes

- Change Sprint Planning time allocations as needed (we always go over 5 minutes for reviewing new issues, assigning, and linking to correct Sprint)
-

### ToDo

- Next steps for hyper-spectral data (Issue #57):
- clipping to plot
- computing indices
- putting indices in BETYdb
- Kristina to schedule Wednesday review of pull requests
- Everybody share calendars
- Kristina - switch to Google calendar! (and make 5-year plan)
- Emily & David discuss communications issues with PEG Group members and moving forward
- Emily - fix tickets / split meeting tickets into meeting & outcome tickets
- Julian - fix tickets (too many points)
- Ryan & Emily - talk to CyVerse people about TASSEL v5

## Sprint 25 Planning - 1-8-2020

### Roles
* Leader: David
* Notes: Kristina
* Timer: Emily

### Notes
- Emily
- Meet with David & IDEAS folk to figure out next steps for Anne
- Kristina
- Add interesting ideas OLS page & previous Pecan projects to GSOC project ideas
- Meet with David about ideas for Rladies talk
- See if url traitvis webapp PR can be merged

## Sprint 24 Retrospective - 1-8-2020

### Roles
* Leader: David
* Notes: Kristina
* Timer: Emily

### Demo: Chris

* How to set up servers in Tombstone OpenStack
* Create key pair
* Launch an instance
* Base specifications
* Volume = harddrive
* Cores, memory size (8 GB)
* Leave defaults for Network pages
* Security group = exosphere
* Select newly created key pair
* Leave defaults for rest of pages
* Under Actions
* Choose "Associate floating IP"
* Shelve instance to free up resources
* Can create new volumn under Volumes and associate with instance
* ssh into new instance using IP address
* Delete by checking instance box
* Exosphere will be nicer UI for this
* There's also Atmosphere's version of this
* Some documentation already exists for Exosphere

### Notes
- David
- Review all ready issues and move relevant issues to icebox or backlog
- Chris
- Make sure these PRs are resolved: https://app.zenhub.com/workspaces/ua-ag-data-science-5a57a3198339f11ba1c85775/board?milestones=Sprint%2024%20(December%202%2C%202019%20-January%205%2C%202020)%232020-01-05&filterLogic=any&repos=80695066,165746676,160253698,151617511,175507213,101220639,185447068,201100988,203868729,42889668,207390055,216677713

## Sprint 23 Retrospective - 12-2-2019

Present: Chris, David, Emily, Julian, Kristina

### Roles
* Leader: Chris
* Timer: David
* Notes: Emily

### Demo: Kristina
* Running a model in PEcAn - estimate biomass of Setaria plants over time
* BioCro

### Notes
- Kristina
- [ ] Get traitvis webapp [pull request](https://github.com/terraref/traitvis-webapp/pull/61) to show up in sprint 24

- Chris
- [ ] AgPipeline PR #1 - needs to brought into a milestone and repo into org (?): **update** Add new tickets to track pull requests for repositories not already on the board
- Emily
- [x] Take notes from meeting with Ramona for [Issue #11](https://github.com/genophenoenvo/terraref-datasets/issues/11)

- AZ DIAG needs a new ticket for e-mail address
- Jorge
- [ ] Computing pipeline #16
- [ ] Pull in one or more issues from ready to sprint 24
- Julian
- [x] Decrease number of points for sprint to a reasonable number by moving issues to backlog or out of sprint 24

## Sprint 24 Planning

* David has done backlog grooming: there's tickets that need to have more information added to them
* Emily has problems with traitvis-webapp #47
* Will meet with David on Monday
* Emily should still meet with Ramona and move forward on all fronts on this
* Spend time on Fridays after Documentation hour to finish reviewing all Pull Requests
* Kristina will present at Monday's Sprint Review

### TODO
- David
- [x] Assign points to: Organization #119
- [x] Add tickets for work items; including one for data paper outline
- Kristina
- [x] Close Brapi bug issue Tutorials #218 and create new issue for next sprint for reviewing this
- [x] Will do demo for next week's sprint retrospective
- Julian
- [ ] meet with David and Chris about relative priority of Welsch machine
- [x] Meet with Chris to flesh out tickets (make epics)
- [x] Provide points to tickets in Sprint 24 that are missing them (and any others as possible)
- Jorge
- [x] Meet with Chris about fleshing out Sprint 24 issues
- Chris
- [ ] update OSF document to clarify steps between current sprint and next sprint
- [ ] update OSF document: sprint preparation - review checklist items from this document
- [ ] update OSF document: identify one or more people to present at retrospective
- [x] work with Julian to move tickets into Sprint 24 (done)
- [x] ~~create ticket for~~ write up abstract for December 5 deadline
- Emily
- [x] Assign reviewers to Pull Request traitvis-webapp #61 (this is completed)
- [ ] talk with David about terra-ref/datasheets #9

## Sprint 22 Retrospective & Sprint 23 Planning - 2019-11-18

* Moved all of Julian's sprint 22 issues to sprint 23
* Chris did demo on how he restructured the pipeline code

### TODO
- David
- [x] Write issue for sprint 23 for data paper
- Kristina
- [x] Meet with David about biomass partitioning after this meeting
- Julian/Kristina/David
- [ ] Create issue for asking Tyson about how much CyVerse can help with creating Pecan Vice app
- [ ] Figure out what role Julian will play in DARPA project
- Jorge
- [x] Create followup issue(s) for [#10](https://github.com/AgPipeline/computing-pipeline/issues/10)

## Sprint 20 Planning - 2019-10-31 Happy Halloween!

Present: David, Chris, Emily, Jorge, Kristina, Julian

### TODO

- Julian
- [ ] issue for testing makeflow version against new dataset
- Chris
- [x] Add link to newsletter to #87
- [x] Document one pr per issue
- [x] Meet with Jorge about py2las (?)
- [x] make sure all repos have next milestone

- Kristina
- [x] Close all in review issues (including notes about what is done), open new issues for getting them reviewed
- [x] Create new issue for figuring out traitvis issue #45 (1 day max)
- [ ] Discuss traitvis next steps with David
- Kristina/Julian
- [x] Create issue(s) for first steps for Pecan Vice app
- David
- [x] create issue for debugging traitvis webapp; created this and then

## Sprint 20 Review - 2019-10-21
Present: David, Chris, Emily, Jorge, Kristina

- Chris
- [x] Create issue: followup to #109 for moving script from personal repo to new org repo

## Sprint 21 Planning - 2019-10-18

(Continued)

Present: Chris, David, Kristina, Julian

### TODO

- David
- [x] Create issue: Onboarding of Emily & Jorge

- Emily
- [x] Create issue: Use pivot tables to view Team OKRs by person

- Kristina
- [x] Meet with Julian about connecting issues to team OKRs
- [x] Go through onboarding documents (Monday morning)

- Julian
- [ ] Create issue: Rolling sprint planning document
- [ ] Create issue: Shoulder-surfing Sean on gantry cache server tasks
- [ ] Make ticket descriptions more useful (115 & 116)
- [ ] Create issue: Second part of Makeflow PoC with remaining extractors

---

## Sprint 21 - 2019-10-17

Present: Chris, David, Julian

File: 2019-10-17_sprint-planning.md

Also see [2019 Q4 OKRs](https://docs.google.com/spreadsheets/d/1LSpa24C_ltHGPI1FK5-xjQgobcMmFcbLvO2vRCU6VBw/edit#gid=1777430460)

### Roles

- Scribe: Julian
- Time keeper: David

### Notes

Started: 13:05
Finished: 13:33

ZenHub broke around 13:25. Will have to pick it up again.

### TODO

- Chris
- [x] invite Max to sprint review and planning meetings
- [x] remove Clairessa and Kimberly from meetings
- [x] change sprint planning meetings so that they don't conflict with Thurs 12-2 terraref meetings
- [x] Create issue: Resolve missing FQDN on Welsch (sprint 21)

- David
- [x] Check in w/ Nirav about CyVerse components
- [x] Create writing tasks for Fridays
- [x] Create issue to brainstorm CALS support projects https://github.com/az-digitalag/organization/issues/110

- Julian