-
Notifications
You must be signed in to change notification settings - Fork 11
Meetings
At the beginning of each sprint we discuss what we shipped last sprint and what we plan to ship next, outlining each feature and discussing the “why” as it relates to our longterm roadmap and team KPIs.
This is a weekly meeting (on Monday) where we, as a team, discuss the what, why, and how we're tackling work related to GMV iOS goals.
- What we are planning on tackling for the week.
- A designer will present a quick status update for where they are in a particular part of the design process.
- We look with Ani at how our core “health” analytics metrics are looking and what, if any, improvements we can make.
- We’ll go through issues in the “New Issues” pipeline that you have filed the previous week and move them to their new pipeline.
This is a biweekly standup (on Tuesday) where we talk about everything mobile that is not Artsy, akin to our #mobile-banter Slack channel. It may be about our experiences with technology you’re using for work, but it’s not about team/product goals.
This will be a moment to bring together the designer of a feature and engineer(s) that is/are to work on said feature to walk through the finalised feature and discuss the desired user experience.
Here the goal is to answer the “how”, meaning how will this be implemented. The product of that walk through should be an outline of how the engineer would like the feature spec’ed (i.e. the UI design) and split up into GitHub issues.
As described in Specification, this will also be a time for an engineer to define user-stories with the designer to further understanding of the “who”, “what”, and “why” of features; and as a tool to remember where to pick-up the implementation discussion once the engineer finally gets to work on said feature.
Typically held during the QA period of the sprint, where the engineers go through issues in the ‘Estimation’ pipeline, for which you should prepare as outlined in Planning#estimation.
Held after estimation has been done, where the designer and engineer feature owners determine what requirements need to be finished first and what requirements may be deferred until a later release, as outlined in Planning#prioritisation.