IPT Meeting 2016-04-26 - Sprint 1 Stand Up 6 - Review

Mach 30 IPT Meeting April 26, 2016

Discussion Topic: Sprint 1 Stand Up 6 + Review + Retrospective

Attending: J, Jeremy, Greg, Ray, Brian, Ryan

Start: 2050 Eastern

End: 2230 Eastern

Summary:

IPT completed first sprint of 2016! Six of seven tasks finished including logo, research, and attempting to capture satellite signals for under $30.

Minutes:

Stand Up

Did - Documented “a whole mess of thing...” ENG-01 duplicating the $30 blog post. And has no success on a few satellite passes, most likely due to insufficient antenna.
Will do -
Blocked? -

Did - Finalized the details on the logo/patch design (using Microsoft Expressions Design), and have several versions posted to the DMSF on OpenDesignEngine page.
Will do -
Blocked? -

Did - Goal was to get 3 hackerspaces in addition to Quelab... right now we have 2 more (Champ and NovaLabs). Still hoping to hear back from FabLab, MakersAlliance and Catylator. Also focused on GroundSphere social media sites.
Will do -
Blocked? -

Did - Reviewed the old meeting notes to catch up on Sprint 1 progress. Used the USB dongle to receive some FM radio signals. Got stuck on one of the SDR installs.
Will do -
Blocked? -

Review

MKTG-10: Register Social Media accounts for @GroundSphere on Twitter, Instagram, Vine

Results (Brian) - all 3 of these accounts (plus some more) are registered; claiming done

ENG-01: Technical lit review of comparable systems (amateur and open source ground receivers, aka $30 blog post)

Results (J) - https://opendesignengine.net/projects/groundsphere3/wiki/Similar_Projects written covering 11 web pages/sites dicussing this topic about well over a dozen (two?) projects with varying degrees of documentation; claiming done
Accepted? - yes

Results (Ray) - Logo posted on ODE DMSF page (svg, and rasterized). Claiming done
Accepted? - yes

MKTG-05: Post weekly IPT progress (aka - materials from stand ups, etc) on Mach 30 social media outlets

Results (Brian) - Standup summary posted soon after each standup posted to @Ground_Sphere, starting today, the sprint review and forward will also go to @Mach_30. Claiming done
Accepted? - yes

ENG-09: Research and identify a source for link budget calculations (including test cases)

Results (Aaron) - J posted some links to the Resources wiki page; Aaron is preparing video summaries of the materials for link budgets; not claiming done

J - requested the other source materials considered for use as example link budget calcs be added to the wiki page and note the one that was selected

Results (J) - https://opendesignengine.net/boards/51/topics/1149 worked through and documented the bills of materials (hw and sw), sw verification, operation instructions including screenshots and video; conducted multiple attempts to capture signals per these instructions but did not capture signals; the blog post is light on covering antenna selection, believe the blog post material needs to be supplemented with other research (see ENG-01) to address antenna (and maybe more?); still claiming done (reproduced what was documented)
Accepted? - yes

NOTE: (Aaron) - The ISS HAM radio broadcast has “gone dark” and stopped broadcasting... more info gathering needs to happen here, but not tonight.

Retrospective

Greg - re: ENG-01, keep in mind the audience of the lit review (e.g. tagging the content in the lit review to make it more discoverable)

Great work in focusing on finishing PBIs/Projects and personal goals, despite schedules and other requirements of time/etc
Adapted to the Stand Up and over all agile process well for the first time as a new team with a good focus on communication through weekly stand-ups and other online means.
Research projects went back to fundamental principles and verified concepts (this applied beyond just technical issues - for example the logo showed the history and technical detail of the project, requiring research in its own right)
We paced ourselves showing development over the whole sprint period.
Pulled together for PBIs (e.g. the logo) when people needed help
Did sustaining PBIs (social media posts) and one off PBIs (logo, $30 blog post)

Communications between stand ups was hard which made it hard to sync up or follow work between stand ups
Some of the PBIs were not clearly defined and that led to some scope creep and underestimation of size
It was not always clear how to share/communicate the PBIs with the audience (especially over social media)
Some team members found it very hard to make sufficient time to work on tasks
There was some bleed through between tasks for IPT and for other commitments in Mach 30

Team members assume more personal responsibility during sprints as identified by themselves
Offer help at the smallest sign of need
More freely ask for help
Consense on team’s comm channels and their purposes (outside of retrospective)
Be more interactive with people outside of standups
Have the team summarize deliverables for PBIs during sprint planning to confirm shared understanding of definition of done with the product owners
Remember that the team commits together to the product owners for completing PBIs and to each other as individuals at stand ups to make progress on the PBIs. AKA - the team only gets credit or not for PBIs together (live together, die alone)
Plan for a little smaller total commitment to give people room to ebb and flow during sprint
Product Owners could work with Brian/Ingrid (aka - team members who represent the audience as stakeholders) on the PBI descriptions to arrive at a shareable definition - need to determine when to do this
Product Owners ensure PBIs are only for IPT work