zebra

Zebra

• Goals
  • To create app that can help client's customers take and share photos at events.
  • To have feature parity with their existing Android app.
• Project Roles and Responsibilities
  • Client:
    • Product owner: Tim Hoyt
    • Customer Team Members: Tim Hoyt, Louis Zuckerman (dir. of engineering), Juan (Kevin Perez (QA) is no longer with the company)
  • Blazing Cloud
    • Product Champion: Lee
    • Account manager: Sarah
    • Lead developer: Paul
    • Developer:
    • Former team members: Lee (initial dev), Mason (dev), Bill (product champion), Glenna (dev)
• Meeting times (make sure there are no overlaps with other projects; if this is not possible, at least no overlaps for team members)
  • Planning: Depends on build schedule
  • Daily standup
    • Internal: 9:45 a.m. in person
    • With Client: 10:00 a.m. by calling Tim directly (305-400-4660)
  • Review/Acceptance: Depends on build schedule.
  • Retro: Friday at 4:30 p.m.
• Continous integration
  • Development: http://blazingci.local:8080/job/Zebra/
  • Deploy via TestFlight: http://blazingci.local:8080/job/ZebraFlight/
  • Deploy of automated testing app via TestFlight: http://blazingci.local:8080/job/ZebraTestFlight/
• Tracker project: https://www.pivotaltracker.com/projects/463601
• Deployment (the following are in effect while we're in bug fix mode)
  • During development
    • Deploying once we have a build that's useful for the client to test for us to gather more information.
    • Preconditions for sending to client are that the build passes automated tests plus the checklist
  • Before submitting to App Store
    • All automated tests must pass
    • All checklist tests must pass
    • Client must give okay
• Communication:
  • This page :-)
  • Project wiki
  • Mailing list: [email protected]
• Onboarding
  • fill this in
• Source control workflow
  • Each commit should be a logical unit, either representing a story or a task. Comment should include story description, developer notes, and URL back to story if applicable.
• Testing Methodology
  • Unit tests are written in Kiwi
  • Integration tests are written in KIF
  • Additional documentation is on the Wiki
• Team schedule
  • Client team is in Florida
• Android app can be downloaded from client's Jenkins setup (below passwords are for downloading the APK files autogenerated by Jenkins; we don't have logins to view Jenkins itself).
  • user: pmadmin
  • pass: f0t0z@p
  • Production APK: http://goo.gl/TP9ge
  • Staging APK: http://goo.gl/OS0XG
  • See Installing APK file on Android device for more info.