...
Sam Im (Deactivated), Brandon Bowersox-Johnson, Chris Opit (Unlicensed), Craig Appl (Unlicensed), Ashraf
Agenda
- 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
...
https://docs.google.com/presentation/d/1hd0Qt5R98Suzi7NWG5jS6gZVYgqGvwFe8qphCYRZPW8/
Notes
- Goals/Agenda Review
- Craig: Let's talk specifically about the Slack daily communication. There is a lot of it each day. Why? For what purpose? Who is the audience?
- Sam: We might not get through whole agenda today.
- Sprint Process - Sam
- Sprint - Sam
- Craig: What if we take on 10 points, but only finish 8? Is that a failure? What happens?
- (Discussion...Brandon: It is not about punishing us for failure, but it IS about giving quick data to the decision makers to know if things are taking longer. More on this to come later.)
- Backlog Grooming - Sam
- Ashraf: Chris would be doing ticket writing, with assistance from Ashraf if needed. About Acceptance Criteria and Definition Of Done, Chris and I both reviewed the OpenLMIS guides for that. We went through it and we can relate to it.
- Chris: The documentation is quite comprehensive. I think the process will work.
- Sam: This project will also have shared QA resources. It's important to have the QA role reviewing the tickets. They may know of edge cases to add, and it helps them understand how to test the feature.
- Ashraf: What is the ideal approach to bring the QA person in and to write the tickets?
- Sam: We might have a session with the architect and also the QA person. They all sit and talk about what we want with this ticket. The ticket-writing session does not need to be perfect.
- Ashraf: What type of event is it? (More discussion not transcribed....)
- Ashraf: Can it be iterative that the ticket gets improved while the sprint is going? Getting SME input, etc? Sam: Agile process lends itself to ambiguity. You can present work at showcase and decide to revise it during another sprint. The goal of the grooming is just to try to capture what we know now and reduce ambiguity over time.
- Craig: How do I know right level of size?
- Brandon: It is too big if it cannot get done in a sprint.
- Sprint Planning - Sam
- Ashraf: "Commit or don't" means what? It refers to whether the team agrees to (not code commits in git).
- Ashraf: Zephyr for test plans and Balsamiq for mockups? Do we have access? Sam will set up access.
- (Skipped Jira board section because of time)
- Showcase meeting - Sam
- Ashraf: Some developers will join from Ethiopia and there are internet challenges, audio challenges, etc. So in those cases, can the lead (like Chris) present the work? Another option also is they could record a simple screencast video of the feature and share that in advance for review/discussion.
- Craig: I am worried about the scheduling of these global calls. Most of our developers are currently 10 hours ahead of Seattle time, and during winter it will be 11 hours ahead. The current time won't work. Showcase and Technical Committee are the two that are really a challenge because we want the developers to join in to both. Josh Zamor please talk with Sam about Tech Committee timing.
- Retrospective - Sam
- Sprint Schedule - Sam (slide 33)
- TO BE CONTINUED SAME TIME DAY MONDAY
Meeting Recording
(should be available soon in Zoom OpenLMIS account in https://zoom.us/recording)
Next Steps
- Sam Im (Deactivated) set up Zephyr and MyBalsamiq access to Ashraf, Chris, Craig
- Sam Im (Deactivated) schedule a session on Zephyr test cases and process