Meetings

Phase 1 Retrospective April 11

What was good?

• we like communication with the Magento team
• response time to the questions was great
• always had deep discussion of topics on our meetings, no time wasted
• we had design discussions and debated different implementations options
• Magento team supported release of the feature efficiently
• The code reviews were timely review
• It is very valuable deliverable implemented as a part of this Project
• all review comments were fixed very fast, review feedback taken responsibly

What can be improved?

• time for synchronization, timezones — To Try have 2 different meetings in differnt timezones
• we had comments for pull requests with conflicting opinion from Magento team — on @vrann to resolve
• more clarity on ideal timeline for Magento release to be hitting — what dates should we fit to get to release, it was not clear; projected date and roadmap — @vrann, put chart on where we should complete piece of work
• feedback from team members blocks development until you get it; - To Try reassigning issues might help — if you need feedback re-assign issue; use ZenHub more intensively; direct messages on slack about blocking issues
• better cadence, more frequent demoes and checkins of work, demo work in progress — on Eugene to schedule
• DoD should include testing and documentation, should we included as we go, not wait till the end — on @vrann provide documentation for community project; what is expectation for us for documentation; create tasks for documentation; document process for devdocs; separate branch for bulk api
• Docs get outdated by the time we finish — on @vrann bring up on the meetings
• Not sure how testing works, need to have it defined — how to run acceptance tests after refactoring — allow more time to get PR open; a lot of tests you can run locally; does magento do manual aceptance testing; documentetion about it
• when we made PR to magento, Travis passes, but then we receive messages that there are errors in tests
• big architectral changes after deliverable was alreday done — not always possible to deliver task earlier; during the development update PR more often;

What we focus on for improvement?

• have 2 different meetings in differnt timezones
• use ZenHub more itensively
• dedicate part of weekly meeting for demo
• identify testing scenarios in PR
• during the development update PR more often
• add WIP label to PR
• push statuses of jenkins to public

Milestone Grooming April 11