Lightning in a Bottle - InterConnect 2015
•Download as PPTX, PDF•
0 likes•361 views
The story about how we took a research idea into a worldwide success in a matter of months. And then, how we took the lessons learned and processes developed and expanded them to a wider global community.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Lightning in a Bottle - InterConnect 2015
Similar to Lightning in a Bottle - InterConnect 2015 (20)
Recently uploaded
Recently uploaded (20)
Lightning in a Bottle - InterConnect 2015
- 1. © 2014 IBM Corporation Lightning in a Bottle Steve Abrams Patrick Wagstrom
- 2. 1
- 3. Rule 1: Know Your User
- 7. Enabling Technologies Lean Startup Hypotheses IBM Design Thinking Hills
- 8. Design Thinking Hills for SXSW • Hill 1: The Watson Life team will gauge interest in a cognitive cooking assistant using data collected during the event • Hill 2: The Watson Life team will compare/contrast multiple user experience offerings using data collected during the event (UX) • Hill 3: The Watson Life team will infer more about their current personas using data collected during the event 7
- 9. Testing Two Different Interfaces 8
- 11. Rule 2: Use IBM Bluemix DevOps Services
- 12. Plan 11
- 13. Develop 12
- 14. Automate 13
- 16. Rule 3: Use IBM Bluemix
- 17. Load Balancer Web Server Web Server Web Server Database Database (Backup) Authentication Provider Push Provider Automatic Scaling Monitoring and Analytics Web Application Architecture
- 19. “Are you sure you want to own that?”
- 20. Focus on Core Competencies 19
- 21. Expand with the Catalog 20
- 22. Global Team 21
- 23. Global Apps
- 24. Rule 4: Use Watson Developer Cloud Services
- 27. Ramping Up and Out 26
- 28. 27
- 29. Key takeaways • Know Your User – Design thinking and Lean Startup • Get your process in order – IBM Bluemix DevOps Services • Focus on your core competencies – Use IBM Bluemix • Go Cognitive – Watson Developer Cloud Services 28
- 30. Thank You
Editor's Notes
- This is a little bit of a difficult thing to explain, but it’s key to the rest of this talk. In any organization there are always reasons why you can revisit a topic, particularly a technical topic, over and over. Often times it is easy to have another set of discussions about a topic rather than moving forward with action. When we speak of a bias toward action we’re not suggesting that teams just march ahead without regards to the consequences, rather we’re suggesting that if the debate comes down to “Should we move ahead with this?” that in the absence of other evidence the scales should be tilted toward moving forward. Now, you might be saying “Sure, but there are consequences to moving forward, particularly if there are problems with what you’ve done!”, and you know what, you’re right. However, it’s always easier to say “No”. Saying “Yes” means that you’re taking a risk. In the rest of this talk we’re going to discuss four rules that we’ve developed that help to mitigate those risks.
- This is a little bit of a difficult thing to explain, but it’s key to the rest of this talk. In any organization there are always reasons why you can revisit a topic, particularly a technical topic, over and over. Often times it is easy to have another set of discussions about a topic rather than moving forward with action. When we speak of a bias toward action we’re not suggesting that teams just march ahead without regards to the consequences, rather we’re suggesting that if the debate comes down to “Should we move ahead with this?” that in the absence of other evidence the scales should be tilted toward moving forward. Now, you might be saying “Sure, but there are consequences to moving forward, particularly if there are problems with what you’ve done!”, and you know what, you’re right. However, it’s always easier to say “No”. Saying “Yes” means that you’re taking a risk. In the rest of this talk we’re going to discuss four rules that we’ve developed that help to mitigate those risks.
- Best Practices: 1. Create lots of small projects (architect for micro services) 2. Share liberally 3. Don’t be afraid to branch 4. Use code reviews when branching back in 5. Automate everything But if we’re always branching, how do we actually test? Testing requires some infrastructure and for complex environments you can’t have everyone with their complete clone of the infrastructure, can you?
- The key thing is that Bluemix is a platform. While it’s possible to port many applications to Bluemix, if you have a highly specialized environment then it’s likely that you’re going to face some challenges as you may already have elements in your architecture that limit your ability to migrate. By designing around Bluemix in the first place, and rethinking some of your challenges, not only will you end up with no need to own your infrastructure, which is win for you and your developers, but you’ll also end making your application more flexible should you move in the future.
- Even if you’ve managed to get all that stuff installed and running, now you also need to manage any major security incidents that arise. In the last year we’ve seen three critical faults spread across the net that needed timely updates. If you’ve got some developers managing the machines are you sure that you want to trust that they’re going to watch out for all of these defects? Even beyond the defects, are you certain that they’re going to secure everything properly? Beyond that there’s all sorts of reasons that you can have problems. Denial of service, Reddit Hugged/Slashdotted to death, etc.
- Nearly immediately after we fanned out and started to expand our reach across the company we started to get all sorts of quest
- Using Bluemix helps us focus on what’s really important for us – which is understanding the user…
- Serendipitous discovery of useful applications BACK TO STEVE] – Not only that, but bluemix made it easeir for us to scale our team mission across a global IBM. Our teams across the US and in India, China, Africa were able to run similar experiments, rapidly deploying apps on bluemix as part of their user research and rapid prototyping effforts. [Need screen grabs for Speak/be-heard + Career advisor, and MaD OR FTD]
- Personality Insights Relationship Extraction Message Resonance Concept Extraction
- So, that’s all fine, but how did we get here? Well, we knew that we couldn’t do this with just our little team. However, we knew that we could take what our team had learned and teach other teams how to apply the same methods. We’re going to talk about a handful of these projects, what they did, and how they utilized Bluemix and DevOps Services in order to create innovate applications very quickly.