Play game
10x Sprint Master's itch.io pageResults
Criteria | Rank | Score* | Raw Score |
Innovation | #38 | 3.833 | 3.833 |
Theme interpretation | #143 | 3.500 | 3.500 |
Overall | #198 | 3.000 | 3.000 |
Gameplay | #226 | 2.722 | 2.722 |
Graphics | #281 | 2.611 | 2.611 |
Audio | #323 | 1.944 | 1.944 |
Ranked from 18 ratings. Score is adjusted from raw score by the median number of ratings per game in the jam.
GitHub repository URL:
https://github.com/Enet4/10xSprintMaster
Leave a comment
Log in with itch.io to leave a comment.
Comments
I echo what others are talking about.
Some other issues I had were in the UI and how players got information. Like, some months I lose points much faster than others - I assume that's due to pushing buggy code to release without checking it throughly, but I have no sense of which code was causing the issue, and there's no indicator to show how much my score is going down over time.
The UI choice to have all the developers pop up at once every time you pick up a ticket is... interesting. Was it supposed to have one at a time pop up, like, so you know which one you're dragging to?
The review process was very frustrating - unlike the other tasks, there was no way of knowing which ticket was currently being reviewed, so I had no idea which were safe to move over.
I adore the aesthetic, and this was a very creative idea, but as a simulator game it's a bit lacking.
Thank you for the thorough feedback. :)
The score lingering was indeed designed to be unintuitive to the player, since it was meant to be a rough approximation of the clients' receptivity to the product. It slowly takes hits depending on the quality of the software. While you never know how many bugs there are, the end of each month gives you a qualitative measure of technical debt.
The developers popping up was just a simple mechanism to facilitate dragging a task onto them. Making it more sofisticated would require a lot more effort than it was worth for the jam.
As for reviewing, I agree that it is a bit frustrating. The task under review by a particular developer is always the topmost one assigned, although it might not always be clear which tasks are under review at a particular time and how much time have they been under review. One idea that I originally had was developer profiles, which would give team members some personality and freedom to decide what to work on.
And ultimately, the game would need some more polishing to have a fair difficulty. I suspect that reaching the winning condition is next to impossible. 😅
I guess the question is, what kind of game is this trying to be? Is this an art game about the futility of taking over a software project with a team that's too small, or is it a simulator game where you build up the project to completion?
Because if it's the latter, the score being intentionally unintuitive is a bit odd. After all, in real life governments never know how much population growth or money or food levels are exactly changing over time, but pretty much every simulator game (Civilization, SimCity, whatever) does show exact numbers that update instantly.
Realism only works as much as it serves the purpose of the game.
Perhaps reading the blog post on the subject will help clarify what I was going for. https://dev.to/e_net4/10x-sprint-master-a-technical-and-social-experiment-ahp Not because I disagree with what you said, but while I had intended the game to be fully payable, some design decisions were strongly driven by the concepts I wished to portray in it.
tbh I got a little bored, but before I did I never really felt I was in control over whether the code was being reviewed or not. It wasn’t easy to reconcile the developers actions with their active task, and honestly outside of this game and in the real world most of this happens according to process and doesn’t require such a hands on process of a PM moving each ticket through each stage about and re-allocating them.
I thought the game idea was really quite innovative and I gave it 5* in that category but I didn’t feel like I was actually building software. Perhaps the tickets could have been more than just a number but could have told a story in themselves (maybe even some ironic ticket titles showing how design by committee results in everything we build being blue + grey!)
Nice idea, and hey - and the only “bug” I found may have been a feature ( accidentally moved a bug ticket to done and couldn’t move it back… )
Thank you for playing. I agree with the tasks feeling a little bland, there were plans to give each of them a generated description, but that had to be dropped for the jam submission. And yes, that last thing is by design: once merged, it's merged, with or without bugs. :)))
Definitely a unique take on the theme! I would've liked to see it ramp up a bit quicker (it's pretty boring when you only have one or two characters and are doing the exact same pattern over and over) but it was cute and a nice time-sink.
Great concept. Tested earlier also on Discord. Still getting stuck at the end of onboarding :(
Thank you for the bug report! Alas, I could never reproduce this one to this day. 🤷♂️
Nice idea. But I agree with the other comments. This is like my day to day job :)
Oh my, this is more or less my day job :P so I was hoping to have a bit of an advantage going into this game. That said it was still stressful! I'm sharing your game with my colleagues to see what they think lol!
Really clever interpretation of the theme. Graphics are pretty minimal/simple but I don't mind that. Wish there was some more sound. Tutorial was great, and I'm sure people will find that quite useful. Nice work!
Somebody may find iterest in it.
Do you have cookies in game? Game is storaging progress.
Numbers and logic, ohhh) Tasks and deadlines ,like a job)
Thank you for playing!
The game uses local storage to save the current state each month, but it might only work on itch.io by allowing cross origin resources in the browser (shields down). Later on I might host it on GitHub directly, so as to not have that problem.
I never thought I would get to play a game that simulates my day to day work. It was a bit slow at the beginning but definetly picke dup pace and made it tough to keep it going. Interesting take on the theme, and a clever way to incporate the theme.
Well done!c:
Interesting game - it was quite additive! I appreciated the tutorial option and really liked the application of the theme. The graphics were well matched to the game. I had fun. Two things I was thinking might make it even more fun (though I'm not sure how realistic it would be): 1. Having characters with different skillsets that work on tasks faster depending on their skillset. 2. Having a little story element at the end to describe the consequence of your poor/good performance.
Thank you very much for the feedback! Idea 1 was something I had in mind at some point, but developing that topic further would have been too much for my timeline. For what it's worth, the developers do gain a bit of experience over time in the current version. Idea 2 would be interesting to have as well, perhaps in a "Jones in the Fast Lane" kind of story at the end of each month.
I thought this was such a cool an unique take on dev work and it fits the them so well haha! I enjoyed playing it! It did take me a second to figure out everything, but afterwards it is a great time management style game! Good work!
The game is addicting, if I had more time I would keep playing, 3 years is enough for me, developers always quitting! haha, overall pretty fun and cool to look at, even if its just a table, also, weird "game" since its like work, great work dude!
Glad you enjoyed
working at my fictional companyplaying my game!Of course one person gotta have a multiple hats!! I laughed a lot by playing this game (especially when dev ops asked some help) - it's about a real world but very entertaining for some reason XD It's also interesting to see me delegating lots of tasks and then getting lots of bugs and then assigning all myself makes me realize inner self somewhat. The graphics are simple and to the point, the tutorial is easy to understand. Overall great work!
"Interesting" game.. feels like work, yet somehow fun! I didn't quite understand the peer review part though, not sure if assigning someone else to review it affected the points, although sometimes a bug icon appeared, and I didn't know what to do after that
So, the idea here is that assigning someone else (other than the one who wrote code for it) to review the task increases the chances of finding bugs. Once found, you'd need to move the task back to "In progress" to fix them, otherwise they'll just enter production anyway!
Thank you for playing!