NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 6

changes.mady.by.user Beyers, Matthew (NIH/NCI) [C]

Saved on

compared with

New Version 7

changes.mady.by.user Beyers, Matthew (NIH/NCI) [C]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Goal

Assigned to

Accomplished?

1Define Minimum Viable Product Plan for Graph based Gen3 and begin design, resource acquisition and development.

2

Begin design for MVP



3Develop resource acquisition plan for MVP


4Begin development for MVP


Retrospective Results

AuthorCategoryCard Title
Philip MSuggestions for ImprovementAs 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.
Comments
Matthew BWhat Didn't WorkProject X really took a bite out of our productivity for this sprint.Amit M, Apr 23 2019 - Indeed!
Matthew BSuggestions for Improvement
Time box, clear scope, bit sized piecesMatthew BSuggestions for Improvementestimation of ticket duration and hence when it needs to be split into smaller tickets
Define teams and team leaders for MVP - Front-end, back-end, Data munging, QA?
Philip MWhat WorkedWe finally opened the lid on user interactions and expectations via Greg TawaAmit M, Apr 23 2019 - Got useful information regarding the submission process.

Matthew B, Apr 23 2019 - Focused on submitter expectations
Philip MWhat Didn't WorkComplications around the NCATS data prevented us from making anywhere near as much progress on getting the data into ICDC as planned for the sprint
Matthew BSuggestions for Improvement
put retrospective comments in without being nagged
Dimitri wants access to source files in future.Matthew B, Apr 23 2019 - raw data access to look at file formats.
Matthew BSuggestions for Improvement
Capture dependencies of ticketsMatthew BWhat Didn't WorkTeam members missing standups did not allow for good flow of informationPhilip MWhat Didn't WorkSprint 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 MWhat WorkedIn 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 BWhat Workedestablishing initial rules and meetings for sprints allowed us to organizePhilip MWhat WorkedHaving a second stand up meeting each week has been a big improvement in terms of discussing incremental progress.John FWhat WorkedGetting started and making progress and not waiting for everything to be in place before moving.John FWhat WorkedThe team is gelling and sharing thoughts and getting work done.Ye WWhat WorkedGreat team chemistry and dynamics
Can we pare back on some of the meetings? - DimitriMatthew B, Apr 23 2019 - Perhaps one weekly team meeting with everyone and no standups?

Matthew B, Apr 23 2019 - Will continue with 2 standups per week, including all team members.  Members need to close/update tickets as soon as possible so that scrum can be faster.  Leads will attend sprint planning meetings.  Retrospectives will be cut down to 15 min and members will enter thoughts earlier (two days before end of sprint).

Tickets


Sprint 5


Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerysprint=1820
serverId7954a81f-12da-3366-a0ef-97c806660e7c