A retrospective about myself, what went “good,” “not good,” and what to improve: usually, on my teams, we started with those questions. Sometimes we review all tasks, trying to figure out any conclusion of how the thing went. If everything was fine, we asked why and mostly what could be improved. The bad things are easily spotted, and the feeling is easily shared.
I’ve already used the Start, Stop, Continue model (‘Start Stop Continue Retrospective, Retrospective Template’, no date), but I also tried:
- The 4 Ls: Liked, lacked, learned, longed-for.
- Glad, sad, mad
- The sailboat method
In the game industry, I identified some different aspects of adoption (Godoy and Barbosa, 2010). I believe it is natural and part of the process and natural ways to overcome the most common problems in the adoption (Lopez-Martinez et al., 2016).
But when applied to a personal aspect of this self-evaluation, I have less experience, and it became a blur scenario for me. I followed the recommended Start, Stop, Continue technique to do my review and also pointed out the critical aspects from the Reflective Domains as described on Week 5 post.
- To start
- Review more, and write a progress summary into my journal;
- Follow the plan;
- Have a better vision of priorities;
- I need to have a better view of my daily, weekly, sprint priorities;
- To stop
- Work alone, I need to learn how to work better with peers;
- Find a better strategy for my time-management. Pomodoros didn’t work very well, and because of that, I’m switching to a 2hours time box;
- Don’t leave all the articles for the last moment. (yeah, I have a lot to improve here 😦 )
- To continue
- Continue to use SMART goals.
- Learning and reading a part of the main activities
The reflection domains still influence me. And I think they will be part of my self-evaluation for some time now. (This is something that I want to internalize.)
Progress on prototype session
I’ve been working on this on all my disposable time. I finished my concepts and spent a lot of time learning about clouds and shaders and how to do them in Unity, I found that this would be easier, but I was profoundly wrong.
I decided to do a flying simulation “game” to have a flying boat that will navigate the clouds to grab some boxes. I ignored the arithmetic part of the game and focused on the technical aspects.
At the end I missed the focus on the game play but was able to publish it at: https://lbs.itch.io/skyboat
Struggles and achievements
My available time continues to be a constraint, and for some days, and my son will be at home for some days. Some of the teachers got COVID, and the maternal was closed. It will reduce my time dramatically.
I’m feeling some difficulty coding in Unity and C#. I don’t know about the internal API, and I’m spending much time reviewing and trying to make the code work. It makes it even more important to spare some time and learn some of the prototype tools.
But to good work in something, it’s been nice. I feel capable of continuing to pursue my goals and want to test many other ideas. However, I miss some structured knowledge about game design. From the academic perspective I’m reading more papers then just sites and videos. It’s been an interesting experience.
Godoy, A. and Barbosa, E. F. (2010) ‘Game-Scrum: An Approach to Agile Game Development’, p. 4.
Lopez-Martinez, J. et al. (2016) ‘Problems in the Adoption of Agile-Scrum Methodologies: A Systematic Literature Review’, in 2016 4th International Conference in Software Engineering Research and Innovation (CONISOFT). 2016 4th International Conference in Software Engineering Research and Innovation (CONISOFT), Puebla, Mexico: IEEE, pp. 141–148. doi: 10.1109/CONISOFT.2016.30.
‘Start Stop Continue Retrospective, Retrospective Template’ (no date) GroupMap. Available at: https://www.groupmap.com/portfolio/start-stop-continue-retrospective/ (Accessed: 3 January 2021).