Our retrospective got our team talking about the good, the bad and steps to a better future (for Clairvoyance). Our flip charts are in German, but I will explain the content in English.
We do our homework on time. We reliably write blog posts and peer reviews in accordance with each weeks grading criteria. The spring boot hello world instance is up and running (sometimes). SCRUM tools are deployed and are utilized (more on this later). Some Use Cases regarding the frontend are nicely specified and come with pretty mockups.
Some weaknesses in our inception phase have become apparent: there is currently one UC with one UCD that covers both user navigation to and view of the data. The UCD and its mockups specify the navigation well.
While we have all the tools to SCRUM, we so far have not used them effectively. This spirals adds to our time management issues and a lack of ownership by team members.
Steps to a better future
We will add a new UC to deal with the data view. Over UCs and our SRS will be adapted accordingly. More realistic specs and informative UCDs will aid implementation.
The biggest step towards more productive (team)work is build on the making SCRUM work. We have all the tools, now we will use them. Specifically, team members put things, they want to have done into tickets. Appropriate parts of the product backlog are pulled into the sprint backlog each thursday. YouTracks timekeeping feature will be used at a short retro to compare the input of each team member to address impediments.
I believe we have identified some of the biggest impediments in SaSEps workflow. The tools change things are already deployed. Now we have to change our work culture to level up.