![]() |
Page History
Report
Goals
Project | Goal | Assigned to | Accomplished? | |
---|---|---|---|---|
1 | ICDC | Detail out the Program Detail page based on the wireframes and expected functionality. | Yes | |
2 | ICDC | Integrate File Loader with IndexD | Yes | |
3 | ICDC | Present Files in Case Detail on "Checkout" | Yes | |
4 | ICDC | Implement Partial filter functionality on Dashboard | Yes | |
5 | ICDC | Create a case detail view accessible from a link within the cases grid. | Yes | |
6 | ICDC | Extend Data Loader Implementations | Yes | |
7 | ICDC | Implement Diagnoses, Primary Disease Site, Tumor Stage, Gender/Neutered Status Widgets on the Dashboard | Yes | |
8 | ICDC | Create Study Detail Page | Yes | |
9 | ICDC | Create Files View (Embedded in Case Detail Page) | Yes | |
10 | ICDC | Develop the Program View: program cards (Should also include a studies listing for that program), details, link out to program pages. | Yes | |
11 | ICDC | Implement Donut Widgets on Dashboard | Yes | |
12 | ICDC | Solidify SBG Integration | Yes | |
13 | ICDC | Implement Cart functionality | Yes | |
14 | ICDC | Evaluate/build Automated filter functionality tests. | Yes | |
15 | Bento | Define preliminary architecture for submission pipeline | Yes | |
16 | ICDC | Implement new UI design changes | Yes | |
17 | ICDC | Setup ICDC Production Environment | Yes | |
18 | ICDC | Design and Implement Landing Page | Yes | |
19 | ICDC | Auto generate model SVG and Implement view | Yes | |
20 | ICDC | Develop SBG notebook to test integration | Yes | |
21 | ICDC | Setup Dashboard for Alerting for ICDC Operational Performance | Yes | |
22 | ICDC | Prepare for User Acceptance Testing | Yes | |
23 | ICDC | Prepare Minimum Viable Content package for Initial Release | Yes |
Retrospective Results
What went well
Description | Author |
---|---|
Cross functional team works well. | Ye |
Loves her team. Best experience with professionalism. | Hanna |
Team "gels" really well. | Amit |
Front-end team is too modest in their self-assessment - huge improvement in a very short time. | Ming |
Teamwork is awesome. | Yizhen |
Good team dynamics. | Anjan |
Team dynamics are excellent. Positive/Negative feedback is all good. | Dimitri |
All went well. | Ajay |
Like working with Amit and Phil | Laxmi |
Shout out to Ming for helping her and Kevin. | Claire |
Thanks to Phil/Ming/Claire. | Kevin |
UI transformation was phenomenal. Pleased with data team - thanks to Ming. | Phil |
Things are improving with Cloud One. | Vincent |
What could have gone better?
Description | Author |
---|---|
Improve tracking of difficult tasks first. Add prioritizing to tickets. | Ye |
Lessons learned: better planning needed. Setting of expectations. Need clear submission guidelines. Cloud One interactions could be better and are getting better. | Amit. |
Plug-in table (cases, files, etc.) should be re-evaluated. | Yizhen |
We should customize our code - especially the data table (see Yizhen). | Ajay |
Last minute change requests are a problem. e.g., JSON to CSV, Typos. Requirements need to be written. | Sri Kiran |
Last minute changes are difficult. User stories are a consistent problem - no home page user story. | Laxmi |
Need to better define stories, requirements and goals. Agile does not mean knee-jerk. Testing needs to be done earlier - especially not underestimating the static pages. | Phil |
Tickets
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...