Notices by Adrian K. (goshki@mastodon.gamedev.place)

[1/4] Here's something cool from “Wright Files: Egerton’s Pickle” development! I think I’ve finally nailed low-res retro style with 3D environments and 2D sprites (notice how characters maintain constant size regardless of camera distance).

#gamedev #indiedev #madewithunity

@jzillw yes, exactly! I think we've looped back to the initial notion of business people's aversion to spend time (and money) on something that was deemed done. 😁

@jzillw great example showing how it's not possible (or sometimes just not feasible) to design/implement a feature upfront-ready for some future extension. That's why I'm a die-hard proponent of iterative approach (where iteration sometimes means implementing a feature gradually where each next step is informed be the previous one and sometimes it means introducing separate version of the feature and gradual exchange of its existing uses). YAGNI and KISS FTW! 😄

@jzillw and re: half-baked features, this is also another issue with obsessing with the process – typically business expects that once a story is done then the feature is done and there should be no need to re-open it again. But this is often not true in case of projects with strong creative aspect (like games). The question is: should implemention of a feature be agile-driven if the feature requires iteration and tuning process.

@jzillw obsessively trying to do agile “by the book” is one of the banes of software-related companies and projects. The essence of agile is that no rule is set in stone and every part of the process should be scrutinized for its value. Anecdotally, I've been on a dozen of projects where switching from sprints to kanban at one point was one of the best decisions a team (and PM) could make.

@jzillw with visual style by Matthew Lyons!

https://twitter.com/LyonsMatthew/media