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. |
||
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. |
||
DevOps Transformations for QA Teams: A Slack Takeover with Stacy Kirk Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. QA architect an agile coach Stacy Kirk, founder of QualityWorks Consulting Group LLC and nodeqa.io, hosted this Slack takeover and discussed improving teams by implementing DevOps practices. |
||
Agile Is Not the Same as DevOps Agile and DevOps are two terms that are often confused with each other and sometimes used interchangeably. But they are not the same idea. While both improve software performance, these concepts are actually quite different. Let's look at their definitions, origins, and principles, as well as using each in practice. |
||
5 Mistakes to Avoid When Implementing Agile at Scale Businesses are increasingly hopping on the agile bandwagon, but ensuring effective adoption of agile practices throughout the organizational hierarchy is easier said than done. To ensure that your agile transformation doesn’t get stuck in limbo and is scaled successfully, you need to steer clear of these common errors. |
||
The Myth of Too Many Scrum Meetings A common complaint in organizations adopting Scrum is that Scrum has too many meetings. However, people may not be considering all the time they spent meeting before Scrum—and how effective that time really was. As long as you keep meetings focused, people should waste less time in meetings than they did before Scrum. |