You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Participants
Retro Points
Some things to think about:
- What did we do well, that if we don’t discuss we might forget?
- What did we learn?
- What should we do differently next time?
- What still puzzles us?
- Which tools or techniques proved to be useful? Which not?
- What is our biggest impediment?
- If we could change 1 thing, what would it be?
- What caused the problems that we had recently?
- Which things went smoothly? Which didn’t?
| # | Subject | What went well 
| What didn't go well 
| What can be Improved 
| Puzzle/Blocker |
|---|
| 1 | Reviews/tasks/docs | - Improved review process speed/turn-over
- Code review process (Code Quality)
- Documentation has improved
|
| - become clearer about who is assigned to a Jira using reviewers in gerrit
- is everyone participating equally in reviews
- earlier sharing of reviews
|
|
| 2 | Responsibilities | - Sharing work
- Team collaboration is working together as a group on a project, process, or concept to achieve a better
|
|
|
|
| 3 | Performance/Env | - performance bugs slow
- just one person working on these
| - Performance environment
| - share with others
- report of perfoamcne issues, progress
|
|
| 4 | Staffing | - - too many people leaving :-( Bell opted out
- Adity no loger full tim on CPS :-(
- BT starting to particpate
- Luke will be participating with new team
| - attendeance during Tuesday in office, maybe betetr after summer
- Team members left
|
|
|
| 5 | Software/Bugs |
| - Bugs coming up are not that descriptive and missing files, steps, etc.
| - Fault slip analysis (FSA) should be done for major bugs
- .KT OOM (Kubectl)
| - Lliquibase changes, is it the best approach?
|
| 6 | Meetings/WoW | - . Early scrum meeting(Better planning for the day)
- Team meeting every 2 week
| - Backlog grooming (More questions need to be asked)
|
|
|
Actions