What happens when defects go unnoticed until it is too late? Mayank provides an insightful view of the true cost of not providing enough test coverage during a software development lifecycle. He also suggests some techniques to ensure that defects are identified and mitigated early.
Agile projects assume that test planning, test creation, and test execution take place throughout a project's lifecycle. So the need for unit testing (and especially automated unit testing) can't be ignored and should be considered as a key responsibility of the entire team—not just the software developers.
It used to be that a project manager did one thing: manage the success of the project. As IT budgets shrink and job responsibilities expand, there is no such thing as a typical project manager role. You're expected to wear many hats, facilitate human resource issues, become a subject matter expert, and assist with key technical activities.
Whole team testing makes product quality everyone's business. It can also make people uncomfortable. Matt explains how this new way to approach project quality helps with leading retrospectives, conducting defect analysis, and mitigating project risks.
Claire takes us on a nontraditional journey where designing and implementing testing approaches can be rapidly organized into a hierarchy of connected elements. Mind maps, used primarily for visual and conceptual thinking, may be just the answer for quality assurance professionals.
What happens when younger knowledge workers, the millennials, bring a new perspective to an organization? Reverse mentoring can dramatically improve employee retention, team collaboration, and the adoption of newer technology.
Without clearly defined roles and responsibilities, actions taken by key project stakeholders may result in project misfires. Kyle shows what you should do to avoid the situation when roles are misunderstood, overlapped, or completely missing.