The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
How would you like to view the presentation?
Five Key Practices to Agile ALM
Transforming Software Delivery: An IBM Rational Case Study
Agility at scale, become as agile as you can be
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
I found the presentation extremely (pun intended) interesting. I know I have sometimes used the parallel change "pattern" myself without even realizing how useful it could be in other situations.
What I was thinking about (and I don't think any of the questions presented by the audience touched this) was how does this apply to acceptance test driven development. Acceptance tests are by definition written beforehand, because their meaning is to a) make the story more understandable for the team and to b) make sure that the requirements of the story are really met. They are typically "red" until the functionalities they require are implemented, thus the story is more or less "done".
Maybe failing new (story) acceptance tests shouldn't even show up as red, but as yellow or something. On the other hand, they do tell that there is work in progress, which should be limited. If we create just one test at a time, we miss the big picture completely, which doesn't seem like a good idea, either.
Is there something crucial I'm missing here?
Paralell Change is one of the design principles in Kent Beck's responsive design theme. It was also presented on a qcon last year.
Hi Daniel,
I've been using the term Parallel Change for at least 4 years now, talking about it in my Refactoring Strategies & Tactics tutorials (formerly called Patterns of Refactoring) and showing videos of these strategies in my Refactoring eLearning album (bit.ly/9T5S9I). So it may just be that Kent selected a similar name to mine. I have to read his stuff and see how close it relates to the technique I'm referring to.
Here are a few more Refactoring strategies I've been writing about over the years:
* Piecemeal Change
* Gradual Change
* Narrowed Change
* Sequence Change
* Evolved Target
* Unified Methods
* Graceful Retreat
I will blog about these one day.
I don't think you're missing anything. If you do ATDD (or as we call it, Storytest-Driven Development), you will have work-in-progress and it will be good to work in such a way that you aren't "in the red" for very long periods of time, even though they will be longer than if you were just doing TDD.
BTW, there was a time when we did ATDD all of the time and now we're much more selective about doing it.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
4 comments
Watch Thread Reply