Get global perspectives on critical business technology issues
Objective, experience-based opinion and insight from a variety of perspectives on the critical IT issues you are faced with every day.
A cursory description of the technical debt problem oversimplifies and overlooks many important details. For instance, the differences between technical debt and other kinds of debt, the different forms of intentional and unintentional technical debt, the specific coding sins that lead to technical debt, or the steps needed to both eliminate current debt and prevent future debt. On that last front, opinions vary widely, from "Run a static code analysis tool once in a while" to "Just don't write poor code." Fortunately, in this issue of Cutter IT Journal, we have many good articles that help flesh out these critical details.
- Technical Debt: The Continued Burden on Software Innovation -- Opening Statement
- Technical Debt: It's Not the Real Problem
- Using Technical Debt to Make Good Decisions
- Managing Technical Debt with the SQALE Method
- The Psychology and Politics of Technical Debt: How We Incur Technical Debt and Why Retiring It Is So Difficult
- Addressing the Hidden Obstacles to Innovation and Digital Disruption
- Vendor-Driven Technical Debt: Why It Matters and What to Do About It
Emerging technologies and digital disruption will transform the enterprise, but they will also transform the ways in which we architect. What will this mean for enterprise architecture in general and for the role of the enterprise architect?
- Disruption and Emergence: What Do They Mean for Enterprise Architecture? — Opening Statement
- Disrupting EA
- Leveraging EA to Incorporate Emerging Technology Trends for Digital Transformation
- Big Data vs. Enterprise Architecture
- Managing Disruption in Enterprise Architecture: The Personal Cloud in Healthcare
- EA for the 21st Century
Technology seems to be moving at the speed of light these days, so we decided to ask Cutter’s team of experts for their insights on some of the technologies and trends that are going to be game changers in 2016 and beyond. In true Cutter IT Journal fashion, our call produced a wide range of opinions on what everyone from C-suite executives to technology managers should plan for as they strive to meet their business and technology goals.
- Technology Trends and Predictions 2016 -- Opening Statement
- Talking the Talk: Advice to C-Suite(rs) About “Game-Changing” Technology
- Let’s Hope 2016 Is the Year of the Ethical Algorithm
- Technology Forecasting Is Not Just About Technology
- 2016 Trends Hitting the Mainstream: Wearables, Machine Intelligence, and Data Visualization
- Agile in 2016: Party out of Bounds
- 2016: The Year That Agile Explodes
- EA in an Age of Terrorism
- The Nine Lives of QA in Software Engineering
- IT Trends for the Next Decade: Does an IT Quantum Leap Lie Ahead?
An unrealized potential to transform existing businesses and industries exists. Many observers have identified a significant gap between organizations' recognition of the importance of new digital technologies currently at their disposal and their understanding of how to optimally exploit them. This signals that many questions surrounding digital transformation are left unanswered and even unidentified. The articles in this special issue help us deepen our understanding of what digital transformation means and provide us with practical advice on how to transform organizations to address the digital world.
- Digital Transformation: Unlocking the Future -- Opening Statement
- Winners, Survivors, & Losers
- Enabling Supernormal Growth into Adjacent Digital Markets
- Five Steps to Digital Transformation
- Transforming Government for the Digital Era: A Simple Rules Strategy
- Breaking Waves: Wearables and the Future of Digitization
- Redefining Boundaries: Insights from the IBM Global C-suite Study
- Moving from "Best Practice" to "Next Practice" to Drive Effective Digital Transformation
- Digital Transformation: Technology Is in the Driver's Seat
Many organizations are still on the fence about moving their infrastructure to an IaaS model. IaaS can be deployed in different models, including on-premises and off-premises, managed by a third party or managed internally, and/or using private or public cloud environments. Which model(s) should an organization adopt? How do firms know if moving their hardware, software, servers, storage, and other infrastructure components to a third-party provider is right for them? Should they consider IaaS only for temporary or experimental workloads? Also worth considering and planning for are the technical/security risks, scalability, and legal/contract issues that are critical to a successful IaaS platform deployment. In this issue of Cutter IT Journal, our authors share their insights on the issues organizations should contemplate before moving to IaaS.
- IaaS: Ready for Liftoff? -- Opening Statement
- What Should a CIO Consider When Running a Cloud RFP?
- Cloud-Native Design -- What Has Changed?
- The Reasons for (and Benefits of) Moving to IaaS: A Case Study at FINRA
- Adopting IaaS: The Legal and Security Issues You Can't Ignore
- Darkness on the Edge of Cloud