Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Free Book Offer
SOA Demystified
$40 Value
Posted by Abel Avram on Aug 17, 2008
In this presentation filmed during Agile 2008, Ron Jeffries and Chet Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense in the software development world.
Watch: Natural Laws of Software Development (1h 30 min.)
Ron and Chet say that, usually, in business, nothing goes according to the plan, but in all other businesses, except software development, they know before hand they are not going to meet the deadline, and proceed accordingly. We need to provide the same ability to have predictability. It is not possible to have predictability if one is given all the specifications and attempts to complete an entire project before a deadline is met because nobody knows for sure how much of the project has been done. Instead, if the project is approached step by step by doing chucks of it, one could figure out if the project is in graphic or not.
Ron and Chet continue by saying that if we deliver Running Tested Features, then the business management can have predictability, early releases, and will request high value features first, which in end will be a return of investment. Businesses need incremental software development: "if they have it, they can manage it, make more money with it, understand what's going on with it."
Defects may be accounted as negative features. Not knowing what they are means not knowing for certain where we are in the development process. An important cause of defects is misunderstanding the requirements, which happens easily when a team has to deal with all of them at once, instead of incrementally receiving and addressing them. Requirements are well understood during conversations person to person. User stories come handy because they open the conversation which conducts to confirmation. The end result is clarity, the clear understanding of requirements.
In that manner, Ron and Chet derive in their presentation all Agile practices as inherent effects of the natural laws of software development.
Learning to be a Good Product Owner: Foundation Skills
VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
3 comments
Watch Thread Reply