This website uses cookies. By continuing to browse or login to this website, you consent to the use of cookies. Learn more.
OK
DebKelchner
Commodore
Commodore
‎2015-02-27 13:42
700 views

Process when Defect is not completed in the Sprint it is assigned to

What is the suggested process to follow when a Defect is not completed in the Sprint it is assigned to? 

 

A scenerio we encounter is some tasks are completed within the sprint but not all.  If we reassign the defect to the next sprint, the completed tasks are also moved so it appears all the work was done in the new sprint and therefor skews metrics. 

Tags (1)
0 Likes
Reply
Report Inappropriate Content
1 Reply
KimLandau
Absent Member.
Absent Member.
‎2015-03-09 12:42

Hi Deb,

 

Since splitting a defect is not a good solution (Defects are not "splitable" because it skews defect data), our best practice would be to convert the defect to a US.

The defect would still exist and it will be linked to the new US with a comment that this defect was converted to a US. This info will be in ALM.

Until this feature would be available, it should be done manually --> create a US --> link it to the defect.

 

 

Regards, Kim.

 

0 Likes
Reply
Report Inappropriate Content
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.