Page Comparison

Administrivia

meeting_saved_closed_caption.txt

PO perspective: life cycle of a feature

1]  Define the need in as much detail as possible: Organise talks; elicit feedback.
_“What is the problem?
What are we trying to solve?
What does the user need?
What are the most common use cases?
What are edge cases that should be accounted for”
_ Then translate into FOLIO!

2]  PO writes the stories based on the SIG input.

3]  Back and forth discussion with the devs to write finalise the stories.

4]  Devs develop; PO is available for questions and needs to validate (business) functionality in Snapshot, then Flower.

5]  User Acceptance Tests – try out your own workflows

6]  Communication and documentation

7]  Take on Bugfest tests! Please…..

8] Bug alert! What to do:
_ Narrow down the circumstances as much as possible; which options; intermittent = (exploratory) task, not a bug.
_ Replicate in Snapshot, current release and previous release (i.e. regression?)