This is the current picture of the items in the sprint:
Time spent on non-BLISS tasks:
And the burndown chart:
During the Retrospective we focused on discussing the attached document: Proposal_for_clarifying_what_is_included_in_BLISS_sprints.docx
The team decided to:
We will carry on using SCRUM with a Planning meeting at the start, stand-ups three times a week, Review and Retrospective at the end of the Sprint.
We will be more active regarding GitLab's issue board, trying to ensure that it is up to date for each stand-up (this includes task list, status and definition of done).
Bring a laptop to the stand-ups, so we have a good view of where we are (we will update the board then and there if not yet updated).
We will NOT track items outside BLISS.
We will not split stories to separate development and integration in the BLs.
We agreed a new way to control how items move accross GitLab's issue board:
6.1 When we assess the stories at sprint planning we will not take into account integration in the BL or when it will take place.
6.2. Items that can be tested in the lab without support of external dependencies (i.e. BLs) will be closed normally.
6.3. Items that must be tested/integrated with external dependencies will not have this effort specified in the story.
6.3a. Instead, when all work that can be done at this stage is completed they will be moved to a new status: "Pending Integration". At this point we will count the points.
6.3b. "Pending Integration" will become a list of items that are pending some work with external dependencies and that cannot be scheduled normally within sprints.
6.3c. When it will be possible to finally complete an item from "Pending Integration" it will be done. Points for that will be counted a posteriori based on the amount of time spent doing the work.