Page History

(Escalation) To communicate with E to define roles/responsibilities in terms of epics/stories/prioritization decision making .

Cross team meeting on new way of implementing user story breakdown

To be done for next retro

> Didn't have time

Clarify names on the tests (i.e. Integration tests) and create guidance for team

Daniel Hanrahan 

still need to follow up on use of Acceptance tests 

On user stories - 

• (E) be clear on acceptance criteria before starting especially when working with bugs
• use right level of Jira creation i.e. 'user stories' 'sub tasks'
• description on Gerrit for code reviews

> (E) has been better on writing acceptance criteria ; 

Steps to reproduce still needs to be provided though!

On bugs -

say 'NO' more often especially when there is not enough information!

On release notes -

Update release notes with commits if possible

• Note to add it on acceptance criteria (if it makes sense)

Call 'retrospect' like meeting with (E) to discuss ways of working with CPS team. 

CPS team has repetitive points from previous retrospective meetings that relates to the E team

Example of points to discuss

• Priorities and planningReleases
• Ways of working with developers

Lack of communication and involvement needs to be resolved here.

Follow up to ask Peter K or (E) regarding new team integration (for datajob)