Covering Sprints 5 through 7.
Jason Gush
View the Sprint reports on Jira from the links below:
Sprint 5
With the core of the Hub’s launch functions established. Sprint 5 centered on improving the security (i.e., serving over https with a sound SSL certificate and hardened server config) and polishing the flow of researcher interactions.
17/04/2017 - 28/04/2017
Sprint 6
The main effort for Sprint 6 was to stand up a Hub instance for user testing, i.e., https://test.orcidhub.org.nz/. This involved linking the test Hub to the Production Tuakiri Federation, unlike the dev Hub, which uses the TEST Tuakiri Federation. Effort was also put into improving the Technical Contact flow for onboarding.
01/05/2017 - 12/05/2017
Sprint 7
Sprint 7 was a continuation of polish and bug hunting, with the new functionality limited to addressing the needs for Organisation Administrators that are not also Technical Contacts, and giving the users a positive indication of when their ORCID iD has been recorded by the Hub.
The Test hub was promoted and users from Tuakiri-member organisations encouraged to test their ability to interact with the ORCID sandbox.
15/05/2017 - 26/05/2017