Sean Moir has over 18 years of industry experience as Software Engineer, much of it with additional mentoring and knowledge share components.
Over the last 2½ years, he identified the need for, and introduced Agile to a team of Engineers developing Wickes (DIY) Store Systems for Travis Perkins PLC. In this role, he coached Product Owners and Team members on SCRUM roles, principles, process and practices. He also acted as Scrum Master through the planning of around 20, three week iterations.
Most recently he has set up as a freelance practitioner so that he can have more experiences in Agile Coaching and provide guidance for others during their transition.
Travis Perkins PLC, Senior Software Engineer, Agile Coach, Scrum Master
December 2010 - March 2013, Swindon, Wiltshire, United Kingdom
I accepted the challenge of joining a recently formed, chaotic Development team.
The team had been creating a replacement Back Office system, some web services which allowed communications with Travis Perkins HQ, and supporting other legacy systems such as the Wickes till.
I had previously been introduced to some of the concepts of Agile at a DSDM conference in 2006 and had since liked the idea of timeboxing prioritised work items.
In this role, I read up further on Agile and it became clear that lots of the XP practices I'd heard about support the management style of Scrum. Eureka! I persuaded my Project Manager that Scrum might help to solve some of the issues which we were facing.
With the Project Manager initially acting as Product Owner, he created a Product Backlog after some guidance from me. I took on the ScrumMaster and Scrum Coach roles. I introduced the team to Scrum and they were mostly keen to try it. There was naturally some resistance to the ways of working since some of them seem counter intuitive - particularly TDD and Pair Programming. Through some theory sessions, Kata exercises, and by working through real life issues with the team, they gradually felt more confident and more convinced that this was indeed an improved way of operating.
Skills which I introduced;
Consistent use of Source Control
SOLID Design Principles
Increased use of abstract interfaces to allow loose coupling
Use of programming patterns
Mechanism for all new functionality to be switchable on/off
Working towards Build Automation - large amount of technical debt in this area for VB6
Consistent Rollout/Rollback procedures
Later on the team started BDD as well using FitNesse