You could say we're in the beginning stages of our application striving for an MVE experience. We're constantly measuring each feature sprint with what is the solution that helps the customer solve the business problem vs. what would the "smart" users want. Our team is full of smart users but we're not the audience.
Mixed into the situation, we have a deadline to get customers over from our current platform over to our new platform. Okay, that's the context for this game.
The game is called a Bridge Too Far. It helps you suss out your team's thoughts and ideas of what would be MVE vs what is the ideal solution money, time and resources aside.
Introduce one or two of your personas. Refer to them by name. If possible provide actual customer feedback based. Also introduce the design pattern. Perhaps it's something your team is familiar but often look to you as a UX/UI designer to solve. This is a great opportunity to impart your team leadership skills.
Next, provide a sketch or wireframe of the very basic UI elements and a set of drawing materials.
With a timer set for 10 minutes ask the group to add in UI features and tricks that are either REALLY nice, expensive or useless. These are a bridge too far features. Feel free to let your team have fun with this. Trust me, the smart ones will go for MVE++ and take it seriously. Loosen them up a little.
Finally, go around the room and have each team member talk about what their Bridge Too Far and explain why they think this is feature bloat.
The results. One, you'll be able to gauge the team's individual and group response and force them to out their solution as expected or not. Two, you might discover what you think is bloat is actually worth testing and bringing to the sprint. Three, you'll challenge your team to think outside of the norm on a particular design pattern.
Let me know if it worked for you.
Don't forget to validate your new feature with real audience members.