...
- Retrospective
- What went well?
- What went wrong?
- What did we learn?
- What should we do differently?
- What was completed?
- What remains to be done?
- When/How should we plan on completing the effort?
- Does the team have on-going availability?
Notes
- Retrospective
nd:
just got up to speed near the end, lost a few days due to easter
better git workflow in etv
hard to get a team together, everybody working in concert etc.ml:
problems with getting testing environment up and running
rb:
learning curve is slow, first time in a sprint is a lot of overheadbl:
only joined towards the end
great to surface things from fresh eyes and testers
incrementally testing and verify is better, so getting pull requests tested and merged as it goes along is bestmh:
impressed with amount of work we did
team spirit is good
problems with jira, git, whitespace, took more effort than anticipated, had to acclimate to structure
need time to learn new tools, and teach tools to other team members, heavy case load and supporting team members at same timerof:
wished i had more time to spend on sprint
not much else to sayaw:
echo nd thoughts on team and team spirit,
impressed with level of testing,
good to clean up whitespace
some process points could be improved, more clarity around test/verify/merge/iterate
availability could have been better, more people signed up than were available
understanding git and github, it is an ongoing practice, git is an issue that needs its own time
making prerequisites more clear, installation should not be a barrier
2. What was completed:
aj: testing not quite finished, did not install new language, did not get around to documentation
nd: testing completed, did not get prereq. of install to document process
mh: worked on selenium test bench, automated testing is step by step, and advancing in phases. lots of work to set things up, reset/reload, results in a heavy unit test. work to separate out dependencies from language/vivo
bl: worked on language filters