Related Content
Why Laughter Is a Sign of Creative, Productive Teams Laughter is a sign that people feel relaxed and safe. In a workplace, safety leads to environments that enable more idea generation and innovation, so one approach to improving teammates' creativity and connection is to encourage laughter. But how can you do that so it doesn't feel forced? Steve Berczuk has some ideas. |
||
5 Ways to Improve Your Project Management As a project manager, it's your job to cut through the noise to make clear objectives for your projects. But it’s not so easy to do, especially when your superiors or board are politely “suggesting” another action item. Help your team stay on track with these five tips to move more efficiently through your projects. |
||
Building a Culture of Continuous Improvement A culture of continuous improvement means you are open to improving how you build and deliver. You don't accept the status quo; you choose how to work and feel empowered to change it if it no longer makes sense. Kevin Goldsmith gives some ideas for frameworks to adopt in order to move toward this people-first culture. |
||
4 Impediments to Nurturing a Feedback-Rich Culture Being able to have open, candid conversations that fuel learning, growth, and improvement is critical to a team’s success, so it is important to look out for impediments that can get in the way of having a feedback-rich culture. Here are four common impediments to watch for, as well as behaviors you should nurture. |
||
The Changing Facets of Integration Testing In the current dynamics of product development and confirming quality in the agile world, the definition (both narrow and broad), significance, and scope of integration testing have increased manifold. Rajini Padmanaban highlights the changing facets of integration testing that teams need to make note of. |
||
Fighting Key-Person Dependency Risk on Your Team Key-person dependency risk is when only one person on your team possesses certain business-critical abilities or knowledge—so if that person leaves, you're in trouble. The first step of mitigating that risk is taking stock of your team members and their skills. Decide what's important, and train or hire accordingly. |
||
Is Your Agile Team Taking Every Opportunity for Communication? Scrum events are well-defined points where team members communicate, but they shouldn't be the only times. If you’re not considering coding, tests, and the delivery process as opportunities for a conversation, you are missing an important chance to leverage individuals and interactions, as the Agile Manifesto states. |
||
Testing Your DevOps Is Just as Important as Testing Your Software Many DevOps engineers fail to test their automation code in the same way they test the software they deploy. It's crucial for software to have tests, and this should apply to infrastructure-as-code software too, if we plan to change and improve this code with no worries about breaking automation in our DevOps pipeline. |