I'm not an expert in this by any means, but maybe using Scrum with a one week sprint instead of two can help. Use your boss as the product owner (the one that says what he wants done and what he doesn't), ask him what his priorities are, select the priorities that you think your team can achieve in one week and divide into different tasks that each member of the team can do. Then code, code, code until you finish what you selected for that week and only what you selected. After each Sprint you're supposed to have a piece of the final work that you can already show and put into production, so you can show the results to your boss.
Obviously I just did a massive simplification of Scrum, but it's just an introduction. We're using this in our company and it's working surprisingly well. If you want more information you can take a look at the official (and free) Scrum Guide.
There is a problem though and that's you will be taking on a lot of work since you will have 2, if not 3 roles: lead developer, Agile coach and, maybe, product owner. I've been in a similar position and it becomes very difficult to do everything. It will be essential to have your boss or the product's sponsor in the role of product owner and have the committed fully to that role. Otherwise, the likelihood of failure is going to be high and you will be the one blamed for it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not an expert in this by any means, but maybe using Scrum with a one week sprint instead of two can help. Use your boss as the product owner (the one that says what he wants done and what he doesn't), ask him what his priorities are, select the priorities that you think your team can achieve in one week and divide into different tasks that each member of the team can do. Then code, code, code until you finish what you selected for that week and only what you selected. After each Sprint you're supposed to have a piece of the final work that you can already show and put into production, so you can show the results to your boss.
Obviously I just did a massive simplification of Scrum, but it's just an introduction. We're using this in our company and it's working surprisingly well. If you want more information you can take a look at the official (and free) Scrum Guide.
Good luck!
😤😭👍👌
Thanks Man.
I agree Agile/Scrum is going to be the easiest and best way to handle this.
We use Planning Poker to estimate our user stories. This makes estimation a team effort.
Mountain Goat Software is another good Agile resource.
There is a problem though and that's you will be taking on a lot of work since you will have 2, if not 3 roles: lead developer, Agile coach and, maybe, product owner. I've been in a similar position and it becomes very difficult to do everything. It will be essential to have your boss or the product's sponsor in the role of product owner and have the committed fully to that role. Otherwise, the likelihood of failure is going to be high and you will be the one blamed for it.