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. |
||
The ‘Third Rail’ of Project Management: Cutting Quality Scope, schedule, and resources: Whether you’re using agile or more traditional project management approaches, this triple constraint is the law of the project universe. The unmentionable “third rail” of project management trade-offs is compromising quality to deal with the other two aspects. Don't make that an option. |
||
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. |
||
A Goal to Get You Writing NaNoWriMo—National Novel Writing Month—is a month off, but it’s not too soon to commit to participate. The goal is to write 50,000 words (about 175 pages) during November. That may seem crazy, but there's lots of guidance and support available online and in local writer chapters. Break through that writer's block! |
||
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. |
||
Creating a Community of Testers Many teams are divided by product or feature, with only one dedicated tester per team. How do you learn and grow in your career when you’re disconnected from your peers? One solution is to create your own community of testers that spans the organization. Here are some ideas to start and facilitate a Quality Guild. |
||
Stop Email Overload and Communicate Better Many of us fire off correspondence to groups and distribution lists that include more recipients than necessary, and we overcommunicate without stopping to think about exactly what needs to be conveyed. Here are some ways organizations and teams can cope with the influx of information and communicate intentionally. |