The rapid rate of technological change is forcing enterprises to reinvent themselves and provide more flexible approaches, so agile transformations are key. However, knowing that agile is important is one thing, but the ability to properly implement the main principles, tools, and techniques of agile is another. Let’s explore time-tested agile principles that will help your organization build innovative products that customers love.
The recent surge in virtual meetings necessitates an entirely new set of desirable behaviors. But how do you keep participants engaged and material useful and on topic remotely, when it's hard enough to do that with everyone in the same room? The key is keeping value delivery front and center. Here are some tips and best practices for virtual meetings that will help you continue to deliver value.
Nearshore software development—or working with teams in similar time zones—have different challenges from teams that are collocated. They might find it easier to work in a traditional, hierarchical structure, but agile practices are actually still an ideal way to work through these challenges. Here's how an agile mindset can help nearshore development teams improve communication, organization, and processes.
An organization shouldn’t spend all its time building its delivery muscle without simultaneously building its discovery muscle. In fact, successful software teams deliver great products because they invest in discovery. Learn how to expand your innovation and strengthen your discovery muscle.
Rather than rely on large handoffs between specialties, high-performing Scrum teams learn to do a little bit of everything all the time during a sprint. To do this effectively, teams must make three changes: shift from writing about requirements to talking about them, reduce the size of handoffs and make them more frequently, and pay more attention to the size of the product backlog items that they bring into their sprints.
Many new products being developed require the contribution of artists and other such "creatives," but artists often view the creative process as an organic thing that cannot be analyzed, dissected, or reduced to a set of defined practices without killing it. This article explores barriers such as these to the introduction of agile methods and how these barriers can be overcome.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
Marcia Buzzella, an independent leadership consultant and strengths coach, discusses the importance of communication and social skills in a business atmosphere. She offers advice on tools to recognize your weaknesses in those areas and how to work toward improving your effectiveness.
In this interview, Selena Delesie, an international leadership and transformation coach and trainer, explains how your team can find the soul of agile, why some agile teams lack creativity, and who on your team should become a leader.
In this interview, Jessie Shternshus, the owner and founder of The Improv Effect, explains the similarities between agile development and improvisation. She details how, in both cases, team members need to learn how to support each other, build on work, and be comfortable with failure.
The problem with many agile teams is that they simply never become a team. This often manifests itself as team members feeling unsafe or not quite trusting each other. This workshop will show you how the same techniques improv theater troupes use to improve collaboration, creativity, and communication can be used to help agile teams, too. The three-minute improv warm-up games Wayde Stallmann will lead you through in this session—including improv's famous "yes, and" technique—will help you learn to establish trust, improve collaboration, and learn how to provide a safe environment for your team to bond. You also will get a flier explaining the top twenty improv games, allowing you to leave with actionable material to use immediately upon returning to work so that you can help your team reach its full potential.
The key to creating high-performing teams is psychological safety—the ability to be vulnerable in front of others even when they hold diverse viewpoints, and the opportunity to take risks and trust that everything will be OK. However, creating this safety is easier said than done. Maaret Pyhäjärvi shares her story of working with software development and test teams to enable them to be awesome. She explains how to reinforce the positive while enabling great software product development by empowering others in your team. Maaret explores how to be brave when others are not, and how to care for and build safety for others. She describes being a catalyst for your team, emphasizing learning—always with safety as a prerequisite. Today, Maaret uses her position as a tester not only to test every part of the software but also to build the collaboration habits of the team, delivering actionable information to improve product quality.
Are you looking for new ways to invigorate your teams? Do retrospectives seem stale? Do story breakdown meetings feel flat? On the other hand, maybe your teams are humming and you’re looking for additional variety. The research is clear—movement matters, and play stimulates creativity.
Many organizations want to create systems delivered in a DevOps framework with diverse services implemented via API building blocks. Chris Haddad says that people, processes, and tools often hinder a team's ability to comply with security policies, streamline collaboration, and rapidly...