Remote development mainly involves the same tasks and challenges as when you're sat in the same office, except that any communication issues can't be fixed by physically standing/sitting next to someone. Instead the tools we use have to support us in making the sure communication works.
One of the concerns with remote working is how meetings work. I can't give a general answer, but over about 10 years remote working in software development team, I can talk about the regular meetings that pretty much work for us.
My solar inverter doesn't include any external monitoring or data collection. But it does have an RS232 socket - Raspberry Pi Zero to the rescue! This is a scratch pad page for the project
In the beginning was the project kick-off meeting. And following this, Lo' the developers did say "erm, what are we actually building, how are we building it and where do we start?"
As (or before) the first iteration of an agile development, I'm suggesting that it can be helpful to have a Zeroth Iteration to get some "scaffolding" in place and start things moving.
There are many things to consider when you have a webapp that dynamically generates reports and that generation takes a while. This article is about giving the user some feedback that their report is being processed and hiding that message once the report has completely downloaded.
This is a followup to the article Gracefully handling inherently slow webapp actions