Related Content
Are Your Retrospectives Adding Value to Your Scrum Team? Sprint retrospectives are often skipped, compressed, or organized in a way that doesn't provide good feedback. This is unfortunate, as a well-planned retrospective is a great way to improve how you work. Good retrospectives enable engagement and safety, distill and prioritize ideas, and create concrete action items. |
||
Using Agile to Navigate through Medical Device Regulations When you test medical device software, you must be very careful. But when development wants to push a cadence of two weeks per sprint, every sprint, you’ve just got to keep up! Interpret the regulatory requirements not as a set of disabling constraints, but as a challenge to find the optimal route to navigate through. |
||
Lower Risk of Downtime by Testing with Production Traffic Teams need a means of identifying potential bugs and security concerns prior to release—with speed and precision, and without the need to roll back or stage. By simultaneously running live user traffic against the current software version and the proposed upgrade, you can detect bugs while reducing risk and downtime. |
||
The Importance of Data Encryption in Cybersecurity Encryption protects private data with unique codes that scramble the data and make it impossible for intruders to read. Despite a data breach, encryption ensures that an institution’s private data is safe, even when attackers get past the firewall. Here are four reasons to use data encryption cybersecurity measures. |
||
Agile Tips to Make the Most of Conferences Time spent at a conference is precious, so you should make sure there is a return on that investment. What better way than to leverage agile ideas? Here are a few tips based on the principles behind the Agile Manifesto—embrace change, collaborate with others, and more—for making the most of attending a conference. |
||
How Embracing Differences Makes More Robust Agile Teams On any team, there are bound to be some differences. But even though work styles may differ from what you expect, they may not be problematic simply because they are different. Before making assumptions about what a teammate is doing or why, just ask to find out. Their differences may bring a helpful new perspective. |
||
Change Is Hard, but BDD Is Worth It Behavior-driven development is a methodology change that impacts the whole team, and unfortunately, it’s not as easy as writing scenarios in a specific format. What is the added value of BDD? Why should the team throw their current process out the window and try to incorporate a new methodology? Here are some reasons. |
||
Making the Product and Development Partnership Thrive The product manager and the development lead partnering well together is a cornerstone of great product teams. The behavior they exhibit sets the standard for how the team cooperates, connects, and thrives. One great way to do this is getting closer to your customer. Here’s how this advice works with both protagonists. |