Related Content
The Premortem: Planning for Failure While a postmortem, or retrospective, is done after a project is completed, a premortem is done before the project starts as a way to imagine that the project failed and to explore what went wrong. You list every possible thing that can go wrong, then devise solutions to the most probable risks—before you need them. |
||
Can Your Project Succeed without Your Sponsor On Board? Project managers are tasked by sponsoring executives to complete projects successfully and provide timely communication if barriers arise. But what should a project manager do if the sponsors are the biggest barrier? If you can’t get the answers you need, is it a good idea to make your best guess and proceed? |
||
How Testers Can Use Docker to Shift Left and Automate Deployments Docker has several advantages over virtual machines: It’s easier to deal with, starts up faster, and requires fewer resources. Using Docker also can give testers more confidence in their releases. Developers use the same environment that will be used in production, which streamlines code delivery and shifts QA left. |
||
Lessons Learned in Testing a UI Test Automation Tool How do you test a tool to be used for automated testing? If a tool executes an automated test that generates keyboard and mouse events to replay user actions, can the test emulate user input and control another instance of the tool to automatically record and play another test? Here's how you test the test tool. |
||
Yes, She Can STEM—and More Many girls begin losing interest in STEM subjects as early as middle school, and this path continues. #SheCanSTEM is a new public service media campaign that hopes to encourage middle school girls to ultimately pursue STEM careers by challenging stereotypes and showcasing female STEM role models. |
||
How to Prioritize Tasks and Do Only the Work That Matters When you’re working on multiple projects at a time and everyone is breathing down your neck for results, it’s difficult to separate wants from needs. You have to be smart about task prioritization. Here are four ways to break through the noise and make sure you’re focusing on the work that really matters. |
||
A Tester’s Role in Requirements Exploration Agile is supposed to get people to talk to each other in real time. However, many teams still lack a shared understanding of what they are going to build, even as they start coding. As testers, we can explore feature specifications early, contributing to successful and timely delivery through defined requirements. |
||
Wisdom from Consulting: Getting and Vetting Advice When you hire a consultant, they may appear to have a wealth of experience and knowledge—and may actually have it. But accepting their advice without question is dangerous. Here are some good practices to keep in mind when you're receiving advice, including asking questions, exploring alternatives, and analyzing risks. |