Garrett Eardley explores how Riot Games is leveraging Riak for their stats system, discussing why they chose Riak, the data model and indexes, and strategies for working with eventually consistent data.
Ronny Kohavi shares lessons learned, cultural and scaling challenges conducting hundreds of concurrent online controlled experiments at Bing.
Bjarte Bogsnes discusses Beyond Budgeting and tackling budgeting issues in traditional management, the Statoil "Ambition to Action" management model with implementation experiences and advice.
Stephen Hardisty presents how Etsy delivers products without having project managers, business analysts, or testers.
Guy Dugas, Angie Duncan, Barb Spurway, Kevin Giles discuss about the roles, skills and competencies of business analysts, challenges and experiences, and how they have delivered value.
Jonathan Seidman and Ramesh Venkataramaiah present how they run R on Hadoop in order to perform distributed analysis on large data sets, including some alternatives to their solution.
Nathan Marz explain Storm, a distributed fault-tolerant and real-time computational system currently used by Twitter to keep statistics on user clicks for every URL and domain.
In this presentation from SOA Symposium 2010, Manas Deb and Clemens Utschig-Utschig discuss how to derive business agility from SOA and BPM, motivations for agility, developing and nurturing agility, influencers and dependencies, how SOA and BPM enable agility, pitfalls and recommendations for organizational culture, and pitfalls and recommendations for business and technical architectures.
Hilary Mason presents the history of machine learning covering some of the most significant developments taking place over the last two decades, especially the fundamental math and algorithmic tools employed. She also exemplifies how machine learning is used by bit.ly to discover various statistical information about users.
At a recent IIBA New Zealand members event Shane and Pete debated the role of the business analyst on Agile projects. Shane presented on why analysis is so important on Agile projects, and why the role of the analyst remains crucial to project success. Pete said that the traditional role of the Business Analyst is under threat and will need to evolve in order to be valued on an Agile project
Agile methods are empirical: plan, do, evaluate how it went, plan the next thing. When these cycles are very short, learning happens quickly and teams can move into high-performance mode. But discipline is necessary - planning must happen continuously to feed the fast-moving team. For 80 minutes David Hussman looks at the Agile practices around planning a project, a release, and an iteration.