process improvement | TechWell

process improvement

Agile team member pointing at user stories written on sticky notes What’s the Problem with User Stories?

Agile projects focus on very lightweight, simple requirements embodied in user stories. However, there are some problems with relying solely on user stories. They often don't contain enough accuracy for development, testing, or industry regulations. There's a better way to write detailed requirements that are still agile.

Adam Sandman's picture
Adam Sandman
Candle burning in the dark Testing in the Dark

Requirements only go so far in identifying areas to test. Sometimes testers are given no information at all, leaving it up to them to determine what to test. Don’t accept the need to indiscriminately test with no clear understanding. Your testing should be targeted, and these techniques will help focus your test effort.

Richard Estra's picture
Richard Estra
Group of game pieces with one left behind Leave No Tester Behind

Creating comprehensive automated tests within a sprint can be a challenge. If the testers don't finish the automation and the rest of the team moves on, testers get left behind and can't catch up. You need some techniques to keep everyone together and ensure that all essential work is accomplished—including test automation.

Hans Buwalda's picture
Hans Buwalda
Green plastic army soldier figures Building a DevOps Army

As you scale DevOps, you need more team members who understand the fundamentals. You could bring in external folks, but they're expensive and in short supply, so start building your DevOps army now by training existing employees. Here's what testers, developers, and IT operations professionals each need to know.

Tom Stiehm's picture
Tom Stiehm
Agile team member drawing out a process on a whiteboard Good Process, Bad Process

“Process” is a word that seems to have a lot of baggage. Depending on whom you ask, process is either essential to delivering value, or something that gets in the way. But this is the wrong way to frame the issue. A process is not inherently good or bad; it's how you use it, and whether it's right for your situation.

Steve Berczuk's picture
Steve Berczuk
Agile team in a meeting Does Agile Have Too Many Meetings?

Because agile favors lots of short meetings, it may seem like they take up a lot more time. But when you compare it to time spent meeting in the pre-agile days, it's usually actually less. However, this doesn’t mean all meetings you attend are useful. Here are a few tips for deciding if all your meetings are necessary.

Jeffery Payne's picture
Jeffery Payne
Tester looking at a defect log Defect Reporting: The Next Steps

When a software defect is identified, best practices usually only pertain to the initial writing of the defect, not the tasks required to close it. Many factors can influence the tester's work. The solution is to add a “Next Steps” section that identifies the work remaining and the person responsible for completing it.

Richard Estra's picture
Richard Estra
Cursor about to click the word "Security" Shifting Security Left: The Innovation of DevSecOps

The more established a product is when it is first audited for security, the harder it will be to find the time to fix problems and to refactor the software. DevSecOps was created to get application security practices into the development process as early as possible, so we can use them from the beginning of a project.

Tom Stiehm's picture
Tom Stiehm