Scrum in eBuddy
•
0 recomendaciones•873 vistas
Short intro about eBuddy and our Scrum flow.
Recomendados
Más contenido relacionado
Destacado
Destacado (20)
Scrum in eBuddy
- 2. Agenda! • Introduction! • Agile buzzwords! • Scrum in eBuddy! • Constraints!
- 3. Who am I?!
- 5. 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! ! !
- 7. Buzzwords!
- 8. Uncertainty! variables DEFINED PROCESS CONTROL! EMIPIRICAL PROCESS CONTROL! Theoretical! Complexity! Technologies! Deterministic! Requirements! Transparency! shared product backlog! user stories People Simple?! es>mate velocity standardized input burn-up/ down charts! definition of done! cookbook random output! Inspection! frequent standardized output daily stand-ups! code review no evalua>on cost Adaptation! open communication! Scrum Waterfall retrospective ! Kanban re-prioritisation ! XP TDD
- 10. Management Stakeholders Needs (Users, Sales, Traffic, 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
- 11. Dev Teams! • 8 Teams! • 2 teams – 6 products! • Velocity planning vs Release planning!
- 12. Definition 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!
- 13. 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 configurations eclipse! – Refactor the code whenever it makes sense! • MEETINGS! – Review the working agreement and definition of done in the retrospective! – DECLINE meetings without agendas! – Don't interrupt others! ! • RESPONSIBILITIES:! – @PO, Setup meetings for Go/No-Go! – Live issues: Drop everything and fix it! Call the on-call person.!
- 14. Retrospective! • Different approaches depending on how the sprint went! – Boat! – Stickies board (plus and minus)! – Feelings chart! – Example: http://innovationgames.com/speed-boat/!
- 15. Constraints!
- 16. • 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
- 17. Scrum surfaces issues! Communication!
- 18. Q&A!