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 Mark Levison on Jun 17, 2008
Scott Ambler, author of Refactoring Databases: Evolutionary Database Design, writing for Cutter IT Journal has written about how Agile methods can be adapted for Data Warehousing and Business Intelligence systems. Scott and his co-authors are writing for an audience who's users are suffering from large centrally designed systems.
In Scott's opinion mainstream Data Warehousing projects often fall short of user's expectations:
End users commonly complain that the delivered BI capability does not keep
pace with rapidly evolving business requirements and that the BI development team does not engage effectively with the user community. Requirements are collected at the beginning of the process, then the BI development team defines an architecture, general design, and detailed design based on the initial understanding of the requirements. The BI team often recognizes that user involvement is important through these development phases, but this involvement is very limited once the project starts.
Beyond the adoption of an Agile approach Scott has a few other key recommendations:
It is important to recognize that there can be several truths and to identify those truths, .... The driving principle should not be purity of the definition but the timely delivery of important business value.
To read more visit the free download of the Cutter IT Journal and enter the promotion code BUSINESSINTELLIGENCE.
Agile Maturity Model Applied to Building and Releasing Software
SCM best practices for multiple processes, releases & distributed teams
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!
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.
No comments
Watch Thread Reply