A Focus on Environment — not Enterprise — as the Context for Architecture
I have three related predictions for Enterprise Architects in 2012. Actually they are more like ongoing trends, but they are the ones that I think will be most relevant when making architectural decisions next year. All three could be summarized as a need to focus on environment as context, rather than enterprise.
The Indoor Garden: Cultivating Openness Inside the Organization
Over the last decade, we've been engaged in an exploration of open innovation, crowdsourcing, peer production (such as open source software and Wikipedia), and related phenomena.
The Indoor Garden: Cultivating Openness Inside the Organization
Over the last decade, we've been engaged in an exploration of open innovation, crowdsourcing, peer production (such as open source software and Wikipedia), and related phenomena.
The Indoor Garden: Cultivating Openness Inside the Organization
Over the last decade, we've been engaged in an enthusiastic and far-ranging exploration of various kinds of openness. We've explored open data standards and open application platforms as well as the concept of open innovation in which we seek to leverage both the intellectual property and exploitive capability of external individuals and organizations.
The Indoor Garden: Cultivating Openness Inside the Organization
Over the last decade, we've been engaged in an enthusiastic and far-ranging exploration of various kinds of openness. We've explored open data standards and open application platforms as well as the concept of open innovation in which we seek to leverage both the intellectual property and exploitive capability of external individuals and organizations.
When Technical Debt Hits Life
In my recent Cutter Webinar "Implementing a Technical Debt Prevention, Measurement, and Reduction Program in Your Company" (8 June 2011
Repurposing the Business Analysis Practice for Greater Value
The business analysis profession is in the midst of change. Work is underway within organizations and associations to formalize and standardize what it means to be a business analyst (BA). The role has had a long and tortuous existence. A child of necessity, the role evolved to bridge the gap between what those responsible for operating an organization wanted to do and what those responsible for implementing technology were able to deliver.
Agile Analytics
Watch Ken Collier in this on-demand webinar to learn how to enable the collaboration and continuous realignment of expectations between developers, customers, and managers that agile analytics requires; who makes up the core group of critical project community members without whom the agile analytics project cannot succeed?; the collaboration characteristics shared by effective analytics teams, and how you can become an effective leader who fosters these characteristics.
Agile Analytics
Watch Ken Collier in this on-demand webinar to learn how to enable the collaboration and continuous realignment of expectations between developers, customers, and managers that agile analytics requires; who makes up the core group of critical project community members without whom the agile analytics project cannot succeed?; the collaboration characteristics shared by effective analytics teams, and how you can become an effective leader who fosters these characteristics.
Unified Portfolio Management
To Change or Not to Change?
Take a SCARF to Architecture Reviews
Measuring Collaborative Value
Is Agile Shortchanging the Business?
Agile methods provide a very efficient way to develop software. But efficiency is not the point. As we explore in this Executive Report, the point is that in the rush to experience the virtues of this effective development method, and the excitement of the surrounding publicity, an important question is left unanswered: Does efficient software development (read "agile") necessarily bring a real advantage to the owner of that software? A growing number of our clients are concerned about business value and that the software they take delivery of is not fully exploiting the potential value. To put it another way, there is real business value to be had, but the software development process alone does not deliver it. Clients complain about the lack of innovation coming from agile development teams, and they report that their new software is often not that different from the previous incarnation of the functionality -- a few extra bells and whistles, yes, but not the breakthrough implementation that delivers a significant business advantage.
Is Agile Shortchanging the Business? (Executive Summary)
Agile methods provide a very efficient way to develop software, but in the rush to experience the virtues of this effective development method, an important question is left unanswered: Does efficient software development (read "agile") necessarily bring a real advantage to the owner of that software? In the accompanying Executive Report, we explore this question.