MY LEARNINGS TO BECOME AGILE SCRUM MASTER

Regression testing a Product Backlog Item (PBI) in Azure Boards involves retesting the PBI after changes have been made to ensure that the new changes have not introduced any new defects or issues. Here are the general steps to perform regression testing on a PBI in Azure Boards: 1. Identify the PBI to be tested: Select the PBI that has been modified or updated and needs regression testing. 2. Understand the scope of changes: Review the changes made to the PBI, including code changes, feature enhancements, bug fixes, etc. 3. Create test cases: Based on the scope of changes, create or update test cases to cover all the scenarios that need to be tested for regression. 4. Execute test cases: Execute the test cases on the updated PBI to verify that the changes have been implemented correctly and that existing functionality has not been impacted. 5. Report defects: If any defects are found during regression testing, report them in Azure Boards and track them to resolution. 6. Re-test: After

Capacity planning is the process of determining the available resources, such as time and manpower, needed to successfully complete a project or sprint. It involves estimating the amount of work the team can handle within a given timeframe. For a 5-person Scrum team working on a 2-week sprint, capacity planning involves calculating how much work each team member can realistically handle during that time period. This typically includes factoring in any potential constraints, such as holidays, meetings, or other responsibilities. As an example, let's consider a 5-person Scrum team working on a project to improve the user interface of Gmail. Each team member has an average capacity of 6 hours per day for the sprint, taking into account any non-project related tasks. Based on this capacity, the team estimates that they can allocate 30 hours per day (5 people x 6 hours) towards the project. Over a 2-week sprint, this amounts to 300 hours (30 hours/day x 5 days x 2 weeks). By breaking do