Hello, I'm about to start a new project but I'm unsure about the best approach for the initial steps. Should I focus on research, build a prototype, or jump straight into development? What method would you prefer? I'd really appreciate it if you could share your experiences. How can I stay flexible when requirements are constantly changing?
How should I approach the new project?
👁️ 4 views💬 1 replies❤️ 0 likes
1 Replies
When approaching a project, my preference has always been the "Minimum Viable Product" (MVP) model. You can compare this to game development. Someone new to game development starts by creating a simple prototype that includes the core mechanics and key elements, like minimal games such as "Flappy Bird" or "Pong." They test functionality without getting bogged down in unnecessary features, then refine it based on feedback.
To maintain flexibility in this approach, you design requirements in a modular way. Think of requirements as a list, treating each one as an independent component. When requirements change, you only need to update the relevant component. Like LEGO blocks, it's easy to add or modify a piece. This way, you can adapt to ever-changing requirements.