A product backlog left unattended can become large and unmaintainable. The common approach of reviewing and updating the backlog regularly might be ineffective in the longer term, demanding alternatives to backlog grooming.
Nick Malik, an Enterprise Architect at Microsoft, wrote a blog post differentiating business analysts from business architects and he received a swift rebuke of his stance. Malik contended that business analysts do fundamentally different work than business architects but Kevin Brennen of the IIBA strongly disagreed and pointed out the resemblances between the roles.
Historically, some product owners have prioritized backlogs by making pairwise comparison of projected economic return between two items in isolation. Successful Agile teams often take a holistic approach, accounting for risk, dependencies, and the complex interplay among and across backlog items.
The International Institute for Business Analysis and the Agile Alliance have collaborated on a volunteer program to produce the Agile Extension to the Business Analysis Body of Knowledge. The Extension has now been released for public comment and feedback.
An alarming study by Flyvbjerg and Budzier published in the Harvard Business Review has made everyone stand-up and take notice. The coherent advice being that IT projects are much more riskier than we think.
The International Institute of Business Analysis announced the release of a first draft of the Introduction for the Agile Extension to the Business Analysis Body of Knowledge at Agile 2010 today. They are looking for participation and feedback from Agile practitioners and business analysis professionals.
FlightCaster recently open sourced Crane, a tool for distributing and remotely controlling Clojure instances, currently specialized for EC2. Incanter is a Clojure library and tool that makes R-like statistical computations easy with Clojure. Also: the build and dependency management tool Leiningen 1.0 is now available.
Caliper calculates various metrics – for example code duplication and complexity – for your Ruby code; all you need is a public Git repository.
Wakoopa, a new start-up based in Amsterdam, Holland, has created a new social network aimed at discovering and sharing what applications people are using. While its user base is relatively small and geek oriented, the network provides useful insight on software usage with a social twist.
TargetProcess has released a free 5-user Community Edition of its Agile project management software. The Community Edition contains the same features as the full edition of the product with two limitations: a maximum 5 users, and no support.
VersionOne, a maker of agile project management tools, has announced that the third annual 'State of Agile Development' survey is open for participation. The online survey is intended to gauge the value of agile development practices in the field. Results will be announced on August 4th, at the Agile 2008 conference in Toronto.
Return on Investment is a critical factor for decision making pertaining to following a particular software development practice. The post summarizes the ROI benefits of Agile and the inexpensive practices which lead to highest return on investment.
In February 2008, Dr. Dobb's conducted a survey on Agile adoption and the success rate of Agile software development. The survey revealed some interesting results on various parameters, including: adoption, scalability, iteration length, and team location.
This recent inquiry, by InfoQ China editor Jacky Li, looked at five very different cases of Scrum adoption in China, which got different results. He asked: Why did you use Scrum? How did you adopt it? What problems did you encounter, and why did it succeed or fail? Despite the small sample size, it's an interesting comparison, pointing out that improvement doesn't ensure success.