agile
|
5 Key Factors to Achieve Agile Testing in DevOps Part of the path to DevOps requires adoption of agile methodologies. What does it mean for testing when you switch from the traditional waterfall model, with a few long release cycles per year, to the agile model, with changes occurring every two weeks? Here are five key factors to achieve the agile software testing necessary in DevOps.
|
|
|
Picking the Right Branch-Merge Strategy A good branch-merge strategy facilitates processes among multiple developers and is the basis for any well-functioning DevOps pipeline that uses continuous integration. Let’s explore branching strategies, merging strategies, and how you can put them together in a way that’s right for your team in order to bring quality features to production faster.
|
|
|
Why You Need Continuous Testing in DevOps DevOps is more than adopting the right set of tools; it's a cultural shift that incorporates testing at each stage of the agile project lifecycle. Continuous testing is key to unlocking this culture change because it weaves testing activities into every part of the software design, development, and deployment processes, which helps everyone involved communicate more, collaborate better, and innovate faster.
|
|
|
When DevOps Gets Lost in Translation The waterfall method of developing software is a bunch of translation activities: The design is a translation of the requirements into the language of architecture, the code is another, and a formal test process is a third. And with each translation, there’s the opportunity to introduce error. When your DevOps team is isolated, it creates another handoff, and another point of failure.
|
|
|
Using Agile and DevOps to Achieve Quality by Design When software nears completion, it is the wrong time to focus on quality. Product delivery improves if you invest in a plan, validate in small increments, and focus on continuous testing.
|
|
|
Great Big Agile: An OS for Agile Leaders Following agile ceremonies may make an organization feel good, but that’s only a start. “Great big agile” requires leadership at all levels to focus on self-organization and empowerment as a universal framework.
|
|
|
Scrum: Back to Basics So you think you know Scrum? Using the whimsical notion of farm animals and light-hearted visuals, take a refreshing review of the entire Scrum lifecycle as an intuitive set of roles, responsibilities, and handoffs. Particular attention is placed on what the ScrumMaster and product owner are expected to do at each handoff.
|
|
|
DevOps and the Culture of Code Migrating an organization to continuous integration requires adoption new processes, tools, and automation. DevOps relies on dramatic culture change to encourage total transparency and collaboration among all project stakeholders.
|
|
|
Getting Restarted in Test Automation: A Conversation with Chris Loder
Video
Chris Loder, automation architect at InGenius, talks about being a self-taught automation developer, why learning new skills is so important, and the synergy between manual testers, automation testers, and developers.
|
|
|
Finding Microefficiencies in Agile Practices: An Interview with Melissa Tondi Melissa Tondi discusses retuning your standard agile practices to better engage the project team, enabling them to write code that will pass testing and free testers to assume the role of user advocate.
|
|
|
Why You Need to Take Security and DevOps Seriously: An Interview with Jeff Payne
Video
In this interview, Jeff Payne, the CEO and cofounder of Coveros, explains why major companies just aren’t that good at security. He discusses how you can better protect your business, as well as why DevOps can and should be a key to your success.
|
|
|
Why Bug Reporting Is More Important than Ever Before: An Interview with Sam Kaufman In this interview, Sam Kaufman, the founder and CTO of BugReplay, explains why most teams don’t put enough emphasis on bug reporting—even though agile and DevOps have made it even more important than before. He also details where DevOps can improve and where he sees it in five years.
|
|
|
Delivering the Goods: Harmonizing Regulated and Agile Practices
Slideshow
Agile testing is hard. Testers contend with terse requirements, minimal process, little documentation, continually evolving business, technical and organizational factors. Auditors demand proof of compliance. Some teams have trouble conforming to regulations while preserving agile practises..
|
Griffin Jones
|
|
Troubleshooting and Understanding Modern Systems: Tools Testers Need
Slideshow
Successful agile testers collaborate with programmers as code is written, isolating problems, troubleshooting defects, and debugging code all along the way to getting the product to done. But modern systems are scaling beyond what traditional teams are able to understand using familiar tools.
|
Chris Blain
|
|
Test Management in Agile—What Happened to All My Testers?
Slideshow
Substantial confusion exists about the roles and responsibilities of test management when using an agile software development process. Agile seeks to streamline project management and leadership under the role of a ScrumMaster, but what does this mean for test managers? How do they stay...
|
Jeffery Payne
|
|
Telling a Better Story: Finding Quality in the Agile User Story
Slideshow
When delivering agile software development projects and conducting quality assurance and testing assessments, it often seems that “solving the testing problem” doesn’t solve “the quality problem.” The testing problem is much broader than just code quality, testing tools, automation...
|
Stephan Marceau
|
Visit Our Other Communities
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.