You are currently browsing the archives for the Meeting category


February 2012 – Coding Golf

Details 

Golf Balls

Golf Balls by walknboston

Date: Tuesday 28th February 2012

Time: 7:15pm start to 9:15pm .

Location: http://themorrismanpub.co.uk
Google Maps: http://g.co/maps/ptzt5

Theme: Practical Session

New Venue

Please note the new venue. It’s our first meeting at The Morrisman. Follow the links above for further information.

When I called in, the menu and food being served looked excellent. The beer was pretty good too.

Coding Golf

Shaun Finglas has kindly offered to run this months session. His proposal email was as follows:

My proposal is simply Code Golf. We’ll spend an hour (ish) solving a fairly trivial problem in the style of a kata as normal. The twist is you must then refactor your code to an extreme level so that you can solve the problem in the least amount of characters possible.

Rules:
– The code must compile/execute
– You can use any language you want as long as you can accept user input/display output – think simple console application
– The code must implement the required functionality

The challenge will be revealed on the night so there is no prerequisites apart from laptops. The more laptops we have the better. People can work solo/pair if they want but as long as we have enough machines we should be fine.

“Golfing” real life production code is not something you would want to do, but I’ve found Code Golf challenges very fun, and they show just what sort of merciless refactoring you can do once you have a good suite of tests to back you up. These sort of challenges are incredibly hard without a good suite of tests, so you can often win over people who maybe do not see the value in unit testing production code.

Lightning Talks

As yet (usual!) their are no volunteers for a lightning talk. If you have any topic you’d like to share with the group then you can have a 10 minute slot at the beginning of the meeting. Please email the group or mention it at the venue before we start.

Hope to see you there,
Neil Kidd

January 2012 Meeting – Space Invaders vs Continuous Testing

Details 
What it should look like with no glare [1680x1050]

What it should look like with no glare by DUCKofD3ATH

Date: Tuesday 24th January 2012

Time: 7:15pm start to 9:15pm (doors open at 6:30pm).

Location: http://www.pieandale.com

Theme: Practical Session

Space Invaders vs Continuous Testing

Paul Williams will be running this session, that he first took part in at the Software Craftsmanship Conference in 2011. Paul has since gone on to run this session at his place work, so he now has a fair bit of experience with it!  To minimise possible complications, we intend that the server will be run locally and connected to a wireless access point.

The description shamelessly taken from the original session description is (my emphasis):

A fun coding challenge to find the fastest way to develop reliable software, between: * Manual testing * TDD * Continuous testing. Participants will write code to defend earth from alien invasion. Score will be accumulated over 60 minutes depending on how many cities are successfully defended. Participants will be split into 3 groups, each representing a different testing practice. Scores will be averaged between the groups at the end of the session to determine some interesting statistics.

This session is for .NET developers only. Participants who wish to operate in the TDD group must have a manual test runner available on their machine that can run NUnit tests. Participants who wish to try out continuous testing are recommended to first try NCrunch on their machine ( www.ncrunch.net ) – though there will also be some setup time at the beginning of the session for those unfamiliar with this tool. Visual Studio 2010 will be used along with .NET v4.0. A downloadable solution will be made available at the beginning of the session containing the code and instructions needed to get started.

 

Lightning Talks

As yet their are no volunteers for a lightning talk. If you have any topic you’d like to share with the group then you can have a 10 minute slot at the beginning of the meeting. Please email the group or mention it at the venue before we start.

See you there.

September Meeting: Systems Thinking Games

Details

Date: Thursday 29th September

Time: 7:15pm start to a 9:15pm (doors open at 6:30pm and close when the games have finished).

Location: http://www.pieandale.com

Theme: Systems Thinking

Systems Thinking

Following the excellent talks from Kevin Rutherford and Harriet Shannon in June we’re continuing to think about how teams and environments can be improved by considering how things influence one another as part of a whole. The practice concentrates on viewing complex problems as larger systems rather than focussing on the individual components out of context. It’s all about relationships, philosophy and common sense – much like the topics we’ve covered already at Agile Staffs. The topic is vast and is best discovered over time, rather than via my bumbling summary here. There are plenty of online resources and even a user group in Sheffield. We’ve covered some aspects before (Theory of Constraints, Lean) so this meeting should give us all a good understanding of the basics, giving us the opportunity to go away and learn more.

Playing Games with Ash

Our speaker for the evening will be Ash Moran, a software developer, agile coach and user group regular from Stoke-on-Trent. He provides advice and training on these matters too through his company Patch Space. He is an ex-colleague of a few group members and we’ve been planning on having him pay us a visit for some time. I’m not entirely sure what his plans for the meeting are but I know they are going to involve some games. These will likely be in the form of interactive exercises to illustrate the various concepts, much like the dice game exercise we did with Kevin. I’ll update this when I know more, or I might just leave it as a surprise…

Bring Your Friends

As the meeting will have a less technical theme than recently it is a great opportunity to bring new members, bring your boss, or even your non-computery friends as Systems Thinking has been widely used in all manner of contexts. By the sounds of some of the games (Ash asked me how much room we’d have!) we could do with as many people as possible too. Information for new members can be found on the New Members page.

 

July Meeting: Back to TDD with a Lean Code Challenge

Details 

Pineapple Bike by gipukan

Date: Monday 25th July

Time: 7:15pm start to a 9:15pm (doors open at 6:30pm and close late).

Location: http://www.pieandale.com

Theme: Back to TDD (with a Lean Code Challenge)

Back To TDD

Following the session on the Software Craftsmanship 2011 conference, and then a great session with two speakers, it makes sense to get back to some programming, and use some of the examples picked up at the software craftsmanship conference.

Test Driven Development enthusiast and Agile Staffs member, Paul Williams, has volunteered to run a session from Software Craftsmanship originally created by Chris Parsons. It involves the building of a small shop checkout application for a fruit seller that has to expand quickly to meet customer demand. The increasing complexity and high pressure features that will need to be added mean that test driven, clean code should help you out – no-one says you have to test drive and refactor though, the only requirement is to produce the features in time. As this is in a TDD session, and being run at Agile Staffs, it might be a clue which approach should yield the most successful project outcome, but we just don’t know.

As ever, there will be some developers experienced in test driven development around, and there will be lots of pairing going on, so don’t worry if you are unsure about TDD,  just ask.

Requirements

You’ll need your favourite development environment and the ability to write, run and unit test code. The “acceptance tests” of each stage involve typing in the fruit purchased to compare the expected price. Your application should have the ability to accept this input from STDIN, command line or a web interface. Other than that, you can use any language you like. We’ll have limited internet connectivity so please download anything you think you may need in advance. Again, for those PHP and JS types amongst us I’ll bring the licence code for PHPStorm so if you want to download and install the latest version in advance you can just register it at the meeting.

Lightning Talks

I’ve not had any volunteers for a lightning talk yet although this doesn’t mean we won’t have any. If you have any topic you’d like to share with the group then you can have a 10 minute slot at the beginning of the meeting. Either let me know via twitter, the email group or in the bar before we start.

 

June Meeting: Flow and F1 In Paediatric Intensive Care

Intensive Air Flow © Paul Shannon 2010

Details

Date: Thursday 30th June

Time: 7:15pm start to a 9:15pm (doors open at 6:30pm and close after last orders).

Location: http://www.pieandale.com

Theme: Flow and F1 In Paediatric Intensive Care

Guest Speakers

For the first time in a few months we have not one but two guest speakers (rather than members’ contributions). Our guests are both internationally renowned speakers and doctors of their respective professions.

Flow – Dr. Kevin Rutherford

Kevin’s experience in the software development industry and wealth of knowledge on the subject of Agile and related topics makes him the finest Agile Coach for miles around. He will be demonstrating the theory of constraints and the benefits of concentrating on batch sizes using a simple dice game. This great way of illustrating how agile methods can improve the flow of your value stream and make your work life easier and simpler is not one to miss. I’d recommend that everyone at your organisation should attend this talk as it has relevance in all areas of business, and is a great way to convince senior management that agile methods can work in your organisation.

F1 In Paediatric Intensive Care – Dr. Harriet Shannon

In 2005 Harriet took up a post as research physiotherapist at the UCL Institute of Child Health to investigate respiratory physiotherapy techniques in intensive care at Great Ormond Street Hospital for Children.  Harriet’s PhD work focussed on the safety and efficacy of on-call physiotherapy treatments in intensive care and she is now a primary tutor for the MSc Course in Advanced Physiotherapy at UCL.

Harriet’s talk, “F1 In Paediatric Intensive Care: Reducing Bottlenecks in Time Critical Environments”, comes from a partnership created at Great Ormond Street Hospital for Children between the intensive care teams and the pit crews of Formula One teams. Both environments require precision in preparation and planning with constant analysis of process speed and obstacles. The talk should give you a good insight into the observations and changes made in these time critical arenas, where a slow reaction could be a matter of life or death (and winning or losing).

Agile North

Following a successful presentation by Agile Staffs regulars Paul Shannon and Neil Kidd they managed to shamelessly plug the June meeting so it seems appropriate to point out the information for New Members to show any “North” converts everything they need to know to come and join in the Staffordshire Agile fun.

May Meeting: Software Craftsmanship

Bombe at Bletchley Park © Bletchley Park

Details

Date: Tuesday 31st May 2011.

Time: 7:15pm start to a 9:15pm (doors open at 6:30pm and close with the pub).

Location: http://www.pieandale.com

Theme: Software Craftsmanship Round-up

Software Craftsmanship

The analogy of software development as a medieval style craft will romanticise our profession but it also provides a keen set of principles that will ensure software produced today will be used and evolved well into the future. The movement has been popularised by the likes of Uncle Bob Martin, Corey Haines, and, particularly in the UK, Jason Gorman. It is Jason Gorman that organises the Software Craftsmanship conference at Bletchley Park which is the main European conference on software craftsmanship. The attendance is limited to around 120 participants and demand always outstrips supply. This year though Agile Staffordshire will be represented by 8 members –  4 of which also attended last year.

A call to action by Jason Gorman at the end of last year’s conference urged us all to go out and spread the word about high quality, well tested, communicative code in well designed and usable software. This, coupled with the upcoming conference and the release of Uncle Bob’s follow up to Clean Code: The Clean Coder: A Code of Conduct for Professional Programmers, means now is no better time to talk about software craftsmanship.

The Meeting

Software Craftsmanship 2011 is on Thursday 26th May and the plan for the Agile Staffordshire meeting the following week is to bring as much content and discussion as possible back up the M1 and across the A50 (and down the A34). This does mean that those involved will have to come up with something over the weekend so we don’t know yet what will be discussed. The programme for the day is available on the SC2011 web site so please take a look and let the group know what you’d like to know more about – some people already have which is great.

The format of SC2011 sessions are a mixture of programming, discussion and talks so we’ll probably have a mixture of topics at the meeting – bring a laptop as we’ll no doubt be writing some well crafted software.

I’ll not be organising this meeting from the end of this week as I’ll be on holiday. My able assistants Neil Kidd, Shaun Finglas and Paul Barrett are all on hand via the mailing list for any queries or suggestions.

March Meeting: TDD Exercise and Designing A University Course on Agile

Details

Date: Monday 28th March

Time: 7:00pm start to a 9:00pm (although doors open at 6:30pm and close when the beer’s gone)

Location: http://www.pieandale.com

Theme: TDD Exercise and Designing A University Course on Agile

Test Driven Development Exercise

Following feedback in the last meeting’s retrospective it was noticed that TDD is a central part of adopting a set of agile practices. Continuous integration, refactoring and high standards of code quality are all achieved more effectively with a suite of unit tests, and code that has been written test first. While some of these practices can be adopted without TDD it is a useful tool for anyone attempting to try a more agile approach to software development.

We’ll be undertaking a short exercise where we test drive a String Templater class based on a similar exercise performed as a prepared kata by Software Craftsmanship Journeyman, Corey Haines. Participants will need a laptop and the ability to write and compile/interpret/run code. This exercise will be language agnostic so you can choose the language you use every day, something you’re experimenting with or something completely new – the only thing you will need is a unit testing framework. A good list of xUnit based TDD frameworks can be found on http://en.wikipedia.org/wiki/List_of_unit_testing_frameworks

I use NUnit for C# which is very similar to JUnit for Java. PHPUnit is another similar framework but SimpleTest for PHP is also adequate. Ruby and Python are popular options but for ease of use you could use JSUnit or QUnit for JavaScript and just use a browser to run your tests. There are even TDD frameworks for database languages, functional languages and XSL.

We’re planning to take TDD from the beginning so please come along if you would like to learn some basic TDD. Also if you have experience and would like to help others to learn then come along too.

Designing A University Course on Agile

Trevor Adams, long time group member and university lecturer at Staffordshire University, will be preparing a discussion to focus on items that people working in software development think that universities could teach while also providing ideas for how this could be achieved. Hopefully this will explore the topic that has been a talking point at most meetings so far as the guys from the university are keen to get relevant agile content into their modules while local companies want graduates with agile experience. If you have ideas, experience or opinions then please drop in.

Retrospectives

At the February meeting we ended proceedings in a truly Agile manner by inspecting and adapting the way that the group and meetings were conducted through a Retrospective.

For those who found this useful and want to take this away and try it elsewhere then here is the format we used:

  • Give everyone some sticky notes, a pen and 5 minutes to consider the following two questions:
    • What have we done well?
    • What can we improve?
  • Invite everyone to write down as many points as they want, one per sticky note, that answer one of the two questions.
  • Place the two questions (or a 🙂 and 🙁 will suffice) as headings on a whiteboard, a wall, a chart, a table – anywhere that is visible and accessible
  • Invite everyone to stick their notes under the relevant heading.
  • Once everyone has had a fair chance (5 minutes) to stick their notes and think of any additional points then get everyone to sit down ready for the next step.
  • Group any related notes together to avoid duplication.
  • Invite everyone to take a pen and place a mark, dot, circle, tally or cross against the points they wish to talk about:
    • Each person gets 3 votes
    • They can vote for any of the notes, including their own
    • They can place their 3 votes on any note, with all 3 on one if they wish
    • Allow around 5 minutes for this activity
  • Once everyone has voted you should see an order to the points that people want to talk about – take the top 3 notes as the topics that will be discussed.
  • Spend the remainder of your timebox (we used 30mins but at Codeweavers we generally use 1 hours) discussing the 3 top points.
  • Appoint a chairperson to control the flow of conversation and to ensure everyone gets a fair chance to speak
  • Appoint a time keeper who ensure that the 15 minute timeboxes for each point are kept to – this isn’t strict but ensure the timebox is not abused.
  • Try to summarise discussion into actionable points – two or three per point should allow you to complete these actions before the next retrospective. Some things don’t have actions, just the discussion is enough.
  • When the timebox is up, the discussion comes to a close and no further points are discussed – if a point was not discussed this time, and it reoccurs for next time, it is likely that it will get discussed. Only points that the whole group deem important will be discussed so no one person will get to dictate the course of improvement.

Variations

  • If you find that you don’t have time for 3 points, try just 2, or try extended your timebox.
  • If you find you are not covering enough items then try taking the top 5 – be aware though, that your goal is to raise actionable points from the issues raised, so ensure you only cover what is likely to be actionable before the next meeting.
  • Don’t make the timebox too long as people lose concentration and other stakeholders think you are wasting time in meetings. Keeping the discussion focussed and producing action points mean that other stakeholders (managers etc) can see the results of the meeting, and if you follow up on the action points, they can see the improvements being made.
  • Give it a go, if it doesn’t work, have a retrospective retrospective – what went wrong, what can you improve, what went well? Change the format, ask on the google group for suggestions.

Tag Cloud