Agile and Beyond - The Power of Aspirational Teams
Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.
Tracking change and innovation in the enterprise software development community
Posted by Mark Levison on Jun 17, 2008 09:09 AM
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.
The Agile Business Analyst: Skills and Techniques needed for Agile
Scaling Agile on large teams & Being Agile every day Tracks @ QCon SF Nov 19-21
Six Free Project Management Certification Training Courses
Gamma's Jazz platform's first implementation: Rational Team Concert (Trial Download)
Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.
Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.
Nick Sieger talks about the future of JRuby, Java Integration, and his work on JEE deployment tools for Ruby on Rails like Warbler.
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
No comments
Reply