The dream of any product owner is fully customizable production software without the expense of the hardware it rests upon. While not completely free of infrastructure, serverless infrastructure significantly reduces overhead costs by abstracting away physical hosting, physical security, server maintenance, and OS patching. Here's what you need to know to decide if serverless infrastructure is right for you.
Agile software development is mainstream by now, but people are still finding ways to experiment with agile. Measuring agile success with metrics, the debate over whether to use estimates, and improving predictability in Scrum were all hot topics last year. The rise of DevOps has given even more material for people curious to adopt the practice, so automation and "continuous everything" were also popular subjects.
For an organization transitioning to agile development, creating software architecture isn’t incompatible with your new processes. Consider the principles in the Agile Manifesto, involve team members who will be using the architecture in its development, and reflect and adapt often, and you will end up with an architecture that meets the needs of your team and your enterprise.
The #NoEstimates movement isn't really about no estimates. It’s about working in a sufficiently agile way that you don’t need estimates. When you break down your work into smaller chunks, you provide more value by delivering working product than you do by estimating. What would it take for you to work that way?
Many systems architects have a technology—centric view of service-oriented architecture. This article emphasizes the need to understand the business side of SOA before tackling the technology and illustrates this need with a look back in time.
Software engineering has come a long way, but programmers still spend a lot of time on tasks that could be automated. Fortunately, there's model driven architecture with its new generation of modeling tools that go way beyond the average UML. Learn how MDA addresses the challenges of today's highly networked, constantly changing systems environment and provides an architecture that assures portability, platform independence, productivity, and much more.
Connect with an expert to learn how to work smarter and discover new ways to uncover more defects. In this issue, Michael Bolton takes a close look at one of the key skills of Rapid Testing: critical thinking.
The most costly product defects are often a problem of software architecture. Testing your architecture is a crucial, but often overlooked, step in product development. Learn how to create apply a Systems Architecture Review Board for your own architectural review process.
In this interview, Neal Ford, a director and software architect at ThoughtWorks, explains why software architecture has traditionally been so difficult to change later on in the process and how you can adapt your modern architecture to be much more evolvable.
In this interview, Dennis Stevens of LeadingAgile talks about his upcoming presentation on the value of aligning teams, architecture, and governance, along with common pitfalls organizations face when it comes to syncing up their teams.
Kevlin Henney believes that it's time to revisit the thinking behind "Worse is Better," which he does in this interview with Noel Wurst. Kevlin explains that by getting past the catchiness of the phrase, and really digging deep into its real meaning, there's a real sense of agile underneath.
HP's Kelly Emo discusses why test automation is on everyone's minds these days, yet might not always be the answer people are looking for. Kelly shares how test architects and properly built test management can give your team and project the best chances for success.
For many years, software architecture was described as the “parts that are hard to change later.” Modern advances in architecture have shown that if architects build evolvability into the architecture, change becomes easier. Neal Ford describes a family of software architectures that...
Ever since distributed software became popular, developers have been choosing whether to use monolithic architectures or service-oriented architectures. With the advancement of cloud infrastructure and the widespread implementation of agile methodologies, the latter approach has been...
Continuous integration has made development faster and more reliable. However, as codebases expand, organizations are finding that their build pipelines slow down dramatically. One of the most common reasons is that we often rebuild parts of the system that don't need to be rebuilt.
“Can we do agile?” is a question often asked by individuals enviously looking at the impressive results reported by other organizations that adopted agile practices. What they are usually concerned about are the commonly perceived barriers to agile adoption: large scale, legacy...