Natasha Sayce-Zelem - Surviving the beast

Presented at Hey! #20 on 3rd November, 2015.

Transcript

2. Hello…
4. Head of Technolog
7. Broadcast fixed deadlines
8. Broadcast fixed deadlines
9. BBC Sport refresh
10. BBC Sport refresh
12. BBC Live
13. BBC Live
15. Surviving a few beasts…
16. Surviving a few beasts…
17. Who are your stakeholders?
18. Who are your stakeholders?
19. Who are your stakeholders?
20. Who are your stakeholders?
21. Who are your stakeholders?
22. Who are your stakeholders?
25. • What is our goal? • Define problem and who our customer is • What do we want to learn? • What’s the minimum we can build to test that? • How do we measure success?
26. Build a platform for live events that can be easily tailored to suit a wide range of events, which we can continually iterate and improve over time to provide the best-possible experience across four screens - PC, tablet, mobile and connected TV. The underlying technology had to be scalable across the BBC, giving us the capability to bring even more live events to audiences digitally.
 Speed/load was a key consideration with live events as we’d need to update the page more frequently. GOAL PROBLEM
27. We used Socket.IO and Sock JS using node.js to see how quickly we could achieve horizontal scaling to n users for the back end…
 

28. We used Socket.IO and Sock JS using node.js to see how quickly we could achieve horizontal scaling to n users for the back end…
 
 We needed a stable, scalable, future proof framework that would enable use to create inter-actionable components. We spiked using Backbone, Ember and Angular
 
 In the end we chose Angular for the front end
29. Comms
30. Comms
39. Delivery and approach
40. Visibility of progress Know how fast the team is working – and how many sprints will deliver the proposed MVP time = (<points> / <velocity>) * <iteration length> e.g. time = (300 pts / 20 pts) * 2 weeks = 30 weeks (or 15 iterations)
41. Visibility of progress Know how fast the team is working – and how many sprints will deliver the proposed MVP time = (<points> / <velocity>) * <iteration length> e.g. time = (300 pts / 20 pts) * 2 weeks = 30 weeks (or 15 iterations)
42. MVP
46. Parallel Tracks development +2 sprints (ideation) +1 sprint (design) 0 (current sprint) -1 (last sprint)
49. Shiny HAPPY people
50. Shiny HAPPY people
51. Shiny HAPPY people GDS chief Mike Bracken CBE shared the secret of how to make a happy workplace with an American audience in 2013
 “Hire the very finest minds in digital and dress them in onesies. Have some fun while you’re doing it. Insist on Hawaiian shirts – absolutely de rigueur. Make sure your insignia is good. And have lots of cake. And make sure there's stickers. You can’t beat a few stickers for your laptop!” Source: TheRegister

52. Shiny HAPPY people GDS chief Mike Bracken CBE shared the secret of how to make a happy workplace with an American audience in 2013
 “Hire the very finest minds in digital and dress them in onesies. Have some fun while you’re doing it. Insist on Hawaiian shirts – absolutely de rigueur. Make sure your insignia is good. And have lots of cake. And make sure there's stickers. You can’t beat a few stickers for your laptop!” Source: TheRegister

53. Shiny HAPPY people GDS chief Mike Bracken CBE shared the secret of how to make a happy workplace with an American audience in 2013
 “Hire the very finest minds in digital and dress them in onesies. Have some fun while you’re doing it. Insist on Hawaiian shirts – absolutely de rigueur. Make sure your insignia is good. And have lots of cake. And make sure there's stickers. You can’t beat a few stickers for your laptop!” Source: TheRegister

55. TRUST
56. TRUST
57. Team members need to think of the rest of the team as "us", not "them” 
 You need to trust that taking time to help others won't make you look unproductive. 
 You need to trust that you'll be treated with respect when you ask for help
58. Always be honest about your achievements. 
 Avoid the temptation to whitewash problems or misrepresent partially-done work.
 
 Create a no blame culture
59. Your team – Tuckman’s Model
60. Your team – Tuckman’s Model
61. Your team – Tuckman’s Model
62. Your team – Tuckman’s Model
63. Your team – Tuckman’s Model
75. • Blog posts • Conferences / brownbag sessions • Github / Behance / Dribbble • Washup • Awards
76. Any questions? I’m on that Twitter too… @unharmonic