Eventually Consistent HTTP with Statebox and Riak
Bob Ippolito explains how to solve concurrent update conflicts with Statebox, an open source library for automatic conflict resolution, running on top of Riak.
Presentation
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
Scaling Lean & Agile: Large, Multisite or Offshore Delivery
- Sections
- Process & Practices
- Topics
- Team Collaboration ,
- Distributed Team ,
- Collaboration ,
- QCon London 2011 ,
- Offshoring ,
- Teamwork ,
- Agile in the Enterprise ,
- QCon ,
- Scrum ,
- Agile Techniques ,
- Business Models ,
- Lean ,
- Architecture ,
- Agile ,
- Conferences ,
- Business
-
- The next QCon is in London March 5-9, Join us!
How would you like to view the presentation?
In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
Craig Larman presents practices and tips related to adoption, structure, requirements, contracts, architecture and design, offshore, multisite development, and coordination with large Scrum teams.
Bio
Craig Larman is a management and organizational-design consultant for enterprise adoptions and large-scale product delivery with Lean principles and large-scale Scrum. He is the co-author of Scaling Lean & Agile Development: Thinking & Organizational Tools, and Practices for Scaling Lean & Agile Development: Large, Multisite, & Offshore Product Development with Large-Scale Scrum.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Craig Larman presents practices and tips related to adoption, structure, requirements, contracts, architecture and design, offshore, multisite development, and coordination with large Scrum teams.
Bio
Craig Larman is a management and organizational-design consultant for enterprise adoptions and large-scale product delivery with Lean principles and large-scale Scrum. He is the co-author of Scaling Lean & Agile Development: Thinking & Organizational Tools, and Practices for Scaling Lean & Agile Development: Large, Multisite, & Offshore Product Development with Large-Scale Scrum.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
RelatedVendorContent
Five Key Practices to Agile ALM
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Agile Maturity Model Applied to Building and Releasing Software
Related Sponsor
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
- This article is part of a featured topic series on Agile Techniques and also Agile
- See more Agile Techniques content at: http://www.infoq.com/agile_techniques
- See more Agile content at: http://www.infoq.com/agile
- Other recent content items in this topic
Query
by
Ajay Kumar
Posted
Great talk!
by
Andreas Meyer
Posted
Feature teams scale
by
Andreas Meyer
Posted
great stuff
by
suba bose
Posted
-
Hi Craig,
I was able to understand your perspective on large scale software development model. One point which I am not convinced that if we do not set architectural constrains before starting development there are chances where each team can go in different direction to implement same common component. Example could be exception handling guideline or may be some common component. I have given two features to two development team and both the team may come up with different approach and different component for exception handling. This will not solve purpose of reuse of same component.
Thanks,
Ajay -
Well, found this talk very impressive and I feel impressed by the framework 1 and 2 and how this scales to such great number of teams around the world. I imagine how great it would be to work in such environment.
Ajay, I understand your point, but I think this is a high level view and in daily practise there arise so much problems and complicated situations, which are not shown here. Your architectural question is one of them, but there are a couple of more, like adressing the "right" feature team, and let them come/work together to solve the problems.
I'll believe architectural issues are demistified while designing sessions if the teams are addressed and dive into the problem domain. The architecture documentation past release is great :-)
I do fully agree with the crossfunctional teams, the role of architecture (and architects, no powerpoint architects) in agile development.
It sounds to me more KANBAN than SCRUM though some SCRUM ceremonies are manifested.
Great job, Craig. I ordered the books immediately to dive more into the details and get more tips. -
Hi Craig,
most interesting is that feature teams scale and component orientated teams did not. You are assuming bigger components that only one teams owns, right?
Are multiple fine grained components in some requirements area that "owns" a team similiar to your what you have called "feature teams"? -
key takeway: component teams lead to waterfall.
4 comments
Watch Thread Reply