Some thoughts on being a new-commer to Dwyl processes

As a newcomer coming into the project it would be helpful to have a set of clear basic guidelines to follow. What we should aim for, and what are 100% requirements.

I think it is also reasonable to expect there to be serious teething problems taking on a new project, a new partner and new processes to follow. I personally would have found it helpful to have a couple of things to focus on in a given sprint, then I know that I have to be doing those processes and will not feel hard done by if/when it gets brought up in a PR. That way good habits can be gradually built into our work flow. It might also help you identify the specific processes that people really struggle with and understand why.

Opening an issue in order to have a discussion on every question/idea that we have still seems a bit ambitious especially given the QAs time constraints.

It has been suggested that we should try a new feature/idea out in a separate spike, which sounds like a great idea, but is there time made for that? If there is it would be helpful to have some input from the QA at the beginning of the sprint to identify a good feature that we could separate into a ’spike’.

Before starting a dwyl project for the first time, if you expect people to use modules like hapi login, make sure they know in advance, and that they know and really understand how they work.