About eBuddy! ! 33+ million ! ! monthly active users! ! ! 200+ million ! ! unique downloads to date! ! ! ! 17 billion ! ! messages processed per month! ! ! ! 4+ million ! fans on Facebook! ! ! !eBuddy is web and mobile messaging The Crunchies Awards ! !for everyone, everywhere!! winner: Best international Startup! ! ! ! Mashable Awards ! ! winner: Best Mobile App! ! ! ! Mashable Awards ! ! winner: Best Mobile User Experience! ! !
Management Stakeholders Needs (Users, Sales, Traﬃc, Customer etc.) Roadmap daily scrum Review Product Owner Priori>zed Product Backlog Shippable Product sprint 2-‐weeks poker poker planning planning sprint planning Scrum Master DOD WA Dev Team velocity retrospec>ve ac>on points sprint backlog
Dev Teams!• 8 Teams!• 2 teams – 6 products!• Velocity planning vs Release planning!
Deﬁnition of Done!• STORY! – Test cases written/executed on top devices/ATC! – No critical or blocker bugs! – Code reviewed! – Documentation on wiki( example:protocol changes)! – Dev. testing: performance, feature impact, non-functional requirements! – Accepted by PO!• SPRINT! – Presentation page is updated! – Final Presentation is done on beta! – Retrospective is done!• Release! – All Core test scenarios pass! – Multibackend should work with all clients! – Build is deployed to Beta env! – Analyze stats and Feedback! – Go-No-Go session!
Working Agreement!• QUALITY:! – Do Design meetings for stories and update the documentation! – Code reviews for each major change! – Code documentation: All public methods to indicate what their parameters are! – Use common conﬁgurations eclipse! – Refactor the code whenever it makes sense!• MEETINGS! – Review the working agreement and deﬁnition of done in the retrospective! – DECLINE meetings without agendas! – Dont interrupt others! !• RESPONSIBILITIES:! – @PO, Setup meetings for Go/No-Go! – Live issues: Drop everything and ﬁx it! Call the on-call person.!
Retrospective!• Different approaches depending on how the sprint went! – Boat! – Stickies board (plus and minus)! – Feelings chart! – Example: http://innovationgames.com/speed-boat/!
• Does Scrum fail?! 1. Deadline/cost not nego>able; 2. Releasing to an enterprise ; 3. Adapt aYer releasing – too costly; 4. Customer is not co-‐located; 5. Customer is too busy to give input; 6. Maintenance projects/ Opera>ons