Connected Devices/Projects/Magnet/Sprint 11

From MozillaWiki
Jump to navigation Jump to search

General info

  • Sprint 11 from January 23th to February 3rd (2017)
  • Participants Development Sprint: Francisco, Wilson, Sam, Guillaume, Francis, Isabel and Maria

Sprint objectives

According to the planned engineering work, last sprint (Sprint 10) we worked hard on the React components, so we are in good shape to finish them at the end of the first week of Sprint 11. We finished the App Navigation and Deep linking tasks too that were scheduled to be done in Sprint 11 but at the same time, we couldn't move too far in the Backend part.

During this sprint 11, we are not going to have visuals yet, we need to do all the work that doesn't require UI (Visual work will not be started until Jan 30th) It will include:

  • Finishing all the React Components (at the end of the next week, Jan 27th)
  • and all the backend part including the libraries. We expected to be finished at the end of next week, but probably it will take until the end of sprint 11. Sam will start working on API, and documenting it

Apart of this:

  • Wilson started to post some mock up concept and we will continue with that until we have the final UI.
  • Francisco wants also to build the the Geolocation component, no the geofencing, to ensure the app has the the localization ready to distribute it to the rest of the components and probably later he will try to give a hand in the offline strategy and the client API as both things have to be built together.

Development tasks Planning

Magnet Engineering sprints postGate1.png


Tasks or Bugs committed for this sprint

Task Assigned Status Status Notes
Create a MediaPlayer element for iOS and Android supporting the Opus codec Sam Ongoing
Document development process for services Sam Ongoing
Render POI view with dummy data Wilson Ongoing Now we have dummy data for home view we need to be able to transition to a POI view from one of the tiles in the home view. This will require reshuffling the Redux store structure to work from a central item-cache. The home view will reference a list of POIs by ID and the POI view will reference a single POI by id. When the view is rendered we will fetchItemIfNeeded(). The cloud API will likely return a list of POIs so we should cache each of these separately so that they can be reused by the POI view.
Audio component Not started Not just the player that is being done in "Create a MediaPlayer element for iOS and Android supporting the Opus codec" task but the screen that looks like a phone call, etc.
Create cron to kick off nightly builds Sam Not started
First testing round Isabel Not started
Fav component Not started
Share component Not started
Carousel component Francisco Not started
Create database "model" objects with a view to reuse in a library on the client Not started
Generate and save terraform plans for creating the k8s cluster and document deis installation Sam Not started

Issues during this sprint

Demos

Retrospective

Actions taken from last sprint

  • [Maria] to remove simplify the Milestones, dropping the "Gate - 1" part

Things that went well

Things that went not that well

Actions for this sprint