The question is no longer how best to automate business systems, but rather how to improve what's already been automated. We are nearly finished with the initial wave of IT adoption and most of what can be automated already has been. This means that the essential set of features and functions required to run a business already exists in some form. The trick is how to reuse and repurpose existing investments for additional value.

Tags: agile, anticipated, application, applications, architectural, architecture, architectures, capabilities, communicating, communication, conjunction, functionality, heterogeneity, implementing, improvements, incrementally, infrastructure, participates, participation, propositions, specifically, standardization, successfully, technologies, transactional, transformation,

Click to add your tags...,

or Close

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.

Tags: administered, agile, applications, architectural, architecture, automatically, availability, communicating, communication, configuration, consistently, continuously, corporations, distribution, environments, establishing, implementation, implementations, infrastructure, logiclibrary, organization, organizational, organizations, realistically, repositories, requirements,

Click to add your tags...,

or Close

Tool integrations are notoriously fragile; how can we fix this problem once and for all?

The first sign of trouble is the unusually long time it takes for your IDE to start one morning. Maybe you can't access the trouble tickets any more or the team members cannot build their applications or run the automated test suite.

Tags: agile, applications, architecture, architectures, capabilities, collaboration, collaborative, configuration, functionality, heterogeneous, implementation, independently, infrastructure, infrastructures, interdependency, interoperability, interoperable, orchestration, orchestrations, organizations, proliferation, responsibility, simultaneously, standardizing, straightforward, technological,

Click to add your tags...,

or Close

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. 

Tags: agile, categorization, certification, characteristics, consistently, consolidated, consolidates, consolidating, cruisecontrol, deficiencies, implementing, inconsistently, instrumentation, intrinsically, methodologies, organization, organizational, organizations, requirements, responsiveness, specification, subsequently, successfully, thoughtworks, transparency, transparently,

Click to add your tags...,

or Close

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?

Tags: accomplished, agile, agilealliance, approximately, characterizes, continuously, correspondingly, definebuildtest, demonstrated, differentiates, distractions, entrepreneur, functionality, fundamentally, infrastructure, methodologist, multiplexing, organizational, organizations, prescriptive, productivity, professionals, requirements, requisitepro, scale specifically, scalespecifically, substantially,

Click to add your tags...,

or Close