 |
Page History
...
| Project | Goal | Assigned to | Accomplished? | |
|---|---|---|---|---|
| 1 | ICDC | Setup Stage Environment | Yes | |
| 2 | ICDC | Implement UI Improvements | Yes | |
| 3 | ICDC | Detail out the Program Detail page based on the wireframes and expected functionality. | No | |
| 4 | ICDC | Integrate File Loader with IndexD | No | |
| 5 | ICDC | Complete ICDC Draft ATO | No | |
| 6 | ICDC | Sunburst on Dashboard: Design and Implement | Yes | |
| 7 | ICDC | Present Files in Case Detail on "Checkout" | No | |
| 8 | ICDC | Implement Partial filter functionality on Dashboard | No | |
| 9 | ICDC | Create a case detail view accessible from a link within the cases grid. | No | |
| 10 | ICDC | Evaluate System Performance | Yes | |
| 11 | ICDC | Extend Data Loader Implementations | No | |
| 12 | ICDC | Implement Diagnoses, Primary Disease Site, Tumor Stage, Gender/Neutered Status Widgets on the Dashboard | No | |
| 13 | ICDC | Create Study Detail Page | No | |
| 14 | ICDC | Define strategy to integrate with Cloud Resource to push/pull manifest | Yes | |
| 15 | ICDC | Preplan the ATO | Yes | |
| 16 | ICDC | Create Files View (Embedded in Case Detail Page) | No | |
| 17 | ICDC | Setup Versioning Software | Yes | |
| 18 | ICDC | Develop the Program View: program cards (Should also include a studies listing for that program), details, link out to program pages. | No | |
| 19 | ICDC | Implement Donut Widgets on Dashboard | No |
Retrospective Results
What went well
| Description | Author |
|---|---|
Did an incredible work in short time. Hannah’s work is incredible. Getting good design direction. | Dimitri |
Communication is well | Kevin |
| User Interface design is well done communicating the intent of the application. | Mark |
| Communication went well. | Yizhen |
| Team performance is has improved. | Matt |
| Everything went well. | Sri Kiran |
| Collaboration went well. | Vincent |
| Everything went well. | Ajay |
Team collaboration went well. Team dynamics is good. | Amit |
Presentation is feature rich. Team presentation is focused. | John |
| Team is very cooperative. | Siva |
What could have gone better?
| Description | Author |
|---|---|
Coordination between dev and QA. Changes made in dev is not communicated to QA. | Laxmi |
| Review user stories by Developers | Philip |
Implement a process to do a status check of use cases during implementation Request for JIRA permission to move tickets into different permission | Dimitri |
Communication with DCF team needs to be improved. Index processing is to be improved. | Ming |
| Contact Codacy to clarify the react.js security code compliance report | Sri Kiran |
| Suggest to review use cases in QA meeting | Afag |
| Coordination with QA. | Ajay |
DCF communication needs to be improved. Cloud One communication needs to be improved. | Amit |
Tickets
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
