Agile FAQ - Part 1


Here are some of the basic most commonly asked questions on Agile.

Q1. For Story Bug I see Discovered/Injected/Planned Release and Iterations. What do they indicate?

Discovered Release/Iteration indicates when the defect was found. Injected Release/Iteration indicates which Release/Iteration caused the defect. Planned Release/Iteration indicates when the defect is planned to be addressed.

Q2. What will the Planned Release and Planned Iteration drop downs list for a Story bug?

Planned Release will list the Releases with sequence number >=Discovered Release. Planned Iteration will list the iterations mapped to the Planned Release and with sequence number >= Discovered Iteration if Planned and Discovered Release are the same.

Q3. For my Agile Project type, while editing Story Bug details, system is prompting to enter the data for Discovered Release and Discovered Iteration.

As part of the new enhancement, two new fields (Discovered Release and Discovered Iteration) have been introduced in the Story Bug Screen.The Existing Story bugs will not have data for Discovered Release/Iteration, so PM is expected to enter the details for the same. However for closed requests the new fields can be left blank.

Q4. The field name ‘Release and Iteration’ in the Story Bug screen has been changed for my Agile project type.

As per the new enhancement, the field names Iteration and Release have been renamed to Planned Iteration and Planned Release.

Note: The Planned Release selection gets populated based on the Discovered Release selection.

Q5. While defining the Defects details in Review /Testing created under a Story / Story Bug, system is prompting to map the defect to Injected Iteration. What iterations will be listed in this drop down?

Summary and Action sub tabs of Reviews/Testing created under a story will have 'Injected Iteration' as a new drop down.Existing Review/Testing will not have data for this new field. User can map the defects to Injected iteration for open Review/Testing.
Injected Iteration will list all iterations that belongs to the Planned release (which is mapped to the story) and having Iteration sequence number <= Planned Iteration.

Q6. Is mapping defects to Injected Iteration mandatory?

If the Injected Phase selected is Release Implementation then selection of Injected Iteration is mandatory for the defect.

Q7. Can the defects in existing open Review/Testing be mapped to Injected Iteration?

Yes. The defects in existing open Review/Testing can be mapped to the Injected Iteration by clicking on the defecting and selecting the iteration from the dropdown.

Q8. Will I be able to create Review and Testing without mapping to any Story/Story Bug for an Agile PG?

Yes, PM will be able to create both Review and Testing without mapping to Story/Story Bug.

Q9. What Review types are possible when an independent review not mapped to a request is created?

Document Review can be created. This review type has been made available since activities during Architecture/Exploration phase could involve documentation.

Q10. How should I decide on when to create independent review/testing?

Activities in Architecture/Exploration phase may require Review/Testing without being associated with a Story/Story bug. In such cases Review/Testing can be created directly from left navigation.

No comments:

Post a Comment

Recent Posts

Popular Posts

© 2011-2019 Web Portal Club