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.
Posted by Vikas Hazrati on May 26, 2009
Recently Mike Cottmeyer recommended a list of books for traditional project managers and new teams trying to make a move towards Agile. He listed the following books, along with a short reason for adding them to the list
Most of the books on this list are also present on the “Top 20 Agile Development Books, Ever” prepared by Jurgen Appelo. Jurgen used the following approach for coming up with the list
A few books from Jurgen’s list include
Agile Tortoise also recommended a series of Agile books and categorized them on the basis of
Ryan Cooper, suggested his list of 10 Must-Read books for people already doing Agile development and others who are curious to learn Agile but are still skeptical. Apart from the books already mentioned above, Ryan mentioned a list of books which deal with people, communication and risk management. His list included
18 agile and lean practices for effective software development governance
Agility at scale, become as agile as you can be
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Wow quite a list! Covers all the books that I should have on my bookshelf. Would be a good starting point for anyone who is new to agile.
I think we all take a stab at this. Mine:
Key Books: www.notesfromatooluser.com/2007/11/best-agile-b...
Background Material: www.notesfromatooluser.com/2007/11/best-agile-b...
Development/Code Related: www.notesfromatooluser.com/2007/11/best-agile-b...
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