Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[spike] Estimate implementation of update analysis and add new data metadata to existing projects #416

Closed
morrisonnorman opened this issue Jun 19, 2019 · 4 comments
Assignees
Labels
Spike Agile Spike

Comments

@morrisonnorman
Copy link

morrisonnorman commented Jun 19, 2019

RFC

@brianraymor brianraymor added the Spike Agile Spike label Jun 19, 2019
@brianraymor brianraymor changed the title [spike] Estimate implementation of add new data metadata to existing projects Estimate implementation of add new data metadata to existing projects Jun 19, 2019
@brianraymor brianraymor removed the Epic label Jun 25, 2019
@morrisonnorman morrisonnorman changed the title Estimate implementation of add new data metadata to existing projects [spike] Estimate implementation of add new data metadata to existing projects Jun 26, 2019
@morrisonnorman morrisonnorman added this to the Q3 2019 Milestone 1 milestone Jun 26, 2019
@brianraymor
Copy link

brianraymor commented Jul 12, 2019

See AUDR 2019Q3 pre-RFC for evolving design. #dcp-aud-work-group is the slack channel for the working group.

@justincc justincc changed the title [spike] Estimate implementation of add new data metadata to existing projects [spike] Estimate implementation of update analysis and add new data metadata to existing projects Jul 15, 2019
@justincc
Copy link

justincc commented Aug 1, 2019

Analysis updates RFC published. Additions still in progress - will likely not be an RFC.

@justincc
Copy link

Analysis updates RFC oversight reviews ends on Fri 23rd August so may get approved by TA same day or a week later, in which case it slips.

As for additions, as discussed last backlog review there is a 90% case which may largely be already implemented and a 10% case which may not be worth fulfilling in favor of other priorities. However, the 90% case can only be estimated after we complete #468 which is scheduled for the local sprint that ends post milestone 2. On the 10% case, need to consult with @lauraclarke and @morrisonnorman to get a decision as to whether this can be postponed, but since both have been on holiday this has not been possible.

For this reason this task will slip to m3.

@morrisonnorman
Copy link
Author

morrisonnorman commented Sep 11, 2019

The conclusion from this spike is that there are two broad tasks that cover the scope of Add new data and metadata to existing projects (AUDR)

AUDR: Add new files to existing bundles and AUDR: add new bundles to an existing project.

Both of these items require further research on implementation (spikes) for estimation, however it is considered that AUDR: Add new files to existing bundles is high effort with use cases that are currently not high priority.

The priority of these items have been discussed with @justincc @lauraclarke and flagged to PM in an email. The proposal is to deprioritise "AUDR: Add new files to existing bundles” for Q3.

It was considered that there are strategic decisions to be taken wrt AUDR: Add new files to existing bundles that would best be supported by a face to face discussion at the next DCP meeting in October 2019. @justincc Justin will propose this session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Spike Agile Spike
Projects
None yet
Development

No branches or pull requests

3 participants