---

Spring Semester

---

Weeks 13, 14 & 15 (4/24/2017 - 5/14/2017)

Progress Presented final presentation [All] Wrote final self-assessment [All] Presented poster [Asma and Sam] Added different icon for alerts [Asma] Added user’s first name and last initial to comments [Asma] Wrapped up documentation and reviewed bugs [Sam] Wrote most of technical report [Jeremy] Worked on user email privacy issue [Austin]	Risks Not enough documentation exists for the next team Not enough time left to fix the high priority bugs We break something important at the last minute
Plans Finish technical report [All] Submit final artifacts to SE department [Sam]	Needs Final review meeting

Week 12 (4/17/2017 - 4/23/2017)

Progress Final poster touch-ups + creation of first draft of slides for upcoming presentation [Jeremy] Started on issue-151, removing user emails from synced table [Austin] Revised the poster, wrote documentation, worked on small bugs [Sam] Added USBRS Routes page with Show Route button [Asma]	Risks Not enough documentation exists for the next team Not enough time left to fix the high priority bugs We break something important at the last minute
Plans Continue to fix bugs assigned in GitHub which are on John’s high priority list for the final build. [All] Write more documentation. [All] Document steps for bugs and make sure they are clear. [All] Work on the presentation. [All]	Needs Test of the latest build Review of the remaining bugs for the final build

Week 11 (4/10/2017 - 4/16/2017)

Progress Finished changing login functionality based on issue-130 [Austin] Poster (Dr. Valino feedback) + test work [Jeremy] Fixed photo upload button in web browsers [Asma] Cleaned up build process a bit for Android and iOS, and updated documentation [Sam] Stopped allowing the app to show any URL in the web view [Sam]	Risks Not enough documentation exists for the next team Not enough time left to fix the high priority bugs
Plans Continue to fix bugs assigned in GitHub which are on John’s high priority list. [All] Review and revise the poster. [All]	Needs Test of the latest build Review of the remaining bugs

Week 10 (4/3/2017 - 4/9/2017)

Progress Worked on changing login functionality based on issue-130 [Austin] Updated buttons to RaisedButton style [Asma] Updated string on “Comment” button to be “Submit” [Asma] Worked on within-AWS HTTPS deployment [Sam] Fixed scrolling in peek card [Sam] Updated Node dependencies to update more conservatively [Sam]	Risks Not enough documentation exists for the next team Not enough time left to fix the high priority bugs
Plans Continue to fix bugs assigned in GitHub which are on John’s high priority list. [All] Review and revise the poster. [All]	Needs Test of the latest build Review of the remaining bugs

Week 9 (3/27/2017 - 4/2/2017)

Progress Finished auto-publish. [Austin] Made a button to center map on user’s location [Austin] Finished poster, updated Burn Up, verified a few recent client pull requests, made some notes for presenters [Jeremy] Added button that shows average review stars and brings users to the review page [Asma] Stopped Camera/Library popover from showing in browsers [Asma] Fixed navigation bar issues [Sam] Fixed iOS photo attaching [Sam]

Risks Not enough documentation exists for the next team Not enough time left to fix the high priority bugs

Plans Continue to fix bugs assigned in GitHub which are on John’s high priority list. [All] Review and revise the poster. [All] Close out dangling reviews. [All]

Needs Test of the latest build Review of the remaining bugs

Week 8 (3/20/2017 - 3/26/2017)

Progress Worked on auto-publish. [Austin] Worked on the poster. [Jeremy] Fixed a bunch of stability bugs and some low-hanging-fruit. [Sam] Can now take a picture with your phone or choose the library option - completed. [Asma] The app will notify the user once the picture has been uploaded - completed. [Asma]	Risks Not enough documentation exists for the next team Not enough time left to fix the high priority bugs
Plans Continue to fix bugs assigned in GitHub which are on John’s high priority list. [All]	Needs Test of the latest build

Week 7 (3/6/2017 - 3/12/2017)

Progress Fixed syncing services before editing. [Austin] Worked on removing user emails from synced tables. [Jeremy] Deployed HTTPS. [Sam] Configured use of domain name. [Sam] Updated iOS browser engine. [Sam] Fixed Android photo rotation issue. [Asma] Updated point card to show entire photo. [Asma] Worked on showing snackbar on photo upload. [Asma] Fix the upload photo button to work properly in web browser, but dependency update broke it. [Asma] Researched taking a photo within the app. [Asma]

Risks We are crushed by a huge pile of tiny bugs. Another giant storm hits Rochester and the power goes out for the third time.

Plans Continue to fix bugs assigned in GitHub which are on John’s high priority list. [All]

Needs Review of the current build

Week 6 (2/27/2017 - 3/5/2017)

Progress Fixed alert validation errors. [Asma] Worked on improving tests and test output. [Jeremy] Worked on syncing services before editing. [Austin] Update dependencies. [Sam]	Risks We are crushed by a huge pile of tiny bugs.
Plans Continue to fix bugs assigned in GitHub which are on John’s high priority list. [All]	Needs None

Week 5 (2/20/2017 - 2/26/2017)

Progress Started task 152 - sync services before editing. Not completed yet. [Austin] Add alert validation errors don't display #81 - not completed yet. [Asma] Skin-deep research, weighed benefits of using another tool (Enzyme) as per last year's recommendation. Updated READMEs for coverage/testing. Wrote some unit tests for the drawer and onboarding page. Verified Sam's photo fixes. [Jeremy] Fixed various critical reliability issues. [Sam]

Risks We are crushed by a huge pile of tiny bugs.

Plans Continue task 152, and add a message while updating points so the user knows why they are waiting. [Austin] Finish up "Add alert validation errors don't display #81" and start another HIGH priority on my list. [Asma] Continue fixing various critical reliability issues. [Sam]

Needs Present testing progress to John [Jeremy]

Week 4 (2/13/2017 - 2/19/2017)

Progress Finished issue 128 so onboarding panels will show on first app load [Austin] Finished issue 114 so the url validation will only occur when making and updating services when there is not an empty string [Austin] Worked on fixing some broken tests from last year (continuing effort) [Jeremy] Added optional expiration on alerts [Asma] Added shrinking photos on upload [Asma] Fixed an issue where editing a service multiple times before publishing would only publish the first set of edits [Sam]

Risks Data storage and syncing could be a lot more broken than we realize.

Plans Start task 131 where there is an informational panel during account creation to let the user know about the privacy policy. [Austin] Fix as much of the data storage and syncing as possible. [Sam]

Needs Determine the specific next priority tasks for team members looking for work to do.

Week 3 (2/6/2017 - 2/12/2017)

Progress Worked on Alert expiration - not completed yet. [Asma] Completed onboarding task 129 where they are accessible from the settings page. [Austin] Stop expiring the sessions. [Sam] Continued attempts at getting client coverage reports with Karma. [Jeremy]	Risks Data storage and syncing could be a lot more broken than we realize.
Plans Finish up the Alert expiration then look into what needs to be done for resizing of uploaded photos. [Asma] Finish task 128, where panels open on first app load. [Austin] Fix as much of the data storage and syncing as possible. [Sam] Continue working on tests. [Jeremy]	Needs None

Week 2 (1/30/2017 - 2/5/2017)

Progress Verified Sam’s Issue-25 fix for running application in a Windows env. Also identified & fixed separate bug preventing client-side test runner from working [Jeremy] Figured out how to obtain coverage reports (via Istanbul) for both model and server, still working on getting similar reports in the client [Jeremy] Worked on onboarding panels [Austin] Make Service/Alert point invisible to user if it has been flagged 5 times - completed. [Asma] Make Service/Alert appear on map again if is_hidden is set back to false in database - completed. [Asma] Flag option to say why you are flagging is merged. [Asma] Did various work around adding Redux persistence and making persistence more reliable. [Sam] Merged and closed various stale bugs. [Sam]

Risks Estimates could be very inaccurate. Point persistence could be much more flawed than we thought. Redux migrations could take a decent amount of effort.

Plans Put optional expiration date for Alerts. [Asma] Figure out what needs to be done for photos. [Asma] Continue onboarding panels. [Austin] Continue automated testing work. [Jeremy] Keep working on reliability in point and account management. [Sam]

Needs Re-evaluation of more serious bugs not on the ‘feature complete’ list

Week 1 (1/23/2017 - 1/29/2017)

Progress Redirected Flag “on click” to new window like comments does. [Asma] New window provides “Other” option for user to type in reason - output goes to DB with user email and their reason. [Asma] Worked with Asma to resolve a bug around flags. [Sam] Assessed work to be done. [Sam] Started onboarding panels. [Austin] Combed through the client/server/model repos and created a defect tracking document for all work thus far. [Jeremy]

Risks Estimates could be very inaccurate. Persisting different Redux data types could take a lot more work than anticipated. Testing framework may be hard to work with.

Plans Persist the entire Redux store across launches of the app. [Sam] Put in the rest of the options for the flag. [Asma] Figure out what needs to be done for photos. [Asma] Continue onboarding panels. [Austin] Continue automated testing work. [Jeremy]

Needs For Flag: What exact options other than “Other” would John like. Should we allow user to put an expiration date on a point (specifically an Alert)? Do we want to have the flagged point automatically remove the flag after a certain number of users have flagged it - if so, what would be the threshold? Should we allow the user to put in a expiration date for when they are flagging a point?

Fall Semester

---

Weeks 15 & 16 (11/14/2016 - 12/11/2016)

Progress Outline, design, rehearse, and present presentation [All]	Risks Lack of attention to following chosen process methodology (continuing) Difficulty learning technical details of current implementation/platforms (continuing) Work required to change map layer (continuing)
Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)] Continue new feature work	Needs Approval on what to deliver right after break

Weeks 13 & 14 (11/14/2016 - 11/27/2016)

Progress Unsupported browser alert tested and merged, some redux research [Austin] Btc-app issue #120 - 404 from password reset email was fixed [Austin] Finished some comment work [Sam]	Risks Lack of attention to following chosen process methodology (continuing) Difficulty learning technical details of current implementation/platforms (continuing) Work required to change map layer (continuing)
Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)] Continue new feature work	Needs Decisions on comment flow when logged out

Week 12 (11/7/2016 - 11/13/2016)

Progress Completed unsupported browser alert and started on btc-app issue 81 [Austin] Created draft presentation, started team interim self-assessment. Continued comment work [Jeremy] Finished Flagging Points (the DB stores the users who flagged the point in the Point table under flagged_by field). NOTE: Does not yet have options as to why the user is flagging. [Asma] Launched custom vector/raster tile server. Loaded in New York State. NOTE: The new tile server is not currently running fast enough to use in the mainline build. [Sam] Added “About” page with build, copyright, and map attribution info. [Sam] Removed map attribution from the map itself. [Sam]

Risks Lack of attention to following chosen process methodology (continuing) Difficulty learning technical details of current implementation/platforms (continuing) OpenCycleMap licensing fees for bulk downloading or work required to change map layer

Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)] Continue new feature work

Needs Decisions on map layer priorities for bicyclists and how to draw them

Week 11 (10/31/2016 - 11/6/2016)

Progress Reported some bugs, studied up on Redux, started the interim slides, continued comment work [Jeremy] Completed forgot, and reset password work [Austin] Investigated mapping solutions [Asma and Sam] Worked on implementing flag behavior [Asma] Added server-side support for comments [Sam] Worked on adding “About” page [Sam] Hid nonfunctional delete buttons on publish page [Sam]	Risks Lack of attention to following chosen process methodology (continuing) Difficulty learning technical details of current implementation/platforms (continuing) OpenCycleMap licensing fees for bulk downloading or work required to change map layer
Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)] Continue new feature work	Needs Decision on mapping direction

Week 10 (10/24/2016 - 10/30/2016)

Progress Worked on service comments feature, created labels for and prioritized issues across all repos, refreshed self on FDD and briefed team on process concerns we need to look at moving forward [Jeremy] Worked on forgot password REST calls on the server side. Btc-model and btc-app should be done [Austin] Snackbar indicating you must be logged in to publish a point is completed [Asma] Points associated to the user is completed [Asma] OpenCycleMap - Hobby Project sign up complete and updated our current map to use OpenCycleMap [Asma] Launched web version [Sam] Fixed some bugs [Sam]

Risks Lack of attention to following chosen process methodology (continuing) Difficulty learning technical details of current implementation/platforms (continuing) OpenCycleMap licensing fees for bulk downloading

Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)] Continue new feature work

Needs Approval to move the map attribution links to a separate page Discussion about OpenCycleMap licensing and bulk downloading (need at least small business sign up) Minimum supported web browsers

Week 9 (10/17/2016 - 10/23/2016)

Progress Worked on btc-app issue/feature 22 - forgot password page (spent time setting up server and models locally to continue work) [Austin] Fixed and integrated authentication patches [Sam] Wrote proposed feature priorities [Sam] Attempted to fix cache issue (btc-app issue 60) [Jeremy] Attempted to fix user-point association issue [Asma]	Risks Lack of attention to following chosen process methodology (continuing - will be more relevant once we begin transition from bug fixes to feature additions) Difficulty learning technical details of current implementation/platforms (continuing)
Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)]	Needs Approval on feature priorities Any new features wanted for 1.0

Week 8 (10/10/2016 - 10/16/2016)

Progress Fixed btc-app bugs 13, 52, 54, 55, 56; btc-app server bugs 20, 22; btc-models bug 10. [Sam] Continued filing and screening new bugs as they are discovered. [Sam] Worked on btc-app issue/feature 22 - forgot password page. [Austin] Reviewed several of Sam’s fixes. Fixed btc-app issue-12. [Jeremy] Worked on associating points to the user they belong to (not completed). [Asma]	Risks Lack of attention to following chosen process methodology (continuing - will be more relevant once we begin transition from bug fixes to feature additions) Difficulty learning technical details of current implementation/platforms (continuing)
Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)]	Needs Results of CouchDB admin evaluation Results of last week’s build evaluation Flow for reset password (Do we need a front end web server running to make this work?) Approval to raise iOS minimum Discussion of tiered build release process (or when that might happen)

Week 7 (10/3/2016 - 10/9/2016)

Progress Started work on fixing download track button [Austin] Got server build to deploy [Sam] Filed/fixed various build/documentation bugs in various repos [Sam] Fixed btc-app issue 30, publishing after closing the app [Sam] Fixed btc-app issue 2, seeing large cards on iOS [Sam] Fixed btc-app issue 15, message on publish page with no points to publish [Jeremy] Fixed btc-app issue 39, password confirmation field [Asma]

Risks Lack of attention to following chosen process methodology (continuing - will be more relevant once we begin transition from bug fixes to feature additions) Difficulty learning technical details of current implementation/platforms (continuing)

Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)]

Needs None

Week 6 (9/26/2016 - 10/2/2016)

Progress Got iOS version to submit to iTunes Connect [Sam] Fixed btc-app issue 3, needing to tap more than once on buttons on iOS [Sam] Remove username from all layers of the app [Asma] Fixed button visibility issue on Track page [Austin]	Risks Lack of attention to following chosen process methodology (continuing - will be more relevant once we begin transition from bug fixes to feature additions) Difficulty learning technical details of current implementation/platforms (continuing)
Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)]	Needs None

Week 5 (9/19/16 - 9/25/16)

Progress Resolved Chrome Remote Debugger issue - now debug-ready. Reported btc-app issue 22, began investigating issue btc-app issue 12 [Jeremy] Started on Track Page issues. Bugs # 9 and 11 [Austin] Got iOS branch fully building and into master [Sam, Asma] Fixed 2 causes of Android white screens on older Androids [Sam] Explicitly set minimum OSs [Sam]	Risks Lack of attention to following chosen process methodology (continuing - will be more relevant once we begin transition from bug fixes to feature additions) Difficulty learning technical details of current implementation/platforms (continuing)
Plans Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [All (Specific bugs assigned on GitHub)]	Needs Approval on exact minimum OSs Approval on calling app “BTC” on phone home screens Distribution channel for iOS builds

Week 4 (9/12/16 - 9/18/16)

Progress Setup emulator on personal machine, investigating indefinite white screen issue on both the emulator/device [Jeremy] Got iOS building, fixed iOS white screen issue, investigated various methods of debugging [Sam] Found correct domain model [Austin] Investigated login issue; CouchDB is not the problem; found suspect file [Asma]	Risks Lack of attention to following chosen process methodology (continuing) Difficulty learning technical details of current implementation/platforms (continuing)
Plans Continue clearing blockages interfering with debug efforts [Jeremy] Continue to find, log, and fix more bugs (prioritizing high priority work-blocking bugs) [Sam, Austin] Research suspect file related to login issue [Asma]	Needs iOS developer account for Adventure Cycling (to sign test builds and possibly use TestFlight) Volunteers to test the iOS version

Week 3 (9/06/16 - 9/11/16)

Progress Fixed infrastructure scripts for automated server deployment [Sam] Got server running in AWS [Sam] Got an emulator to display the app [Asma] Register issue : 400 error [Asma] Register issue: pwd field on form/on request is not being evaluated on server side. [Asma] Registration: Works on Sam’s laptop but not on mine. Might be a CouchDB connection issue. However, login doesn’t work for him. [Asma] Project Plan [Austin, Jeremy]

Risks Lack of attention to following chosen process methodology Difficulty learning technical details of current implementation / platforms (continuing)

Plans Find, log, and fix more bugs that cause the app to appear unresponsive [Sam] Fix Register/Login bug [Asma] Finish Project Plan [Austin, Jeremy] Finish Domain Model

Needs Approval from John on project description

Week 2 (8/29/16 - 9/05/16)

Progress Website [Sam] Project Synopsis [Austin] Project Plan [Austin, Jeremy] Methodology Research/Decision [all] Code review process [Sam]	Risks Difficulty learning technical details of current implementation/platforms Two developers don’t have Android phones (for Android app). Two developers don’t have iPhones (for iOS app).
Plans Crashing Errors [Sam] Login issue [Asma] Work on Project Plan [Austin, Jeremy] Work on Domain Model [all]	Needs Can we edit Domain Model or use existing one?

Week 1 (8/22/16 - 8/28/16)

Progress Set up Github [Sam] Set up Slack [Austin] Reserved room & microphone [Asma] Determined when and where to meet [all] Ran current app [all]	Risks JavaScript Difficulty learning technical details of current implementation/platforms Sub-optimal process methodology adoption Biting off more than we can chew / scope creep
Plans Start fixing bugs (sponsor meeting dependent) [all]	Needs Feature list Bug list SE team account

---