agile | TechWell

agile

man at computer Why the Gig Economy Thrives in the World of DevOps

Even if the industry is booming, it’s not easy filling the full-time DevOps roles. Every software team is vying to find the perfect person to come in and establish a culture to promote improved software release cycles, software quality, security, and rapid feedback on product development. But it's not easy.

Josiah Renaudin's picture
Josiah Renaudin
Arrows pointing to old way and new way An Agile Approach to Change Management

Many organizations are reluctant to introduce new tools or technologies, or even to update existing ones. The reason is often framed in terms of risk management, but agile teams already have the tools to manage the risk of change: testing and experiments. These approaches together eliminate gaps in risk identification.

Steve Berczuk's picture
Steve Berczuk
Agile project 5 Tips for Choosing Your First Agile Project

When transitioning to agile, applying agile methods to a single project is a great way to get started. However, care must be taken to ensure the project you choose is appropriate—it shouldn't be too large, take too long, or be too risky. Here are five tips to help you pick the right project for your agile pilot.

Jeffery Payne's picture
Jeffery Payne
Continuous improvement Driving Continuous Improvement to the Entire Organization

In traditional agile approaches, retrospectives are valuable to team improvement. However, when teams encounter organizational issues beyond their control, such as project structure, interorganizational communication, or resources, it's more difficult. Here's how to expand continuous improvement to the whole company.

Alan Crouch's picture
Alan Crouch
Agile development code Integrating Code in Agile Software Development: Start with the Goal in Mind

Agile software development works because of continuous feedback at various levels, and the most important form of feedback is working software. One way to achieve rapid feedback is to integrate and deploy code frequently. Rather than starting with the process, first decide what "frequently" should mean for your team.

Steve Berczuk's picture
Steve Berczuk
Puzzle piece The Role of Testers on Agile Teams

Some agile teams have so fully embraced the idea of the development team owning quality that they don't hire anyone with a testing background, instead making software engineers responsible for all phases of quality. Still, testers add value to a team in many ways that don’t involve test execution. Where do they fit in?

Steve Berczuk's picture
Steve Berczuk
Hands breaking free of restraints Breaking the Cycle of Bad Scrum

When practiced well, Scrum can empower people, teams, and organizations to solve complex problems and deliver value to their customers. But bad Scrum does the opposite. If team members or leaders don't embrace Scrum values, it can be oppressive and create tension. Here's how you can prevent bad Scrum from taking hold.

Ryan Ripley's picture
Ryan Ripley
Conveyor belt delivering boxes Why Frequently Delivering Working Software Is Crucial to Agile

While completing documentation is often an indication that some progress has been made, until software has been implemented, tested, and approved by a customer, the amount of progress cannot be measured. Here are some common reasons agile teams fail to frequently deliver working software—and how to avoid them.

Jeffery Payne's picture
Jeffery Payne