1. Come up with a feature. 2. Code it. 3. Test it. 4. Release it. Occasionally: Think if there's any process/code problem you keep running into, and spend s

1. Come up with a feature. 2. Code it. 3. Test it. 4. Release it. Occasionally: Think if there's any process/code problem you keep running into, and spend some time fixing that. Don't overthink it. Most of the process ideas that exist out there exist to facilitate communication, which is completely irrelevant if you're the only one. Also, don't create a process for people who don't exist yet. They may never exist, and if they ever do exist, your process will need to accommodate their needs. Having a process already in place creates a "this is how we do things" that creates opposition to accommodating the needs of new members, and puts them in the position of having to change a process they never agreed to and had no part in creating. Remember, agile isn't a process, it's a set of principles[1]. "Individuals and interactions over processes and tools" means that you find the individuals first, and collaboratively build a process that works for everyone involved. [1] https://agilemanifesto.org/ https://agilemanifesto.org/