Tag: requirements

The Growing Influence Of Open Source Projects
Two years ago, I began writing about the impact of open source development tools, components, processes and organizational models on corporate IT shops. I worked with a range of development managers that shared a very similar point of view: instead of dismissing the so-called renegade open source projects, the managers emulated these projects' activities and hoped to mimic their success. This trend is only growing and I am intrigued by the ways in which IT shops are looking to the open source community for leadership.

---

Intellectual Property Management Issues for Development

To maximize intellectual property (IP) value and mitigate risk while operating in an open source application development environment, enterprises need to understand the distinction between real and perceived risks and values by utilizing processes, governance and tools. This is particularly important when involving an outsourcing partner. A lack of intellectual property capture and protection makes it harder for the outsourcing company to move from one outsource vendor to another.  As a software development "value chain" evolves over time, with changes in the business and technology environments, the value of leveraging open source software may grow or decrease in value. So it makes sense to understand and review open source arrangements.  In this scenario, if the intellectual properties associated with managing and producing the product are no longer available, significant flexibility will be lost. 

---

FEATURED BOOK: Practical Development Environments - by Matthew B. Doar

Okay - so you're "doing the ‘Agile' thing" with your software development. How about your development environment? Are all the tools in your development environment truly practical?

---

Tackling Offshore Agile Development
As an analyst, I have spoken with hundreds of software developers and managers struggling to improve their delivery capabilities. Many are turning to Agile processes as a means to deliver high quality solutions and at the same time improve time to benefits. And, at the same time, these teams need to work with ever-shrinking budgets. Of all the questions they asked about Agile development in 2005, the most common - and the toughest - was: "Can we take advantage of offshore resources and still use Agile processes?"

---

FEATURED BOOK: Collaboration Explained: Facilitation Skills for Software Project Leaders

Numerous Agile methods and principles emphasize the value of collaboration and self-organization. Most books on the subject of Agile development discuss principles and practices related to planning and development practices. Yet few Agile books delve deeply into the How To's of collaboration, facilitation and project leadership. Collaboration Explained, by Jean Tabaka, does exactly this: it takes the essential skills, methods, and proven practices of successful team leaders and group facilitators, and explains them in detail while also applying them directly to the context of agile software development.

---

“Agile” Versus “agile” Development

There's no question that "agile" is the buzzword of the times for software developers, ISVs, consultants, and businesses, in general. As with most buzzwords, the term is often over-used and mis-used, especially by those trying to portray their products or services in a new light. In the world of software development, the term "agile" is applied to a wide variety of processes, techniques, tools, projects, and phases of the development life cycle. It's important, therefore, to set out some basic definitions and context for the use of the term "agile," especially as it will be used in articles throughout this journal.

---

Make SOA Governance A High Priority

Today's enterprises face growing regulatory pressures with legislation such as the Sarbanes-Oxley Act, the Gramm-Leach-Bliley Act, HIPAA, the Patriot Act and others. As a result, corporate and IT governance - the processes, controls and reporting infrastructure over business and IT activities, respectively - are becoming progressively more pervasive as a means for providing the compliance infrastructure necessary to satisfy this list of complex regulations. Combine this increased pressure for corporate traceability and visibility with the "next big thing" in software, service-oriented architecture (SOA), and you have a challenging governance environment to say the least. SOA's loosely-coupled nature forces IT away from monolithic application development and deployment, and as a result it greatly increases the number of moving parts that must be managed and governed.

---

Agile Processes: Making Metrics Simple

IT organizations, and in particular application development departments, are increasingly under pressure to provide performance and compliance metrics to justify annual spend.  Unfortunately, many metrics campaigns collapse under their own weight: there's no shortage of things to measure, the scope is greater than first appears, measurement needs to happen frequently, and collection is a distraction to traditional software delivery operations. By comparison, Agile processes are uniquely well suited to metrics, providing measurements transparently and consistently as an extension of day-to-day operations. Framed in a scorecard, information collected during an Agile project provides a comprehensive analysis of delivery excellence at the project, program and department levels. 

---

Seven Agile Team Practices That Scale (Part I of II )

The benefits of agile software methods, including faster time to market, better responsiveness to changing customer requirements and higher application quality are undeniable to those who have mastered these practices. Agile practices, however, have been defined and recommended primarily to small team environments where co-location, ready access to interactive customers and small team size are the defining rule.  Are the benefits of agility to be denied to those larger software enterprises who don't share these simple paradigms? Or can the industry learn from these practices and apply some of the core principles to large scale development of applications that require 100, 200 or even 1,000 distributed team members to achieve?

---

And The Agile Survey Says…

In planning the launch of the Agile Journal, CM Crossroads polled its subscribers on their attitudes towards Agile development and to see how the subscribers' values fit with the priorities for the upcoming journal. In February 2006, over 400 IT professionals representing 25 different industries responded to a short online survey. The results showed a very high level of interest in Agile processes and the recognition that responding to changing business requirements and delivering value are the key success factors for development organizations.

---