Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Five Key Practices to Agile ALM
Transforming Software Delivery: An IBM Rational Case Study
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
Just replace the word agile with any other change that you want accomplished ... and the presentation will be equally impressive.
Agile requires specific questions to be answered ... setandbma.wordpress.com/2008/12/01/off-shoring-...
Hi,
I think the approach outlined in the video is what most agile coaches seems to propose, and I mostly agree. Thanks for putting this together Tamara.
I found some things to that probably do not agree:
- The whole thing with creating the name and the logo for the change. I think a lot of smart people is advocating NOT to name change initiatives. I can think of several reasons: 1) To prevent resistance from people tired of named change programs. 2) To prevent resistance in general, if it does not have a name it is harder to whack it. 3) It is not supposed to be a program that ends some time, it is supposed to be a new culture of learning, problem solving, inspect adapt.
- Creating Best Practices. 1) I think Taichi Ohno said that once you define the best way to do anything it is all over. You will kill future innovation. 2) I am a strong believer that teams need to contribute to a process to feel that they own it. By dong this it will be sustainable change. It will also ensure that the teams keepsdeveloping the process. Best Practices is dangerous stuff...
Best Regards
Henrik
www.cedur.se/index_us.html
Just another one of the million Agile consultants in the market.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
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.
3 comments
Watch Thread Reply