-
Notifications
You must be signed in to change notification settings - Fork 0
Goldilocks
judytuna edited this page Sep 28, 2012
·
6 revisions
- Goals: in 10 weeks, we'll have:
- an "insight engine" comprised of an algorithm augmented with human wizards that delivers insights via email and mobile app
- a "wizard interface" web app that allows human wizards to log/check insights
- a mobile app on iOS that shows a customer their insights
- Project Roles and Responsibilities
- Client: Optality
- Product owner Eli Dezelak
- Customer Team Members: Tony Levitan, Eli Dezelak, Ramesh Jain, Rockhaya Fountila, Kathleen Knopoff
- Blazing Cloud
- Product Champion Judy
- Account manager Bill?
- Lead developer ?
- Project manager Bill? Judy? Sarah?
- Team members: Sarah, Bill, Judy, Mason, Kane, Curtis, Divya, Bonnie, Loredana, Anton, Cameron, Latsamy
- Client: Optality
- Meeting times (make sure there are no overlaps with other projects; if
this is not possible, at least no overlaps for team members)
- Planning: Tuesday 10/2
- Daily standup:
- Review/Acceptance:
- Retro:
- Continous integration URL:
- Tracker project: https://www.pivotaltracker.com/projects/623287/
- Deployment
- When:
- Preconditions:
- Afterwards:
- Production: http://motifmvp.com
- Staging: http://motifmvp-staging.herokuapp.com
- Development:
- Additional documentation: https://github.com/blazingcloud/goldilocks-landing/wiki/Dev-Setup
- Communication:
- This page :-)
- Project wiki: https://github.com/blazingcloud/goldilocks-landing/wiki/
- IRC Channel/Chat/AIM/blah:
- judy skype: judytuna
- Mailing list:
- Onboarding
- 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
- Integration tests are
- Software used rspec, rr, activeadmin, resque
- Etc.
- Team schedule