Sphinx is a web based project management catalog and event subscription system. The goal of this system is to provide visibility and communication about projects within an organization. Employees will be able to browse through their companies projects using various search criteria, subscribe to project related events, and receive periodic updates about their subscribed projects when aspects about them change. Users of the system will also be able to comment on projects with their feedback and vote if they like or dislike a project.
Week | Planned Activities / Accomplishments |
---|---|
Week 1 ( 1/28-2/4 ) | Begin Sprint 4 ( 1/28/ - 2/18 ) |
Refamiliarize with the project | |
Begin planning for semester 2
| |
Update documentation risks | |
Update website | |
Continue researching new alternatives for streaming | |
Complete database migration | |
Create mockups of entity pages | |
Set up test database and populate | |
Week 2 ( 2/4-2/11 ) | |
There will be a different page for initiatives, milestones and risks
| |
The user shall be able to subscribe to an entity from the entity page | |
Week 3 ( 2/11-2/18 ) | |
The user shall be able to click on a learn more link | |
The user shall be able to subscribe to an initiative from the dashboard | |
The user shall be able to view all their entity subscriptions from the main page | |
Week 4 ( 2/18-2/25 ) | |
End Sprint 4, Begin Sprint 5 ( 2/18 - 3/11 ) | |
Week 5 ( 2/25-3/4 ) | |
Week 6 ( 3/4-3/11 ) | |
Week 7 ( 3/11-3/18) | |
End Sprint 5, Begin Sprint 6 | |
Week 8 ( 3/18-3/25 ) | |
Spring Break ( 3/25-4/1 ) | |
Week 9 ( 4/1-4/8 ) | |
Week 10 ( 4/8-4/15 ) | |
End Sprint 6, Begin Sprint 7 | |
Week 11 ( 4/15-4/22 ) | |
Week 12 ( 4/22-4/29 ) | |
Week 13 ( 4/29-5/6 ) | |
End Sprint 7 | |
Begin Final Deliverables | |
Final cleanup | |
Week 14 ( 5/6-5/13 ) | |
Final Presentation Complete | |
CD with all deliverables | |
Poster | |
Post mortem reflection | |
Technical report | |
Week 15 ( 5/15-5/20 ) (Presentations) | |
Week | Planned Activities / Accomplishments |
---|---|
Week 2 | Create Github project |
Create project synopsis | |
Create project website - www.se.rit.edu/~venture | |
Set up VM | |
Week 3 | Submit project synopsis and get approved |
Request VM (Linux) | |
Publish roles and responsibilities on the website | |
Submit first draft of project plan completed for review | |
Week 4 | Add development methodology to website |
Add product/process metrics on project website | |
Create User Stories | |
Start Product Backlog and begin estimating | |
Week 5 | Complete Requirements Document |
Complete Sequence Diagrams | |
Week 6 | End of Sprint 0 (10/01) |
Complete initial wireframes | |
Complete Architecture Diagrams | |
Week 7 | Peer Evaluations |
Week 8 | Get Elasticsearch up and running on VM |
Start prioritizing features and estimating their time | |
Get play to interact with Mongo DB | |
Create presentation for mid-semester review | |
Week 9 | End of Sprint 1 (10/0115) |
Final versions of documents | |
Second pass of Project Schedule - Emphasis on Semester 1 | |
Start Sprint 2 | |
Users' homepage shall have a feed of their current projects. | |
Mid-semester project review with sponsor | |
Get sign offs on completed documents | |
Review Project Schedule for this Semester | |
Go over team review | |
Week 10 | Sprint 2 - Week 2 |
Week 11 | Sprint 2 - Week 3 |
Week 12 | End Sprint 2 |
Demo 1 (Nov 12th) | |
User Story: user's homepage shall have a feed of their current projects | |
Begin Sprint 3 | |
Homepage shall have a project of team's projects coming up | |
Homepage shall have new projects coming up across the firm | |
Week 13 | Start sprint 3 week 2 |
Rough draft of presentation | |
Homepage shall have a project of team's projects coming up | |
Homepage shall have new projects coming up across the firm | |
Streaming in feeds | |
Getting data through the REST client into our database | |
Week 14 | NO MEETING (Thanksgiving) |
Week 15 | Semester Presentation Week |
Final Presentation of the Semester | |
Final Demo |