Development Agile Test & Quality Assurance Project Management Requirements
CM & ALM Devops Cloud Mobile People & Teams

By Topic

Agile Development Methods

Agile Development Stories
Exploratory testing 3 Reasons Exploratory Testing Is Great for Agile Teams

Specification-based testing is critical for determining whether a user story is “done done.” But that doesn’t ensure a positive user experience. Coherence, comprehension, and usability are beyond the scope of automated functional testing. Here are three reasons agile teams should embrace exploratory testing.

Ingo Philipp's picture
Ingo Philipp
Specialist Finding a Home for Specialists on Cross-Functional Agile Teams

It may seem like the best team would be composed of all specialists, but due to their proficiency in only one area, they can actually hold up an agile workflow. You can keep specialists on your cross-functional teams; you just need to structure their work. Here are four options for making good use of a specialist.

Steve Berczuk's picture
Steve Berczuk
Agile culture Creating Your Organization’s Agile Culture

Some organizations decide they can just “install” agile by simply telling the technical team members what to do. It never occurred to the managers that much of what makes agile successful is the organizational culture. It's important to recognize that agile is something you work toward—with the whole team.

Johanna Rothman's picture
Johanna Rothman
figures standing around globe Why You Need to Unify Agile Methodologies among Teams

Agile software development is a complex initiative to undertake, especially when a dispersed team is involved. Organizations must establish a unified agile methodology to ensure that everyone is on the same page and understands what is expected of them in these efforts.

Sanjay Zalavadia's picture
Sanjay Zalavadia
man jumping over hole in bridge How Agile Bridges the Major Gaps between Development and Testing

Agile, by its very nature, is about collaboration. The developers work alongside the testers, the testers see eye-to-eye (at least in most cases) with the developers, and there’s just a more flexible nature to the team itself. It is meant to bridge the major gaps within teams.

Josiah Renaudin's picture
Josiah Renaudin
Transparency Transparency Could Transform Your Company

Transparency is a core Scrum value because it ensures everyone involved on a project has a common understanding of goals, progress, and deliverables. But what about extending transparency to the whole company, sharing revenue and client-related numbers, strategic product plans, and even individual salaries?

Steve Berczuk's picture
Steve Berczuk
Delivering Successful Software Requires You to Fail Faster

The concept of failing has changed from something people dread to a necessary part of creating secure, functioning applications. That means that you don’t want to have one major failure at the very end of the development lifecycle—you need to continue to fail before release to find real success.

Josiah Renaudin's picture
Josiah Renaudin
big fish in small bowl Agile Transformations Are All about Being Uncomfortable

If you’re hoping to become agile, you have to get uncomfortable before you break through and find your stride. Agile is all about growth, and in order to grow, you have to adopt new concepts, practices, and techniques that will force you to change what you’re doing in a way that might not come easy.

Josiah Renaudin's picture
Josiah Renaudin