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 Deborah Hartmann on May 19, 2006 02:10 PM
Tom Looy, Thoughtworks PM, blogs on things he'd like to pass on to his son. In this entry he reflects on an absurdity at the root of traditional planning. So, quickly: how long is a piece of string?... It's a pretty silly question, isn't it? But would you believe that questions like that are asked all the time regarding IT projects? And what is even more amazing is that people actually give answers to such vague questions and then they make important business decisions based on them.In a departure from traditional project management practice, Agile rejects "big up-front" phases, like planning and design. Instead, Agile projects proceed empirically, that is to say, by means of experimentation and reflection: planning and executing incrementally and adapting along the way.
5 Ways to Ensure Application Performance
Give-away eBook – Confessions of an IT Manager
The Agile Business Analyst: Skills and Techniques needed for Agile
Why is that hard? You keep going till you get to the end, then that's how long it is ;-)
Funny enough, I've been in projects that felt very similiar to your algorithm. The only difference is that the ends were tied together...
Funny enough, I've been in projects that felt very similiar to your algorithm. The only difference is that the ends were tied together...
I think you must have made a typo in saying to avoid planning...it's big up-front requirements gathering you want to avoid, that and the falacy of estimates. Planning is always required, and is what allows the project to adapt along the way.
Or you can make more complex, so you can be seen like a cool PM: always devide the string in 2 and show your team the half :-). ./alex -- :Architect of InfoQ.com: .w( the_mindstorm )p.
You are right! It's a typo. Thanks --deb
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.
6 comments
Watch Thread Reply