Learning Points
- Introduction to Critical Reflection
- SMART Objectives
- Intro to Agile development
- Intro to Trello
- Personal Case Study video - accomplishments, Structure thoughts, Outline Practice, Propose way foward, Next steps
*****
Amazingly already four weeks into the course, and time for a look back across what’s been achieved, and where there are still battles to be won.
Various ways of doing this, some of which were outlined in the course material. Starting with SWOT analysis:
Strengths - It’s been a steep learning curve in many aspects, but also quite thought provoking. I think I find it still quite daunting, but remain fascinated by the subject matter of the course and determined to get as much out of it as possible. I think the key strength is that I am doing this because I want to. It’s not particularly because of the qualification at the end of it, but certainly for the skills it’ll encourage me to explore, and the roads down which they may lead.
Weaknesses - Certainly getting up to speed with the technical side of the course is a challenge - not because I find the concepts hard or the technology is hard to grasp - I have lost track of the number of audio editing, delivery and word processing systems I have mastered over time, but I know that I learn best which I am shown. Plus the uncertainty of my working life - week three was all but obliterated by a week of overnight shifts when my brain tends to switch off.
Opportunities - Having just grazed the surface of the subject, I realise how many spin-off skills I shall be learning over the course of two years (coding, content production, storyboarding, time and project management, collaborative skills, ideation), and how they will improve the commercial offer I already have. The aim is still very definately to come up with and develop interesting apps, but I think it’s important to enjoy the process along the way, explore the medium, don’t run too fast, and release my imagination.
Threats - Fear of the unknown. Fear of getting left behind. The clamour of work. Expecting too much from myself. Measuring myself against others.
Dispositional, Affective, Interpersonal, Cognitive and Procedural
Notes in brief, I’ve yet to find a way of ensuring study consistently. The variety of my work/home life must not be an excuse. I need to find a way that I can focus down on aspects of the learning. Till now it’s been somewhat of a scattergun approach to learning. Distance learning is tough. Webinars are great, but I miss the ability to cross check with other students. It’s a bit like language learning as an adult - the frustration comes from not being able to be capable immediately. This is still the baby-steps stage of learning about the subject.
SMART Plan of Action (Specific, Measurable, Achievable, Relevant, Timebound)
Fix a set time every day to work through the course, regardless of work or other distractions
Set a daily target for learning about coding
Reach out to other students at same level
Enjoy the course, take my time
Accept my lack of knowledge in certain areas, and not be afraid of asking for help.
*****
Reflections on Agile Practice
Agile Practice
Plenty of material on Lynda/LinkedIn Learning
https://www.linkedin.com/learning/agile-foundations/understanding-agile
These are overviews of Agile, basics for those starting from scratch. If it’s on LinkedIN, it’s probably been approved or quality controlled.
Checking on the Web, there’s a lot of material. I reckoned this would be authoritative:
Association for Project Management
https://www.apm.org.uk/resources/find-a-resource/agile-project-management/
Range of material in GDC Vault from the conference in 2010
https://www-gdcvault-com.ezproxy.falmouth.ac.uk/play/1012331/Agile-No-Silver
Various speakers discussing the good and bad aspects of Agile development. Also includes a Q&A session.
Content
It’s a framework, not a methodology. Iterative framework. Adjusting how you are building. Apply practices where they are needed. No rules. Shared practices. Avoid project crunch. Scope, Cost and Schedule balance. All three can’t be nailed down. Product backlog is the easiest to control. Monitor schedule and cost.
Application in App Jam
I think I was moving along in jumps – ideation, working out the mechanics, prototyping, gaining feedback, adjusting prototype. I was unsure how much of the initial idea would make it into the final cut. Also, I was open to adding and taking away features. Clearly in a real situation there would be many more iterations, once you get beyond the prototype, once the technical practicalities are approached.