...
- Sam Im (Deactivated) to provide an overview of the OpenLMIS process and workflow between the team leads at 9:00am Pacific/12:00pm Eastern (backup is 7:00 Pacific)
- Team RetrospectivesPreviously-used slides: OpenLMIS Agile Practices google slides plus pull from VillageReach Agile slides (more content on estimation/points/burndown).
- Sprint Process
- Team Grooming Backlog (when/where)
- Team Estimation
- Team Sprint planning
- Daily Team Stand-ups
- Daily updates (end of day)
- Sprint Showcase
- Team Retrospectives
- Communication channels and expectations (meeting notes, flagging priorities in JIRA, responding to mentions)
- QA Process (what the Jira board columns mean, dev to QA hand-off, epics, tickets, tasks)
- rules about ticket types, priority, etc: Software Development Methodology
- rules for reporting bugs, priority, etc: Contribution Guide > Reporting Bugs
- Definition of Done: Developer expectations and definition of done (Understand the current definition, coding standards, code reviews in Fisheye or GitHub) We may need to amend this in the future with Josh as the dev team is onboarded.
- Shared Calendars
- Are we tracking a GAP sprint, or a team sprint in Jira? (Sam to present options so that a decision can be made on Friday - considerations for the importance of tracking velocity by team, shared QA resource, etc)Developer process and definition of done (Understand the current definition) We may need to amend this in the future with Josh.
3. Set expectations on project start dates
...