Планирование спринта Эрика A2

On Monday, Erik joined his first sprint planning meeting. His team worked in short periods called sprints. Each sprint lasted two weeks. At the meeting, they opened the backlog, a list of work for the team. It included new features and problems they needed to fix. Erik read the list and asked a few questions.

One problem was with the login page. Some users could not log in to their accounts. This problem had a high priority because people could not use the website. Changing the colour of a button was less important. The team decided to discuss the login problem first. They talked about what they needed to do for this task.

Before choosing their work, the team needed to estimate its size. They used story points to compare different tasks. These points showed the size of the work, not an exact number of hours. A small task had two story points. A more difficult task had five story points. When team members chose different numbers, they explained their answers.

Erik asked, “How long will it take?” A developer thought the login problem would take about two days to fix. However, he might need more time if he found other problems. The team also discussed their capacity. This meant how much work they could do during the sprint. One colleague was on holiday, so the team could do less work than usual.

Erik agreed to take on the testing of the login page. He planned to check it with different accounts after the fix. Another tester offered to help him if he had questions. The team chose a few more tasks but left the rest in the backlog. Their main goal for the sprint was to help users log in without problems. By the end of the meeting, Erik knew what to do and felt ready to start.