Articles

Failure Next Exit sign How to Guarantee Failure in Your Agile DevOps Transformation

Many organizations make the same agile and DevOps scaling mistakes year after year, then attempt to rectify them by putting together a great new strategy—only to miss the reasons causing the failure. If you want to refuse to evolve and, as a result, cause your organization’s agile and DevOps transformation efforts to deliver zero business value, be sure to follow these seven antipatterns.

Mik Kersten's picture Mik Kersten
building blocks The Risks and Rewards of Adopting a Microservices Architecture in Your DevOps Enterprise

Adopting microservices can be a great way to split up existing monolithic legacy applications in order to gain some flexibility and accelerate the development of new features. But the learning curve is steep, and you may need to make some sacrifices. Andrew Phillips outlines the potential impact this implementation can have on architecture and operations in an enterprise environment.

Andrew Phillips's picture Andrew Phillips
two arrows merging 5 Steps to Successful Process Management in Mergers and Acquisitions

When going through a merger or acquisition, capturing the critical processes of both parties is a key to success. Including everyone in the planning helps ease the impacts of change and develop ideas for the future. Here are five steps to assist with process management and create a new organization that is greater than the sum of its parts.

Ivan Seselj's picture Ivan Seselj
planning diagram Software Project Planning and Processes: 5 Steps to Success

Too often, software teams come up with a lofty goal for a project, then immediately launch into development in an effort to get to market faster. But skipping the planning process for how to actually achieve your goal can be dangerous. John Basso gives five steps to drive front-end planning and set your project up for success.

John Basso's picture John Basso
person removing a piece of the pie 6 Traits to Seek in an Outsourced Product Development Partner

Lower costs, specialized designers, and rare skills sets are among the reasons companies consider working with outsourced product developers. But there are differences between working with these vendors versus the traditional enterprise software solution vendors you may be used to. Here are six qualities to look for when making your selection.

Kaushal Amin's picture Kaushal Amin
silo falling down How to Break Down Silos to Build the Perfect DevOps Team

A degree of specialization is essential in every company, but it can lead to dangerous divisions and an outdated structure. Breaking down your silos initiates the cultural change that’s required to build an effective DevOps team and fully realize the potential benefits of everyone’s talents.

Andrew Phillips's picture Andrew Phillips
gap between two teams Business and Development: Working Together to Build Better Products

Business stakeholders and DevOps teams both have to take an active approach to app development, but neither faction should have to change practices and processes in order to get their needs across. Investing the time to establish communication between these teams will drive delivery of the applications customers demand.

Renato Quedas's picture Renato Quedas
Upgrade 5 Tips for Modernizing a Legacy Platform

There are many reasons to consider modernizing your legacy software. But when doing so, it’s important to remember your customers who regularly use your product and to take their preferences, habits, and needs into consideration. Here are some practical tips to boost your chances of a smoother transition.

Kaushal Amin's picture Kaushal Amin
connected hands Building Effective, Cross-Functional Integrated Product Teams

Product development team members are often focused on the component level, but understanding the whole system is a challenge. Forming cross-disciplinary integrated product teams can provide support for large and small efforts in either agile or traditional development, helping teams achieve total system lifecycle expertise.

Susan Land's picture Susan Land
Examining code The Risks of Measuring Technical Debt

If your organization measures technical debt, have you really considered why you're doing this, and what you will do with that information once it has been gathered? Just because you can measure technical debt doesn't mean you should. Before you start (or continue) measuring technical debt, it's important to recognize that there are consequences.

Wayne Ariola's picture Wayne Ariola Cynthia Dunlop

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.