Skip to main content

Agile East Anglia: A Short History


December 2011 to June 2012

Agile East Anglia was started by Paul Grenyer as an Extreme Tuesday Club (xTc) inspired pub meet on Monday December 5th 2011 at the Coach and Horses on Thorpe Road in Norwich. Attended by a handful of people from local firm Aviva it was followed on Monday 9th January 2012 by  a less well attended meeting at the same place.

On a cold and snowy Monday 6th February, with sponsorship from Ipswich based consultancy firm Smart421, Agile East Anglia put on a presentation on Agile User Stories given by well known Agile consultant Rachel Davies at The Assembly House in Norwich. Around 20 people attended, predominantly from Aviva, but also people from other firms such as Archant, Smart421, Axon Active AG and Proxama.

On Monday March 26th Agile East Anglia put on a second Agile presentation, this time it was a Dialogue Sheets workshop given by Agile consultant Allan Kelly. Again it was at the Assembly House in Norwich and sponsored by Smart421. Around 20 people attended. This time there were more people from local East Anglian companies such as Ifftner (Ipswich), Redgate (Cambridge), Call Connection (Ipswich) and Purple Tuesday, as well as people from Archant, Smart421 and Axon Active AG.

On Tuesday 10th April Paul Grenyer presented The Walking Skeleton for the newly formed facebook group, Norwich Developers Community. The group was created and run by Stephen Pengilley to bring together Norwich’s software developers.

On Thursday April 19th Agile East Anglia regular John Fagan gave a presentation on the Lean Startup book for the Norwich Startups meetup group. The group was created and run by Juliana Meyer to bring entrepreneurs, developers, and anyone interested in startup companies in Norwich together. Starting in September 2011, Norwich Startups had already had a number of well attended meetings and was well established.

It was about this time that Paul Grenyer and John Fagan independently had the idea to bring all of the groups together with the aim of making something bigger and even better. Purple Tuesday co-founder, Seb Butcher had also expressed interest in getting involved with Agile East Anglia. Stephen Pengilley and Juliana Meyer were both approached with a view to merging Norwich Developer community and Norwich Startups with Agile East Anglia.

On Thursday 3rd May at the Gunton Arms near Cromer, Paul Grenyer, John Fagan, Seb Butcher, Juliana Meyer and Stephen Pengilley got together to discuss and shape the new group, which had the working title “On The Code City”.

On Thursday 7th June Agile East Anglia held a meeting at the Hog and Armour in Norwich. Nearly 30 people came to hear Agile consultant Liz Keogh speak about behavior Driven Development. Smart421 continued their sponsorship and there were attendees from Ifftner, Redgate, Call Connection, Purple Tuesday, Smart421, Axon Active AG and newcomers Silo18 (Norwich). During the introduction it was announced that Agile East Anglia would be merging with the Norwich Developers Community and Norwich Startups under the name “SyncNorwich”. Seb Butcher, Stephen Pengilley and John Fagan were introduced to the Agile East Anglia group and the date of the first SyncNorwich meeting was announced as 5th July, with a presentation from Colm McMullan on his one man startup.

With the formation of SyncNorwich, this became the last Agile East Anglia event. Future meetings had already been planned, including Lightning Talks, a presentation on Kanban from Benjamin Mitchell, a session on iteration planning from Simon Cromarty and a workshop on GIT from Pete Goodliffe. All of these sessions were adopted into the SyncNorwich programme.

In six months SyncNorwich has attracted 400 members and regularly gets in excess of 60 people to its events. The first SyncNorwich conference, SyncConf is set for 15th February 2013.

It's been quite a year.

Comments

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resources