Panel Discussion: Achieving Cross Roles Collaboration to Build Quality Software

Today’s software development teams are comprised of specialists, each playing a specific role based on skills and responsibilities. Project managers are responsible for managing projects. Scrum masters guide Agile teams. Business analysts focus on analyzing business requirements. Developers code the software, and QA/testers test the software. Many of these roles are defined by a body of knowledge (BOK), have certifications, and/or professional communities for continuous learning. Whether a software development project is agile, iterative or waterfall, the project’s ultimate success is based on collaboration and an emphasis on building quality into the software instead of testing in quality at the end. Our panelists, representing each of the roles within a software project and are leaders within their respective professions. Come join them as they breakdown role-based silos and share insights to collaboratively building quality software.

  • How does each role define quality software? What are the similarities and differences in these perspectives?
  • How does each role’s Certification Body of Knowledge support building quality software?
  • What challenges does each role face within a project team? How can collaboration overcome these challenges in waterfall, iterative or agile?
  • What are the pros and cons of specialized roles vs. project team members interchangeable in their roles?
  • How can application lifecycle management (ALM) tools foster cross role collaboration?
  • How can other roles help testers ‘shift left’ within a project?