Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Abel Avram on Aug 17, 2008 02:08 PM
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.
Agile Development: A Manager's Roadmap for Success
5 Ways to Ensure Application Performance
Effective Management of Static Analysis Vulnerabilities and Defects
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
3 comments
Watch Thread Reply