Agile Development Methods
Agile Development Methods
|
3 Common Collaboration Problems for Teams Transitioning to AgileA shift toward working in smaller teams on tighter releases forces organizations adopting agile to rethink what successful delivery looks like. It can be a big change for those used to silos. Here are three key symptoms of agile teams that don’t have close collaboration—and some solutions you can implement to fix them. | 
|
|
3 Reasons Exploratory Testing Is Great for Agile TeamsSpecification-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. | 
|
|
Finding a Home for Specialists on Cross-Functional Agile TeamsIt 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. | 
|
|
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. |
|
|
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. |
|
|
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. |
|
|
Transparency Could Transform Your CompanyTransparency 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? |
|
|
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. |
|