agile | TechWell

agile

Requirements document The Curse of Rushed Requirements

When development is outsourced, a documented baseline of expected functionality sets expectations for both the client and developer. Acknowledging that agile practices are flexible, beware the trap of rushing requirements just because you know they are going to change. It's still essential to be as accurate as you can.

Payson Hall's picture
Payson Hall
Framework A Framework for Scaling Continuous Testing across an Enterprise

Scaling agile and DevOps across a large enterprise is much more difficult than practicing it in smaller groups. Frameworks can help, but focus tends to be placed on development, so testing teams struggle to figure out how to best support faster development cycles. The ACT Framework puts the focus on continuous testing.

Mark Trinh's picture
Mark Trinh
Person holding a sparkler with New Year's fireworks in the background Top 10 TechWell Insights Stories of 2019

Career development was on many software practitioners' minds in 2019, as some of our top stories were about having a technical lead on a Scrum team and making the switch from quality assurance to quality engineering. Stories about new ideas such as DevOps and continuous testing also ranked high. Check out the roundup.

Beth Romanik's picture
Beth Romanik
Agile team member expressing intention Don’t Ask for Permission or Forgiveness—Use an Agile Alternative

Some teams get around bottlenecks by taking a “better to ask forgiveness than permission” approach. This may be expedient, but it doesn’t provide a path to changing the organizational dynamic, and it can lead to wrong decisions when wider input is advisable. A more agile way is to take an “I intend to” approach.

Steve Berczuk's picture
Steve Berczuk
Santa Claus talking to a child If Santa Can Be Agile, So Can You

To improve his toy development lifecycle, Santa Claus had the North Pole move to an agile and DevOps approach. Santa knows it's important to accept requirements late in the process, work incrementally, deploy on time, and—above all—focus on the customer. Here’s what he found to be more effective with agile and DevOps.

Jeffery Payne's picture
Jeffery Payne
Scrum team high-fiving after their daily standup 4 Tips to Refocus Stale Standups

The daily standup is supposed to get everyone on the same page and make teams more productive and efficient. But it’s easy for this short meeting to become stale and stop providing any real benefit. Here are four ways to get out of the slump of merely delivering status updates and re-energize your daily standups.

Cristy Bird's picture
Cristy Bird
Team member pointing a finger to blame someone Is Your Culture about Responsibility or Blame?

When things go wrong, it can be helpful to understand what happened and who was involved. However, all too often organizations (and the managers within) confuse responsibility with assigning blame. The former is essential for improvement. The latter works against an effective, collaborative, productive culture.

Steve Berczuk's picture
Steve Berczuk
Neon sign saying "People fail forward to success" Lessons Learned from Product Failures

Being agile is all about learning from failures and building on experiences. This applies to not just individuals, but even to large organizations. The key is being transparent and objective in accepting and understanding failures, and taking away lessons for future actions and decisions. Just keep innovating.

Bharathan Venkateswaran's picture
Bharathan Venka...