Though collocation is one of the prime recommendations of Agile, more and more projects are executed in a manner in which the teams are distributed. Safari Asad started an interesting discussion on the Scrum Development group to discuss about a project in crisis, which not only had a remote customer but also had remote developers.
Engine Yard, the employer of most of JRuby's core team, started offering commercial support for JRuby this week.
This article explores the structural economic changes brought about by service orientation and how the concept of services and reuse at the service level promises to relieve the enormous pressure arising from increasing costs and flat budgets. Service orientation is compared to other strategies for keeping costs in check.
While the Agile Manifesto says "Customer collaboration over contract negotiation", contracts are a reality for many developers and firms. Peter Stevens has analyzed 10 different types of development contracts, shedding light on how well each style fits an agile project. He has uncovered a couple that seem to fit much better than either fixed-price or time-and-materials.
A debate between SOA and EDA has recently resurfaced with a blog from Richard Veryard, who discusses relationships between SOA, BPM and events
Pierre Bonnet, CTO of Orchestra Networks, argues that information systems are too opaque and not agile enough. He claims this is the main reason why "healthy" multinationals can collapse within months as they take on too much risk. He suggests that information systems be rated on how they manage master data, business rules and business processes.
In this interview made by InfoQ’s Rob Bazinet during RubyFringe 2008, Dan Grigsby talks about programming and entrepreneurship, how a programmer can take his idea and transform it into a successful product.
In his new article at BPM.com, Keith Swenson discusses the relationships between BPM and software engineering. He points out significant differences between the two and cautions against blindly using software engineering approaches for BPM design/implementation.
Software development is challenging and lot of fun, but there are several factors that interrupt teams from succeeding in IT projects. These are usually not tools or technologies but it is the people that affect the success of software projects. In a keynote presentation at the recent CodeMash 2009 conference, Venkat Subramaniam talked about facts and fallacies of everyday software development.
Agile experts James Shore and Diana Larsen will benefit from federal funding to teach two courses in Oregon this month, from Employer Workforce Training Funds and the Oregon Department of Community Colleges and Workforce Development.
The results of SOA case study competition, conducted by SOA Consortium and CIO magazine are showing common themes in SOA implementations. The include strengthening of business IT alliances as the main factor for implementation success and definitions of specific, confirmed by real numbers, business benefits, , as a measure of this success.
Kevin Coleman told his story working with an offshore team that claimed to be 'Agile' and the woes and worries that came with that experience in last month's issue of the Agile Journal. Several readers validated his experience with their own. In practice, can Agile methods be used successfully with offshore teams given today's business reality?
IT has consistently failed to deliver expected value time and time again. According to Ian Thomas, Industrialization (componentization, specialization) may be a solution for supporting software agility and reliability in the new business environment.
According to Clay Shirky, the success key for social software is “a brutally simple mental model [...] shared by all users”. Referring to it as Shirky’s law, Michael Nielsen analyzes why programmers often fail to obey it. His arguments as well as the discussion that has followed provide interesting insights into pitfalls that need to be avoided for building successful social applications.
What is the optimal business model for today’s web? Opinions diverge in a series of articles around this issue. While authors seem to share the conviction that simplicity is the key in web environment, they do not necessarily put the same meaning into this term. Is less really more? Or should it rather be more with less? And how do we achieve it?