XP @ Scrum

XP @ Scrum enjoys this classic description.

The new team is transforming agile development. I also read some documents. XP @ Scrum is my goal.

We hope we can help each other with experience and transformation.

Let's talk about recent problems.

1. I understand the requirements, but I find that there is a problem when the requirements are passed down.

2. The number of bugs seems to need to be controlled.

So this iteration made the following adjustments.

Solution 1

The Planning Meeting invited the principal person in charge of business department requirements to talk about business communication. About 2.5 hours;

Business sorting tasks are added during the development of each function point. Including communicating with me. Of course, it was said at the scheduled meeting in the form of "Suggestions.

Communicate at any time. Because I often have meetings and interviews. So I set up a small area in my location. When I was absent, I could leave a message (for fear that the programmer had a problem at the time. When I came back, he forgot to contact me .), When you return, you will be contacted immediately;

Solution 2

Physical task wall. Each task enters the test area to be tested. only after passing the test can the tester enter done;

This module requires the acceptance of business personnel, that is, at the review;