Team Commitments
YSB 4.2 Deployment
Sprint Cloud Atlas
Goals and tickets are a team commitment, not an individual commitment.
Dev team will take advantage of refinement to dig into language in stories and answer questions/remove ambiguity related to requirements.
Communication between Devs and QA helps keep the process moving smoothly
Questions about prioritization should be discussed daily during standup.
To Do: Follow up on Accessibility training for Dev and QA.
Team Lessons Learned
Developers
YSB 4.2 Deployment
Dev team to walk through the Acceptance Criteria more deliberately in refinement
Dev: User stories needs to be broken down more in refinement and in advance (example:
)Jira Legacy server System Jira serverId 0ff96486-f711-332c-a18e-be3fd600929c key CUS-13587 Raise red flag further in advance
Estimates need to reflect planning on working on one story at once
Sprint Cloud Atlas
Ask more questions in refinement about specifics in implementation
Example: “Search all text” - is this grant entity only, or all entities?
Involve other technical collaborators during initial planning phase, specifically around system architecture
IE, Data Services
Versioning must be a part of all development moving forward to help with individual deployments
QA and Dev could include system/browser specifics in bugs/defects
Team needs to document standards and practices around PDFs
To Do: Standardize and document process for ensuring versioning for all features moving forward
Team Lessons Learned
QA
YSB 4.2 Deployment
Sprint Cloud Atlas
QA and Dev could include system/browser specifics in bugs/defects
Screen size and standard screen resolutions must be standardized & documented for testing and Devs
Team Lessons Learned
BA
YSB 4.2 Deployment
Sprint Cloud Atlas
Team Lessons Learned
PM
YSB 4.2 Deployment
Sprint Cloud Atlas
Impromptu deployments need to be documented, go through the change process, and signed off on internally before communicated to the client.