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.
Testers who analyze quality in every aspect of the team’s deliverables also have a responsibility to mitigate risks and practical issues that are bound to come up, and help the team succeed in their product as well as at being agile. Here are five such issues that testers can help the team alleviate or avoid.
Agile and DevOps teams, which emphasize continuous improvement, can benefit greatly from effective retrospectives. However, retrospectives can get monotonous, and that’s when they become ineffective. Using gamification in your retrospectives brings a completely different dimension of thinking—and even makes the process fun.
In this article, a developer shares his personal experience with the transition from a waterfall environment to an agile one. He compares what it was like for him coding, learning, and communicating using each methodology, and he shares what it was like making the change to agile—and why he's never looking back.
Web APIs have opened up a brave new world for app collaboration. James Higginbotham presents a series of guidelines that every programmer should consider in the design and implementation of a great API developer experience.
DevOps can be characterized as the assembly line of building, testing, deploying, and updating enterprise applications. Many software development organizations may claim a comprehensive DevOps strategy, but Chris Riley believes that the only way to be successful is to use a DevOps framework.
Eric Winquist has considerable experience not only leading his company but also consulting with development teams. His advice to “link people to the work” is one of many golden nuggets of information that will help your team deliver projects on time.
Cloud-based software development definitely changes how project managers need to approach their projects and lead their teams. Cloud development is not the same as traditional software product development and requires a unique mix of traditional project management and agility. Project managers considering working on cloud-based projects need to read what Sridhar Kethandapatti has to say.
In this interview, TechWell speaks with Andreas Grabner, a performance engineer who has been working in this field for the past fifteen years. At STARWEST 2015, he presented DevOps: Find Solutions, Not More Defects.
In this interview, Matt Heusser covers how most organizations test now, presents ways you can improve your company's approach to lean, and demonstrates lean tools that can help you understand software development and test flow in a different way.
In this interview, Rob Sabourin talks about his STAREAST presentations. These cover how to elicit effective usability requirements with storyboarding and task analysis, and how to blend the requirements, design, and test cycles into a tight feedback loop.
In this interview, Richard Hundhausen talks about real-world software testing, his experience at STAR<emeast, the benefits of Scrum and agile, and how we can end the developer/tester dichotomy by bringing these two teams together.
Software processes are commonly portrayed using machine metaphors in which consistency is highly prized. Frequently, organizations set up Centers of Excellence in a well-intentioned effort to create enterprise consistency. Steve Adolph reminds us that, in reality, software development...
After providing an introduction to several key agile testing concepts—including the Automation Triangle and the Test Automation Quadrants—Geoff Meyer discusses approaches to effectively deliver automated testing. Geoff shares practical insights and demonstrates how they were employed...
Is architecture the same as preliminary design in agile? It shouldn't be. Do we do architecture up front, then do iterative development after the architecture is done? That is edging back toward waterfall. Can you explain the purpose of the architecture in just two or three statements?
We teach managers to foster agility by encouraging their teams to self-organize, stop assigning work, and telling them how to do it. Since the Product Owner defines the what and the team defines the how, what’s left for managers to do? Managers need to become servant leaders. It’s a key...
David Grabel, Grabel Consulting Services, LLC, and Shyam Kumar, UST-Global