How the Hub's development works and an introduction to the concept of Sprints
Jason Gush
The NZ ORCID Hub is being developed according to the Agile approach with agreed aspects of the overall plan broken into manageable regular work cycles, aka sprints, with each sprint having an agreed series of tasks or issues to address. For this project, a two-week sprint cycle has been adopted with each sprint involving the following communication timetable:
· Week 1
o Tuesday – What this sprint is about
o Thursday – Review Product Roadmap; status update; and discussion of any barriers or problems
· Week 2
o Tuesday – Healthcheck of sprint plan, and review issue backlog
o Thursday – Demonstration of anything that’s ready
These Tuesday and Thursday sessions are conducted from 2:00 pm to 2:30 pm over the University of Auckland’s Zoom video-conferencing system.
Observers are welcome, especially to the the Week 2 demonstrations. Please note beginning 2 March, we intend to record the initial part of each session to provide a record of the hubs development and relevant deliberations; however, record will stop if the floor is opened to a Q&A from participants.
Sprint zero, involved finalising the projects Bill of Materials, i.e., agreeing development tools and hosting arrangements, and the creation of an initial batch of user stories, and collection of credentials for the necessary test environments, was completed 17 February. As of time of posting we are in the midst of Sprint 1, which is to: set up the relevant domains, environments and hosting arrangements and to obtain necessary credentials and permissions for the hub. The first demonstration is scheduled for 2 March, with the sprint ending 3 March before the cycle begins again the next week with Sprint 2. Summaries of each sprint will in future be posted here in the week following the Sprint's conclusion.
A key place to follow both sprints and development issues is the NZ ORCID Hub in JIRA.