Tag: Agile

Use Software Measurement Best Practices to Support Your Agile Initiatives.
How Software Intelligence Can Save Your Agile Program
An Analysis of the University of Zurich’s Published Research on Refactoring Practices.
Refactoring: How do DevOps and Agile Processes Affect Software Quality?
Why it’s DevOps then Agile, not Agile on its own.
Is the Agile Bubble Bursting? I Hope Not.
As DevOps and Agile Mature, Are They Helping Developers Achieve Quality Objectives?
Do DevOps and Agile Improve Software Quality?
An Analysis of Gartner’s Note “Ensuring Quality From External Agile Software Developers”
2 Tips to Ensure External Agile Teams Deliver Software Quality
A look at how the College Board set 7 ‘North Stars’ to rapidly transform monolithic applications.
To Modernize Legacy Systems, Cloud Offers an Optimal Path
Follow these three fundamental steps to go from “cloud as a concept” to “cloud ready.”
Going Clear: Seeing Through the Hazy Road to Cloud Adoption
To compete in a fast-paced digital world, CIOs need the best information about software health to make smart decisions.
CIO Perspective: Using Software Intelligence to Make Better Modernization Decisions
Strategies to fix technical debt is a topic that’s not going unnoticed this year.
Technical Debt for Continuous Innovation: Strategies to Avoid
Overcoming organizational hurdles to adopt an Agile culture can be tough, but the pay-off is huge.
How Fannie Mae Uses Software Intelligence: Six Steps to Successful DevOps
Technical debt is a huge problem for many organizations today and if it’s not being addressed, it’s growing. Growing technical debt takes away from funds for innovation, and instead uses it toward maintenance.
Technical Debt: 3 Biggest Organizational Mistakes
Technical Debt standards have been debated for many years.  And now CISQ (Consortium for IT Software Quality) has released standard that not only measures by automates technical debt calculation in complex software systems.
Technical Debt: CISQ Releases New Standard to Define and Measure Technical Debt
Technical debt and DevOps are two topics on every organizations mind.  Yet, no one tackles the topic better than this article
Technical Debt & DevOps: 5 factors fueling automation in IT
Everyone wants to do DevOps like Netflix, but is it really right for your organization?
Netflix Envy

Last week, CAST attended the Gartner EA Summit, held at National Harbor. It was two days of jam-packed sessions and workshops about Enterprise Architecture, but what stuck out the most was the value of this very unique discipline as a catalyst for Digital Transformation.

EA and Digital Transformation were the core focus of many presentations, including Mike J. Walker’s session “Leverage EA to Understand the Value and Impacts of Digital Disruption.” Mike stressed that this ever-evolving discipline is becoming a vital component to corporate strategy, delivering high-performing and sustainable business outcomes.

Enterprise Architecture as the Gateway to Digital Transformation – Takeaways from the Gartner EA Summit 2016

IT leaders from throughout the federal government discussed the value of how software measurement can positively impact their development process at CAST’s recent Cyber Risk Measurement Workshop in Arlington, VA – just outside of the Washington, D.C. area. The event brought together more than 40 IT leaders from several governmental agencies, including the Department of Defense and Department of State, system integrators and other related organizations. The group shared their experiences in how their respective organizations are driving value to end users and taxpayers.

IT Leaders Address the Value of Software Measurement & Government Mandates Impacting Development

Application portfolio analysis was at the center of discussion as Forrester Research Vice President and Principal Analyst, Margo Visitacion, presented how Agile development is affecting the application development process and IT’s portfolio planning. Ms. Visitacion explained that in the “Age of the customer,” they want more for less and expect companies to fluidly change based on their needs and demands. As companies shift their attention to customers’ experiences rather than production figures, it’s leading directly to higher revenue and a longer-lasting relationships.

Key Discussion Points from Forrester Webinar: Agile Portfolio Management Requires Rapid Transparency

In the current tech scene, it has become common practice to refer to programmers as engineers. It seems that if you aren't part of sales or marketing teams you are now entitled to being designated as an engineer. However, what has been forgotten over the 50 years of looking to turn software development into a legitimate engineering practice, is that we still haven't reached the aspiration of being just that: a legitimate engineering practice. Traditional engineers have to go through stringent regulation, certification, and apprenticeships in order to gain the title. This creates an implicit responsibility of providing reliability and public safety. Software development hasn't reached this point yet - software quality and standards are not universally valued.

So why is the tech industry using the engineering title to describe its technical workers?

Faltering Software Quality and Standards: Why Programmers Should Stop Calling Themselves Engineers

The purpose of this white paper is to portray the worldwide state of agile adoption for our readers. While much has been written about the strengths and weaknesses of the technology, little data has been published to show how widely agile methods are used. This paper corrects that by providing data from our databases for public consumption. As shown in Figure 1, agile methods have become the dominant software development paradigm used throughout the world based on data from 330 organizations. Some of these organizations are offshoots of the 120 firms and government organizations from which we have received data. Figure 2 summarizes which agile methodologies are in use by these organizations. As many said that they were using a hybrid approach, i.e., one that combined agile with traditional concepts, we have included their response and categorized them as either hybrid or hybrid/lean (agile combined with lean).

Agile Introduction: Are You a Laggard?