Please enable JavaScript.
Coggle requires JavaScript to display documents.
Release retrospective Release 2.0 - Coggle Diagram
Release retrospective
Release 2.0
Business Architects
Requirement refinement
Some important topics discussed in the comments section should be part of the acceptance criteria and not just remain in the comments of the story.
Quality Assurance
Status update
Any delays on the status update end up delaying the work from Miipe.
Keep the stories and bugs with their statuses up-to-date.
In-flight case scenarios
Working ahead of time while planning for in-flight case creation (pointing the application version).
We should not be neglecting in-flight scenarios.
Bugs
To describe the steps to consistently reproduce a bug, if possible.
System Architects
Story sizing
Underestimating stories leads to working extra hours to finish the development.
The DEV team needs a space to discuss approaches (pros and cons) of the stories before their sizing.
Customization
Avoid customization at all costs.
Any solution found that involve customization should be mentioned in the bug/story as well as the risks it poses to the application regarding maintainability etc.
How much will we allow the Pega OOTB components to be customized?
Bugs
Set up a deadline on the amount of time to be spent on while attempting to either reproduce a bug or fix a bug.
Communication
It has improved (both among the team members and between RC and the client)
Sprint events
Sprint Review/Demo
Demos are getting better
Call out the known issues before presenting the story to both the RC team and the client.
The QA team can participate on the preparation for the demo meetings
Sizing sessions
Shorter meeting is the best way to have those meetings (30 minutes).
The team should review the stories to be sized, if possible.
The earlier the team knows what stories will be sized, the better.
Sprint Retrospective
The team does not feel comfortable sharing their thoughts and suggestions for improvement in the meetings with the client's presence.
To have more
internal
Sprint Retrospectives (a 30-minute meeting).
Mock-ups
They should be following Pega OOTB standards and application standards
The RC team should be more involved while the mock-up are being elaborated.
SM
Sprint planning
Work on the planning of the subsequent Sprint ahead of time to give team time to also plan their activities ahead of time.
Team collaboration
Keep up the great team work!