Articles

Please enter an article title, author, or keyword
Release management Why DevOps Still Needs Release Management

Release management is still critical in a DevOps environment. You likely will just have to change your current process. You will no longer need to track implementation or back-out plans as part of change orders; you just need to be able to track the application, its components, and its promotion schedule. The key to maintaining these change orders is automation.

Adam Auerbach's picture Adam Auerbach
Icon of agile process Using Sprints for Agile Coaching

Discussing the work to be done as a group, building in short iterations, getting feedback, and looking for ways to improve are not just practices for development teams—it is an effective way to achieve any goal. Here, Ben Kopel details his experience of working with other agile coaches in a sprint to hire a new ScrumMaster.

Ben Kopel's picture Ben Kopel
Agile task board Using Agile to Lead Your Agile Transformation

There's something ironic about starting an agile transformation by spending six months creating a detailed transformation plan. We have to move away from a prescriptive playbook and toward a more responsive transformation model. Why not use the agile transformation as your first opportunity to be agile?

Joel Bancroft-Connors's picture Joel Bancroft-Connors
Speedometer 8 Keys to Transforming into a High-Performance Agile Team

Following an agile process alone will not guarantee your teams will be high performers. Teams undergo various challenges while transforming into a highly productive team. This article looks at the areas where teams generally struggle in adopting agile principles and the typical root causes for those struggles, as well as eight behaviors that can help drive teams toward greater success.

Uday Varma's picture Uday Varma
4 steps in a QA process 4 Strategies for a Structured QA Process

Being a software tester is no longer just about finding bugs. It is about continuous improvement, defining a clear test strategy, and going that extra mile to improve quality. Following a consistent, structured approach to QA will help you acquire more knowledge about the product you are testing, ask questions you otherwise may not have thought of, and become a true owner of quality.

Praveena Ramakrishnan's picture Praveena Ramakrishnan
Lines of code Project Teams Need to Overcome Their Fear of Coding

Many organizations appear to suffer anxiety at the thought of programming. They want to get everyone but the programmers in a room to discuss a project down to the minute and the dollar, without a full understanding of the coding required. But a few hours of code experimentation generates far more understanding than days of debate by architects and analysts. Don't be scared of programming.

Allan Kelly's picture Allan Kelly
Ford Model T car Henry Ford: Master of Lean Agile Processes

Henry Ford, founder of the Ford Motor Company, was a captain of industry who revolutionized production. He also was one of the greatest influencers of the processes we call lean and kanban today. John Yorke believes Ford's ideas about process improvement made him a pioneer for systems thinking and agile software development.

John Yorke's picture John Yorke
The Space Shuttle Challenger launch Prevent Disaster by Righting Cultural Dysfunction on Your Team

The space shuttles Challenger and Columbia were two of NASA's biggest disasters. Investigations into these accidents discovered the engineering issues responsible, but management practices and cultural barriers also were found to be contributing factors. Does your organization have a healthy culture that lets you safely voice concerns? It could help you prevent tragedy.

Payson Hall's picture Payson Hall
Hands put in the center of the group For Agile to Succeed, Put People First

There’s a lot of buzz in the agile world today about becoming more technical, automating everything, and learning the next miracle tool. While it’s important to establish a process, and tools can help with many steps of the software development lifecycle, the human contribution to project delivery is still the most important. Here are some qualities agile teams should encourage.

Leanne Howard's picture Leanne Howard
Icon showing one end to another Endgame Testing: Exploring Your Agile Product End to End

The main goal of endgame testing is to test the system end to end from the user's perspective. This should ensure continuity between components developed by different teams, continuity in user experience, and successful integration of new features. Endgame testing will often identify gaps that are difficult to discover inside agile teams, including flows across the product.

Doron Bar's picture Doron Bar

Pages

Upcoming Events

Nov 28
Dec 04
Jun 25
Sep 30