During week 4 we were tasked with exploring agile development practice in order to promote greater creativity, flexibility and an iterative process. Using the university resources I have picked two sources that I found very interesting and will be looking to supplement my future practice with.
User-centered agile method by Dominique Deuff and Mathilde Cosquer
Published by Hoboken, N.J. : ISTE Ltd/John Wiley and Sons Inc., 2013.
Found: Library.fxplus.ac.uk
Published in 2013 this book analyses 10 years of work focussed on this ‘people first’ agile method.
Looking at combing two different methodologies; user-centred methods from industrial design and agile methods from software development. Mutually integrating these two processes into one methodology combines the project management and adaptability from software development with the user knowledge and testing from industrial design. The framework created brings in practical examples of how to implement the methodology and case studies of projects in which it has been used.
Creating a development culture that embraces change by Connor Crowley
GDC 18; Moscone Center San Francisco
This talk looks into the fluid and changeable manner of the market in which game developers operate in. New technologies, methods of consumption and trends make for a very unstable and constantly evolving market. This is equally true with other areas of app development where iterations and evolution is key. Crowley talks about how Jagex has adapted its team structure, processes and tools to keep Runescape surviving and thriving over 16 years.
Flexibility and adaptability helps them to change with, and ahead of, the market. Describing his method to promote a culture of change Crowley focussed on the ‘scrum’ pillars; transparency, inspection and adaptation as ways he promoted this mindset. Key take aways from his talk were that improvement is not immediate, use the pillars above to support change, smaller teams help to keep the iterations short and distributed decision making allow space for experimentation and growth. Finally he states that change isn’t a process but a behaviour which sums up his talk really well and the changes that he suggests implementing to be adaptable to change.
My practice
During my app jam I applied a design method I have used in the past; the double diamond method. I thought the 4 sections and checkpoints would keep me on track throughout this short project. Sticking to the design method too rigidly, as I did at the start meant that I could not be as spontaneous and flexible as I would have wanted. I found out that keeping to the timings too closely does not work for app jams where rapid development of concepts is needed. A more agile and instinctive approach is needed rather than the more methodical approach that I applied. One method I highlighted design sprints pioneered by Google ventures. These 5 day projects have been used to solve problems and create prototypes rapidly. I have started reading Sprint by Jake Knapp in order to greater understand how this process works and what key parts I can use during this module and future projects.
Researching agile practices has been valuable to expanding my knowledge of methodologies, processes and ways to design and develop apps. Having a large resource of methods, mindsets and activities to promote agile thinking will allow me to pick and choose for each project. The Design Sprints, Scrum method and the User-centred agile process highlighted are just a few ways to promote and iterative and experimental development process in future projects.
