2018 4 20 Sprint Process overview for gap kickoff

Attendees

@Sam Im (Deactivated), @Brandon Bowersox-Johnson, @Chris Opit (Unlicensed), @Craig Appl (Unlicensed), @Ashraf

Agenda

• Sprint Process:

•  

  1. Team Grooming Backlog (when/where)

  2. Team Estimation

  3. Team Sprint planning

  4. Daily Team Stand-ups

  5. Daily updates (end of day)

  6. Sprint Showcase

  7. 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

Expected Outcome: Set expectations for sprint artifacts, daily processes, and communication. Assign roles, and begin setting up sprint meetings.

Slides

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 (Deactivated) please talk with Sam about Tech Committee timing.

• Retrospective - Sam

  • (Boardthing access was later added to the Next Steps list below.)

• Sprint Schedule - Sam (slide 33)

• ~~ CONTINUED Monday 23 April 2018 ~~

• Jira Board - Sam

  • Question: How do we move the tickets across the columns?

• Daily stand-up - Sam

  • Question: Should the team lead of each team facilitate the daily stand-up? YES.

  • Question: Should we also hold a scrum-of-scrums? NO, at least not initially.

  • Question: Could we invite the product owner to participate? YES. How often? Not every day. DISCUSSION of the capacity within the organization to understand the requirements.

• Burn-down chart - Sam

  • Comment: Do more backlog grooming and tracking within Jira itself.

  • As long as we have Jira sprint configured and ticket points, we don't want to have to build these charts on our own.

  • Moving a ticket to done automatically updates the chart. Moving the ticket to Done needs to meet the overall definition of done.

• Sprint Schedule - Sam

  • Agreed: We will all start our sprint on Wednesday and all work on the same 2-week cycle. We can adjust the schedule later after that if/when needed.

  • What meeting tool? Ona uses Google Hangouts. JSI uses WebEx but would be fine using Zoom if needed.

  • JSI starting May 2, writing tickets and getting ready to start sprint May 9. Ona starting April 25. And we will schedule it so all the teams are starting a new sprint on the same day.

• Communication - Sam

  • To recap: Team lead/scrummaster will post a daily message about their burn-down and any blockers/critical tickets that other teams need to respond to.

• QA Process - Sam

  • Automated testing (using Jasmine and Cucumber)? Is this part of the definition of done?

Meeting Recording

(should be available soon in Zoom OpenLMIS account in https://zoom.us/recording)

Next Steps