Sprint 005 complete
This post feels weird to write.
My original vision for Sprint 005 was to release a v2 demo of the new Sex Engine scene. I failed; only a section of it is complete.
Historically, what I'd do at this point is extend Sprint 005 until the objective is achieved. And then operate in a crisis mentality, postponing all non-005 tasks until it got done.
But, as you know, I'm trying to manage myself and the project better, in an effort to get better results. So I'm sticking to the timings. Sprint 005 is complete, even though I didn't accomplish all I'd hoped; I put a dev version of the completed section to Operators+, and am waiting for feedback.
Basically...I've finally realised the solution isn't extend Sprint 5 to Infinity. It's come up with a good Sprint 6.
This has been a highly challenging fortnight for me, with big implications for real changes in the way the game's developed. I've got a lot to say, but I'm tired: tomorrow I'll post a reflection on Sprint 005, and outline my plan for Sprint 006 (starting Monday 20th). Thanks for sticking with me, guys, expect some detail tomorrow. See you then!
Comments (6)
Okay, now that there's a more recent post for on-topic stuff, I'll add this comment to this one: I really want to take that girl by the hand, help her undress and shower, wash her hair for her and towel her dry.<br><br>There. I said it. I hope you can all still respect me, despite these wholesome thoughts.
Congratulations on not extending the sprint, which is definitely not how things should be done. You have to build up experience pointing your tasks and discovering what your real velocity is, which takes a few months to settle into.
One of the key premises of any "agile" approach is that any interesting project involves discovering things (about what you really want the app to do, about how to get it to do it, etc.) that you wish you knew before you started. This way you're never more than one sprint length away from when you can stop, look at what you learned, and make whatever changes you need to around what you try next sprint, rather than spending 24 months trying to save an 18 month plan you're contractually committed to. That isn't always as satisfying as hitting a planned sprint deliverable, but it's a feature, not a bug, really. And completely normal (*especially* early in the process while a lot is shaking out for the first time).
For your sprints, try not to have large goals. If you can break it down to a set of smaller features. That way you won't have failed, you will show progress. Also, breaking down to smaller features let's you get an idea of your velocity which helps you plan better in future sprints.
This ^^^
No worries craboutpost keep doing things as you see fit and you'll get there. It may take up to Sprint 100 but I'll follow you all the way.