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:
Keynote: Predictability and Measurement with Kanban
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
David J. Anderson explains how to use predictability, measurement and change management to balance the factors of observed capability, staffing, and delivery targets to achieve predictable outcomes.
Bio
David J. Anderson is the author of "Agile Management for Software Engineering", a signatory of the PM Declaration of Interdependence and a founder of the APLN, an original member of the "Singapore Project" where Feature Driven Development emerged, and vice president of the Lean Software and Systems Consortium.
About the conference
Agile Cambridge 2011 is for anyone who wants to successfully apply or learn more about Adopting and evolving agile approaches; Agile software development; Agile product management; Agile testing; DevOps/Agile Operations; User experience and design in an agile world; Agile technical communications; Coaching and mentoring agile teams; Leadership; Tool and technology adoption; Distributed agile teams. The focus throughout the event is on sharing practical experience of these topics, in a range of sessions from beginner to expert.
David J. Anderson explains how to use predictability, measurement and change management to balance the factors of observed capability, staffing, and delivery targets to achieve predictable outcomes.
Bio
David J. Anderson is the author of "Agile Management for Software Engineering", a signatory of the PM Declaration of Interdependence and a founder of the APLN, an original member of the "Singapore Project" where Feature Driven Development emerged, and vice president of the Lean Software and Systems Consortium.
About the conference
Agile Cambridge 2011 is for anyone who wants to successfully apply or learn more about Adopting and evolving agile approaches; Agile software development; Agile product management; Agile testing; DevOps/Agile Operations; User experience and design in an agile world; Agile technical communications; Coaching and mentoring agile teams; Leadership; Tool and technology adoption; Distributed agile teams. The focus throughout the event is on sharing practical experience of these topics, in a range of sessions from beginner to expert.
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
Just want to clarify the sigma values
by
steve zhang
Posted
Importance of velocity
by
sameh zeid
Posted
-
Hi, David,
I am not sure where are the sigma values come from, you mentioned in your presentation:
1 sigma = 85%
2 sigma = 98%
But based on my understanding of standard deviation, en.wikipedia.org/wiki/Standard_deviation
1 sigma = 68%
2 sigma = 95% -
Story-point sizing is higly relative to the request size based on team judgement. From my view, Throughput is business metric and defining it in-terms of story-points might not bring the value if we defined it interms of the request itself.
Your presentation is great and asnwers many of the problems I see happening in IT projects.
2 comments
Watch Thread Reply