Goals
Goal | Accomplished? | |
---|---|---|
1 | Standup basic Gen3 system | Yes |
2 | Establish Data Model | Yes |
3 | Explore options for data storage and retrieval | Yes |
4 | Acquire Data to load into database | Yes |
5 | Establish connections with holders of data | Yes |
Retrospective Results
Author | Category | Card Title |
---|---|---|
Philip M | Suggestions for Improvement | As far as possible, given the sudden flux concerning the importance of the COTC trial data, develop high-level sprint goals for a couple of sprints out? Will greatly help detailed sprint planning. |
Matthew B | Suggestions for Improvement | Time box, clear scope, bit sized pieces |
Matthew B | Suggestions for Improvement | estimation of ticket duration and hence when it needs to be split into smaller tickets |
Matthew B | Suggestions for Improvement | put retrospective comments in without being nagged. |
Matthew B | Suggestions for Improvement | Capture dependencies of tickets |
Matthew B | What Didn't Work | Team members missing standups did not allow for good flow of information |
Philip M | What Didn't Work | Sprint 0 was way too long, and lacked the organization that you'd normally want to see. That situation should have been resolved with our new sprint cadence, associated ceremonies, etc. |
Philip M | What Worked | In my opinion, our ability communicate via Slack has already contributed to the effectiveness of the team to a very significant degree, and it will only do so more as sprints get busier. |
Matthew B | What Worked | establishing initial rules and meetings for sprints allowed us to organize |
Philip M | What Worked | Having a second stand up meeting each week has been a big improvement in terms of discussing incremental progress. |
John F | What Worked | Getting started and making progress and not waiting for everything to be in place before moving. |
John F | What Worked | The team is gelling and sharing thoughts and getting work done. |
Ye W | What Worked | Great team chemistry and dynamics. |
Bugs
Future
Tickets