Agile Topics:
- They are largely going to be following our scrum processes (documentation, user story writing, sprint schedule) as closely as they can.
- Our Jira board will contain all of their user stories for the sprint, but the subtasks, planning, etc. will be managed on a separate board that they manage
- Our board will also contain all backlog items for the entire project so that the Product Owners can plan and prioritize the entire platform from a centralized location
- Story points for their stories will not be added to our board, they will keep track of it separately
Meetings:
- Oak ridge will participate in our planning and demo meetings, but they will handle their sprints individually otherwise. We discussed doing a Scrum of Scrums, which may be necessary but it will likely depend on how much interaction will be needed between the teams during the sprint.
- Ideally ORNL will demo their components and stories they are responsible for. The BAH team will not be responsible for preparing the materials, but we may need to be there for QA and getting their components up and running prior to the demo to ensure they are working as expected.
Code/ Architecture:
- As of right now, they will work within their own repo as a standalone Kafka service. We will be working to get them integrated within the JPO repo, but their code will be a separate project
- They are currently running the ODE as the providing service of data, we discussed possible ways to decrease the onboarding time, as their service is almost standalone.