Are you a developer or manager? Your proposal is applicable in very special scenario but it requires complete change in your development process and the way you do the business.
What did you do when you work as one team:
- You had regular sprints with commitment, vision, meetings, scrum board, burndown chart etc.
- Sprint was safe zone for the team
- You had a product owner responsible for defining product backlog
- You had a Scrum master taking care of you and dealing with your impediments
- You had a global code ownership and team spirit
- You was empowered to choose a task
- At the end of the sprint you delivered probably shippable product which offered new business value to your customer
What you have now:
- Multiple people working on separate micro apps - no shared code, people are not empower to select task from other team member
- Probably each team member have own product backlog and own "product owner / customer"
- Probably each team member have different deadlines - different sprint start, different number of sprints, different length of sprint
- Team member has commitment only on his micro app
Do you see a difference?
- What will be purpose of Daily stand up if each team member is working on different commitment?
- What will be purpose of planning meeting if each team member is working on separate application? Will you have one planning for each team member / customer?
- What will be purpose of Retrospective if team members doesn't work together - they don't share any code?
- Will you have one review meeting for each team member / customer?
The first is Scrum, the second is not and cannot be. Narrow this to Scrum would be hard - it would require you to consolidate the process to single development team extending the application and sharing commitments for all customers - basically abstracting customers by single Product owner. Requirements from customers would be prioritized by product owner and delivered in sequence by priority.
Well as I wrote this I see that you don't need Scrum. You would get more value by switching to Kanban which will much better work in scenario where customers are not able to define requirements in the same time and require different delivery dates.
This is applicable if all customers requests some extension to single application or if it same type of programming - for example doing data transformation, integration packages, etc. If it is based on multiple applications you should not combine them in single team.