Even with pages of documentation, there still can be miscommunication and misguided assumptions about a product. A prototype serves as the vision for the product and helps everyone, from a salesperson to an engineer, understand what they are trying to achieve. This article looks at some of the benefits of prototyping early in the development process.
Whether they're on the business side or the IT side, professionals in the software industry tend to agree that more communication about project expectations is needed. So why is it that when the two sides collaborate, bad things seem to happen? Ryan McClish and Kenton Bohn analyze the human dynamics and show how to build a solution that accomplishes the defined goals.
Continuous delivery meshes well with agile development: Both facilitate the need to move quicker and deal with ever-changing requirements, delivering the best quality possible but usually with not enough resources. Agility is what is expected from technology companies and IT divisions. So, what does it take to have continuous delivery in your database?
In short, redistributed testing is a shift in the emphasis and responsibility for testing. Testers are reassigned to work closer to the business with users or business analysts or are embedded in the development team.By being involved in story and scenario writing, the testers help to refine requirements and improve their quality. How could your systems benefit from redistributed testing?
A software tester can begin testing early—very early—before the software has even been built. Karen Johnson explains that one of the best times to start testing a product is in the product-discovery phase.
Big data isn’t just a buzzword; it lives in your software. With millions of possibilities to leverage analytics, how do you pick what’s right for your organization? Robert Cross provides some insight into how to start incorporating data analytics into your software process and management plan.
One common complaint about test automation is that it’s too brittle. Small changes in the system can cause lots of rework during the automated checks. In this article, Clint Hoagland shows a way to fix “the brittleness problem” by using the right abstractions in your automation design.
Kristin Cowhey explains how z/OS development has evolved throughout the years and what that means for developers and tech personnel. With legacy developers leaving the workforce, there’s a dire need to replace the knowledge in order to maintain the mainframe systems and applications that are still in use today.
Bob Aiello explains that software engineers and architects do an amazing job designing a system’s architecture that fully represents all of the parts of the system that are created during the development lifecycle. However, one of the biggest challenges is understanding how each part of the system depends upon the others.
Enterprise development organizations are increasingly embracing agile as a concept, if not entirely in practice. That’s because adopting and scaling agile methodologies for large, complex enterprise software projects can seem daunting. Larry Ayres shares some tips for scaling agile development for enterprise software.