When defining a business case for adopting agile, the question can arise how you can measure the business value that can be delivered using agile software development.
LinkedIn’s DataFu project, a collection of libraries for Hadoop, has now officially entered the incubation status at the Apache Software Foundation (ASF) since the first week of January.
At the XP Days Benelux conference, Paul Kuijten did a session called "kill all projects" where he questioned if getting rid of all projects could be a good idea. InfoQ did an interview with Paul about project management practices that can be valuable for agile, and the funding of product development.
Mobile Backend as a Service provider AnyPresence continues to hone their chops. Launching the fifth update to their self-titled platform geared for the enterprise. Co-founder Rich Mendis provides some insights for InfoQ readers…
Organizations adopt agile to be able to handle changes. Agile helps teams to deliver products that satisfy the needs of customers; products which do not contain unneeded (and unused) features. Lean software development says: everything not adding value to the customer is considered to be waste. How can a transition from waterfall to agile software development help organizations to reduce waste?
There is a need for the public sector to adopt agile software development methods. Two case studies which show how agile has been used for the FBI, and at the Port of Rotterdam in the Netherlands.
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.