While Scrum and other agile methodologies have made inroads since 1990s, much has changed. Startups and enterprises with workforces spread across time zones can no longer co-locate their employees as they were once expected to be able to. As the world shrinks, organizations are finding themselves in a position to decouple the software development approach from traditional means. We see open source everywhere in 2015 -- with the diversity of teams developing for the most popular open source projects, one wonders how to succeed without the benefit of managers, meetings, and code sprints?
With "open development," decisions are made in public view, and Project Managers and engineers are responsible for their own actions -- autonomous but accountable. The approach emphasizes more than just code delivery, but collaboration and transparency. The other aspect of open development method is in keeping the peer review process business-like and professional.
Another consideration is the role of software patents, an issue that remains controversial in the software industry. There has also been much discussion in the software development community over the increasing use of Web 2.0-style software services, otherwise known as Software as a Service (SaaS) or the ‘Service Cloud’.
As part of an open development method, code quality is paramount, so code should be legible, able to be tested, module and minimally verbose. Each of these factors benefits not only the development team, but stakeholders (and, ultimately, end users). Here's a quick summary of the open development philosophy.
No comments:
Post a Comment