Readers/Web/Team/Retrospectives/2014-11-24

= 27 October 2014 =

I Know What You Did Last Sprint (11/10/14-11/21/14)
Notable events:
 * Sam haz baby!
 * Jon remote
 * Rob wuz in SF
 * megateam retrospective/developer backlog
 * WikiGrok A/B test begins
 * Joaquin first iteration remote
 * Bugzilla closed

Absences:
 * Rob sick ( 3 horrible days ) (11/17-19)
 * Sam out (11/16-28)

Points carried over from previous iteration: 8 Points attempted: 35.5 Points completed: 41.5

Velocity chart: https://docs.google.com/a/wikimedia.org/spreadsheet/ccc?key=0AqEdtQuSLdAxdGF0Unlob2MtRmZTeU4tODJXbk9rQ1E&usp=drive_web#gid=1

Actions from last retrospective: https://docs.google.com/a/wikimedia.org/document/d/1NqzIX9hXJbaY-ke6uWThKFBEj7CUweSQrw6cCR_fGcY/edit

= Outstanding from Previous =
 * Make sure Kaldari and Joaquin sync up on WikiGrok before he leaves SF [Kaldari, Joaquin] DONE
 * Give Rob access to WD dbs on tool labs [Kaldari] DONE
 * keep hashing out (on email) ways to get prototypes out for testing quickly [Team]
 * have the option of using user scripts now
 * still don't have a concrete plan
 * we have 2 derploy windows now; aren't using b/c we are A/B testing
 * Table for now, revisit
 * email to Timo and Antoine to figure out how we can avoid getting blocked by Jenkins and not being able to reach people about problems [Jon]
 * Jon has been in touch, still not clear what to do
 * have more undersanding of how it works, but not sure we want to open the can of worms
 * need bigger, prioritized, fleshed out backlog for our new megateam (noted that we might need to allocate more meeting time to fleshing it out) [Maryana]
 * Put together a meeting of whole mobile web team and Lydia/WikiData folk to get everyone on the same page [Maryana]
 * Kaldari is feeling awesome! We're figuring out good ways to work around their codebase :P

What's been working well?

 * Getting ppl from other teams do WD stuff for us
 * -1 code review column - I think it should come before the 'In Development' column
 * Epic amount of work being done
 * Tools tools tools
 * Analytics dashboards less messy
 * Maryana/Kaldari asked me questions outside story estimation, helped spec out stories making estimation meeting go more smoothly.
 * Being super agile & pivoting around Wikidata blockers :)
 * Developers backlog +
 * Collaborating with Analytics to figure out cheap suggestions
 * QAing WikiGrok A/B test (hopefully)
 * dry run is a good thing!
 * Different focus areas e.g. tools and wikigrok

What hasn't worked well?

 * REGRESSIONS!!1 / no QA it's coming next week :) +++
 * Specialist Guild is starting next week!
 * figure out devices and browsers that we want them to focus on
 * Joaquin had some info from Nuria that we could use
 * specific features/areas that have lots of regressions, let Maryana know
 * Let Maryana know if you want to sit on on meeting?
 * ios bugs
 * bugs in A/B test for wikigrok :-/
 * Browser tests as per usual.
 * adjusting the test's scope or design after launching it: we did a good job but with some coordination we could have saved some kittens
 * people not replying to emails e.g. developer backlog next theme. Are people getting too many? - yep
 * better organize cards (labels?)
 * state and speed of tests
 * bugzilla closed and we can't make comments anymore+

What is confusing?
like writing mobile web using a modern web framework so we move faster and can build MODERN web things, unlike our current product +++++++++++++++ ** megaproblem needs mega discussion; could use structured conversation ** can developer backlog help smooth the way? ** Goal: crush app team! :P ** Action!: Doughnut meeting, loop in Damon? Make Damon aware of problems we are facing Moiz/Kaldari set agenda, get it scheduled!
 * Why is Wikipedia banned in China
 * When we pull stuff from dev backlog into iterations +
 * Whether Bahodir is an awesome code producing robot or a real human+
 * Whether we can keep the developer backlog full of work at the rate this time is able to do stuff
 * Now I dont have Trello gold how are we going to get backgrounds+
 * Phrabricator +++++
 * need to get used to it
 * how does it fit in to our workflow?
 * migration will make sense once there's code review
 * Action! Set up a meeting to talk about bug triage [KRISTEN]
 * How to spell Fabrikaethure
 * We are a megateam now and we should tackle some mega problems...