In the context of testing, following the standard steps of filing a bug report in an application management tool helps all the testers in a team have a shared process for managing bugs. A typical procedure may be as follows: take screenshots, supply the reproducible steps, identify the severity, upload the ticket, report to team. However, there will be instances where this process may not work for the testers. For example, they might find that taking screenshots for each bug might not be necessary anymore. Part of being Agile is discussing matters like this with one another to find what will work for the team. The Sprint Retrospective is an excellent time to bring up a process, such as bug reporting, and amend it to be more efficient for the team.
Agile encourages the members in the team to be as collocated or, at the very least, closely connected as possible. With collocation, one could simply walk over and demonstrate a problem. However, for distributed Agile teams, collaboration will pose a bigger challenge, since they are not in the same place. They will need to find the best way to collaborate with one another and decide if they will need messaging apps, video conference tools, and screen sharing applications.
Valuing “individuals and interactions” over “processes and tools” does not mean that processes and tools are no longer needed. It just means that processes and tools should match a team’s needs – and not the other way around.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course:
Course Contents
Section 1: Agile Project Management
Section 2: Using the Agile Manifesto to Deliver Change
Section 3: The 12 Agile Principles
Section 4: The Agile Fundamentals
Section 5: The Declaration of Interdependence
Section 6: Agile Development Frameworks
Section 7: Introduction to Scrum
Section 8: Scrum Projects
Section 9: Scrum Project Roles
Section 10: Meet the Scrum Team
Section 11: Building the Scrum Team
Section 12: Scrum in Projects, Programs & Portfolios
Section 13: How to Manage an Agile Project
Section 14: Leadership Styles
Section 15: The Agile Project Life-cycle
Section 16: Business Justification with Agile
Section 17: Calculating the Benefits With Agile
Section 18: Quality in Agile
Section 19: Acceptance Criteria and the Prioritised Product Backlog
Section 20: Quality Management in Scrum
Section 21: Change in Scrum
Section 22: Integrating Change in Scrum
Section 23: Managing Change in Scrum
Section 24: Risk in Scrum
Section 25: Risk Assessment Techniques
Section 26: Initiating an Agile Project
Section 27: Forming the Scrum Team
Section 28: Epics and Personas
Section 29: Creating the Prioritised Product Backlog
Section 30: Conduct Release Planning
Section 31: The Project Business Case
Section 32: Planning in Scrum
Section 33: Scrum Boards
Section 34: Sprint Planning
Section 35: User Stories
Section 36: User Stories and Tasks
Section 37: The Sprint Backlog
Section 38: Implementation of Scrum
Section 39: The Daily Scrum
Section 40: The Product Backlog
Section 41: Scrum Charts
Section 42: Review and Retrospective
Section 43: Scrum of Scrums
Section 44: Validating a Sprint
Section 45: Retrospective Sprint
Section 46: Releasing the Product
Section 47: Project Retrospective
Section 48: The Communication Plan
Section 49: Formal Business Sign-off
Section 50: Scaling Scrum
Section 51: Stakeholders
Section 52: Programs and Portfolios