Related Content
Designing an Office to Nurture Innovative Agile Development Teams Agile software development is a collaborative activity in many ways, but it also requires quiet time. While open office spaces foster communication and collaboration, it's still important for a workspace to have areas where people can buckle down and work. What is the best office configuration to nurture innovation? |
||
To Improve Agile Teamwork, Think about the Individuals Given the emphasis on teams, it can be easy to forget that agile has the value of individuals and interactions as a central principle. As much as an effective team dynamic is what makes Scrum work, teams are composed of individual people, and it’s important to acknowledge each person's role and to express appreciation. |
||
The Balance between Being Stealth and Being Public during Product Development While end user data protection is important from a business to customer perspective, businesses themselves have their share of data protection problems. Organizations need to find the balance between being in a stealth mode and being too public during product development. |
||
Develop Stronger Client Relationships through Empathetic Action There’s a big difference between simply saying "I feel your pain" and displaying evidence of empathy. When dealing with clients' complaints and issues, do more than try to understand what they're going through. Aim to communicate early, often, and with sincere concern. It will improve the situation for them—and you. |
||
Agile Testing Shouldn’t Change Based on Team Size It’s important to note the more collaborative nature that agile encourages for every single member of the team—not just the testers. Sure, testers might have to adopt the most new skills if they hope to make things work at this new pace, but product owners and developers can’t just rest on their laurels. |
||
How to Make Agile Work for Your Specific Team Taking a step back, being honest about your strengths and weaknesses, and then using agile concepts to make yourself better is smarter than simply copying another team's structure. Agile can be your base, but don’t let trends that work for your competitor dictate the core of your software development. |
||
Catch Small Failures Early with Agile Practices Agile is designed to keep failures small and manageable. It’s essential to be able to talk about small failures and ways to improve during the retrospective so that the teams can advance their agile practices. If your teams can’t talk about their small failures openly, there is a great risk of bigger troubles soon. |
||
Don’t Let Too Little Planning Tank Your Agile Adoption Many organizations turning to agile believe it means you don't have to do any planning. This couldn't be further from the truth. A healthy agile team does just as much (if not more) planning than a team using a waterfall methodology. Preparing and setting goals sets up the team for a more successful agile adoption. |