Talk: Keeping Code Agile Workshop
Speakers directory
Speaker:
David Legge
Talk description
Title:
Keeping Code Agile Workshop
Short synopsis:
Ever asked for a new feature and the team suck their teeth because of the code that needs changing? Ever come across a legacy codebase where you fear to tread? Ever encountered that sinking feeling where a shiny new Greenfield codebase starts to feel less and less shiny new and more like a legacy one? This workshop will get you exploring what both Agile and Legacy Code look and feels like. We can then explore how you can tackle Legacy Code and how to get to Agile Code.
Max size: 500 chars
Long synopsis (optional):
Keeping Code Agile Workshop Abstract: Ever asked for a new feature and the team suck their teeth because of the code that needs changing? Ever come across a legacy codebase where you fear to tread? Ever encountered that sinking feeling where a shiny new Greenfield codebase starts to feel less and less shiny new and more like a legacy one? What we know we don’t like is Legacy Code, but what’s the opposite? Too many developers end up in Bracket Wars(TM) in the name of worshipping at the temple of a coding standard, Clean Code is an essential concept, but like test coverage could be overdone and for its own sake, so ‘Agile Code’ implies stuff that’s good to go, potentially shippable, and easy to change when required. This workshop will get you exploring what both Agile and Legacy Code look and feels like. We can then explore how you can tackle Legacy Code and how to get to Agile Code. Participants will be asked to identify definite aims for a week, a month and a years time. Details: This workshop encourages participants to think through how to avoid code becoming legacy code, and easily adaptable to new requirements and features. Time spent working in small groups will be maximised; Structure: A duration of 90 minutes is assumed. 5 mins - Introduction 5 mins - Form small groups, Icebreaking and Warmup 5 mins - Description and scene setting for 1st main group discussion 10 mins - Discuss 1st topic in groups 10 mins - Collate topics on wall/board & group similar 10 mins - Review grouped issues with all 5 mins - Scene setting for 2nd discussion 20 mins - 2nd Group discussion 10 mins - Groups report back to everyone on conclusions 10 mins - Conclusions and Wrap-up A brief description of each section: Introductory talk/discussion: An overview of the session will be given. Form groups, ice-breaking and then a warmup exercise: Firstly it needs to be ensured that the groups are not just groups of bezzies or colleagues, but a mix. Scene setting for first session This will set the scene for the session, briefly exploring is meant by ‘Agile Code’ as opposed to ‘Legacy Code’, also mentioning ‘Clean Code’ and ‘Good Code’. First session Each group will be given EITHER the problem OR the anti-problem, there might be a split between the two across the room, depending. The groups will be asked to discuss the qualities/aspects of code which make it ‘Agile’ or (the Anti-problem) ‘Legacy’ with the aim of producing a list to report back to the whole group. Issues written on post-its. Collate and Group Groups put all post-its up on a board and group. Report Back Groups report back to produce master list, linking common items with short discussion of each. Scene setting for 2nd discussion Having identified what we want to see in code, we need to identify how we are going to go about it. Equally importantly, how we get buy-in from others around who could undermine the efforts. 2nd Group Discussion Groups will stay with the same Problem or Anti-problem they had in the first session. Back in the same groups, participants will be asked how you might go about achieving Agile code, or the anti-problem, Legacy code, both as an individual, but also encouraging your team members to do the same. Report Back (2) Groups report back to produce master list, linking common items with short discussion of each. Conclusions & Wrap-up:Depending on time available, the lists can be summarised and tied/linked together. Ask if individuals will be taking on actions for their next day/week/month at work. Any observations from facilitating the session etc. At the end of the workshop participants should have some definite action points to take back to their teams and colleagues on how to both write and maintain better code. If time allows an aim for a week/a month and a year will be identified. Probable second presenter identified, but this bit is supposed to be anonymous I think.
Max size: 5000 chars
Tags:
Speaker directory:
Listed in directory
Not listed
Speakers directory