Tag: distribution

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. 

---

Agile at Scale: 7+7 Practices for Enterprise Agility
Part II of II - Seven Additional Practices For Enterprise Agility

In part I of this Article, we noted that the benefits of agile software methods, including faster time to market, better responsiveness to changing customer needs and higher quality are undeniable to those who have mastered these practices. However, these practices have been developed and refined in circumstances characterized by small, co-located teams with ready access to a customer. Can enterprises building applications that require hundreds of distributed team members benefit from these practices, or are they forever doomed to large, late, stage-gate and waterfall-like results?

---

An Agile Approach To Managing Distributed Development
Traditional approaches to distributed development impair flexibility: they don't expose what's actually happening on the ground in different locations, they lack common and effective communication channels, and they substitute "hope" for "managed process" when reconciling work. Distributed development should be as responsive to change as co-located teams.  A program managing distributed development requires behaviors that engender agility.  Three contributing factors are release cadence, transparency of activity, and lightweight communications.

---

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.

---