NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

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

...


Goal

Assigned To

Accomplished?

1

Streamline C3D export and ETL process

Phil/LilyYes
2

Test data upload repeatedly (ETL)

Ye/Phil/AmitYes
3

Conduct Demonstration (one internally and one for client)

Matt/AmitWill be done except client
4

Provide specific vocabulary for data model (BRIDG)

MarkPartial
5

Define specific constraints to graph data model (e.g., required vs. optional)

PhilPartial
6

Conduct test of native graph vs. post-gres/graph

MarkPartial
7

Define team GitHub process and educate the team.

AmitPartial


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.
Matthew B
Suggestions for ImprovementTime box, clear scope, bit sized piecesMatthew BSuggestions for Improvementestimation of ticket duration and hence when it needs to be split into smaller tickets
What WorkedScrum appears to be more efficient.
Matthew B
Suggestions for Improvementput retrospective comments in without being nagged.Matthew BSuggestions for ImprovementCapture dependencies of tickets
What WorkedGood to have Erika there in Scrum
Matthew BWhat
Didn't WorkTeam members missing standups did not allow for good flow of information
WorkedTeam Chemistry is really good.  Never boring.
Matthew BWhat WorkedDemo provided a solid goal for performance.
Matthew BSuggestions for ImprovementIf QA is not necessary, go right to close.
Matthew BSuggestions for Improvementtransfer tickets when done with your part to next person for QA (if needed).
Matthew BSuggestions for ImprovementCould try doing sprint loading based on velocity.
Matthew BSuggestions for ImprovementPeople should try to record ticket updates (including closure) as soon as possible to best affect burndown rate
Philip 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
.

Tickets

Sprint 3

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