process improvement | TechWell

process improvement

Note with "Now" checked instead of "Later" The Key to Avoiding Procrastination

If you have a task you've been putting off, dividing it into small chunks is a good idea. But the real key to overcoming procrastination is just getting started. Once you begin, you’ve built momentum and are likely to keep going, doing a little more until you’ve made good progress—and maybe even completed the job.

Naomi Karten's picture
Naomi Karten
A group of people fist-bumping How Testers Can Collaborate with the ScrumMaster

ScrumMasters serve the team by providing facilitation and coaching, but they also have many challenges. Those in testing roles are in a good position to collaborate with the ScrumMaster to improve agile processes. Here are some ways testers can partner with, support, and assist the ScrumMaster—and the rest of the team.

Michael Sowers's picture
Michael Sowers
Agile and DevOps Venn diagram The Relationship between Agile and DevOps

Many are touting DevOps as something new and different—just like agile before it. DevOps fixes an age-old conflict between software development and operational teams, but it’s not new. In fact, the DevOps philosophy is ingrained within the Agile Manifesto. So why is DevOps viewed as something different from agile?

Jeffery Payne's picture
Jeffery Payne
Tools Balancing Process and Tools

The limits of a tool may lead us to realize that we are not working as effectively as we can, and often, changing a tool is part of the solution. But there are good and bad ways to select a tool and how you use it. In particular there are risks when you focus first on tools before considering the problem.

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
Better Software Fall 2017 issue cover What’s in the Fall 2017 Issue of Better Software Magazine

Better Software magazine editor Ken Whitaker highlights content from the latest issue, including articles on bridging the divide between agile and waterfall, scaling agile through empowered teams, DevOps and IoT, and continuous development.

Ken Whitaker's picture
Ken Whitaker
User stories Use Continuous Backlog Grooming to Refine Agile Requirements

Continuous backlog grooming means systematically refining your user stories: breaking up larger stories, obtaining detailed requirements, writing the requirements in terms of acceptance criteria and acceptance tests, and sharing and refining these details with the team. Acceptance test-driven development can help.

Susan Brockley's picture
Susan Brockley