Extreme Programming Practice


Weekly-Cycle is one of the primary practices of Extreme Programming. It describes the process of setting up a weekly team and customer meeting. During the meeting, you’ll review your previous work and establish the software development process and goals for the upcoming week.

Why should you do the Weekly- Cycle practice?

The core benefit of this practice is that it allows you to stay on track with your tasks as well as the customer’s requirements for the next week. Feedback and communication are some of the core values of Extreme Programming. The regular meetings are the primary method that will allow you to achieve these values. Furthermore, having smaller time periods for completing tasks increases the productivity of the team, and provides a sense of achievement at the end of each week. How to practice Weekly-Cycle?

When the team just starts working together or takes on a new project, the weekly meeting could last for hours. However, spending too much time on planning is generally thought of as a waste of time. The end goal is to the shorten these meetings to an hour per week. That will allow the developers to spend more time in their actual work. Nevertheless, don’t force short meetings at the beginning. It will happen gradually, as the team develops their planning skills and work structure.

You should divide the weekly-cycle into two main stages:

Overview of the previous week

This stage is all about feedback. Both your customer and the team should conduct a functionality test, to estimate the current state of their system. Doing this on a regular basis allows the programmers to spot and recode any mistakes. Furthermore, the customer will be able to make an overview of the completed work and see if the team has met all the deadlines established in the previous week.

Plan for the next week

Planning is the primary feature of the weekly-cycle. The customer will prioritize the stories he wants to be completed in the next week. Meanwhile, the development team will separate those stories into small tasks for each member of the group. You should primarily focus on the most relevant stories, which you will test and complete first.

Start the week by conducting automated tests for the stories. Spend the rest of the time for debugging and implementation. The primary goal is to successfully deploy an upgraded version of the software by the end of the week. This technique doesn’t only increase productivity, but it will also give a team a reason to celebrate each week. As a result, you will achieve a more motivational and positive work atmosphere. That is one of the fundamental ideas of the Extreme programming, and shouldn’t be overlooked.