News


Motivation and Craftsmanship

posted 2 Dec 2014, 14:56 by Neil McLaughlin   [ updated 8 Dec 2014, 15:30 by Royd Brayshay ]

Neil McLaunghlin at Agile Yorkshire
"What motivates you to get out of bed and leave for work in the morning?" asked Agile Yorkshire stalwart Neil McLaughlin at this November's meet-up. We agreed we'd all like our work to be challenging, fun and ...lucrative, but even with all of these things, how does one stay motivated?

It might seem that our desire to enjoy work would be at odds with the running of an efficient business, but Neil reminded us that even Frederick Taylor's carrot and stick approach to getting the most out of his workforce recognised that having breaks from work improved the overall throughput of his operation. As Neil told us, while the carrot and stick of yesteryear may have been superseded by butternut squash and lightsaber, it remains of benefit to businesses to find ways to keep its workforce motivated.

As a salient example of the will of the people with their hobbies and aspirations for autonomy, mastery and purpose triumphing in the face of big business with a 'too big to fail' mentality, Neil brought up the success of Wikipedia in the world of digital encyclopaedias. For many, Encarta pre-dated their experience with the internet. How could Wikipedia, with its articles written by volunteers and lack of marketing ever compete with Encarta? But it did, and open-source projects continue to win out against traditional business models over and over again.

Continuing on the theme of self-reflection, Kev McCabe joined us to speak on the theme of Software Craftsmanship, a topic in which he is particularly inspired by Sandro Mancuso. It's not like people wake up each morning thinking "today, I'm going to do a bad job", reckons Kev, but as pressure to speed up software delivery increases, he has observed that the standard of software delivered often slips. It makes sense that as code quality decreases, it takes longer to develop new features, as developers are no longer working with a system that has been designed with extensibility in mind.

Kev McCabe at Agile YorkshireThe Agile Manifesto calls for 'working software' -- but what qualifies as 'working'?, Kev asks. Why should someone feel they have to say "I've done it and it's working"? Should these two facts not be synonymous? and where did the phrase 'Technical Debt Backlog' come from? Whilst such a thing is blithely accepted, it feels like working software and mastery of the craft of writing software are becoming increasingly difficult to attain.

It can be challenging to improve at our craft when we're not expected to practise in work time, Kev admits. He advocates an approach of learning in small chunks, but often; stopping to ask questions; voicing your frustrations and not being miserable and negative -- you can always leave! Show everyone around you that you're happy and it should benefit everyone on your team.

Kev personally advocates following XP practices. He also advised that when dividing up tasks amongst a team of developers, one should allocate work to people with the fewest skills first in order to avoid a situation where some of members of the team are left with nothing they can work on. We also learnt that some of his top coding gripes are poor naming choices and the lack of deletion of stale code!

As a parting thought, Kev left us with this: Software Craftmanship and Agile in isolation will fail, we need both to succeed.

The evening ended with the monthly prize draw and drinks in the Midnight Bell. Thanks to all our volunteer team who make the event happen and finally thanks to main sponsors iSource IT, Piksel, Callcredit and NewRedo and to our prize sponsors O'Reilly, JetBRAINS, Manning, Wrox and PluralSight.

Write up: Eleanor Chambers

Call for 9th December 2014 Lightning Talks

posted 12 Nov 2014, 00:19 by Neil McLaughlin   [ updated 30 Nov 2014, 11:31 by Royd Brayshay ]




Its an Agile Yorkshire  Xmas tradition to look within our members for the December meetup content and stage an evening of fun and Lightning Talks


CLOSING FRIDAY 28th NOVEMBER

Even if you only have the vaguest of ideas, now is the time to start your career as a speaker. If you're not sure what you’re letting your self in for this may help. A ten minute Lightning Talk for Agile Yorkshire's December 2014 meetup should:
  • Probably have a maximum of four slides (maybe none).
  • Be on a topic you already know quite well.
  • Be interesting to our audience but could be about pretty much anything.
  • Be possible to completely script (if that’s your style).
  • Not be a second more than ten minutes.
  • Win you a SIGNIFICANT prize on the night if you put your mind to it.
Even if all you have is the vaguest idea, sign up now and we'll help you bring it to life. If you have multiple ideas and aren't sure which to use, that's fine we'll help you pick the right one.

Just a flavour of some of the topics submitted so far:
  • Omnisharp, developing .NET code without Visual Studio
  • Finding a School - Code vs MumsNet
  • Build an Interpreter in 24 Hours!
  • How cars work
  • 10 simple ways to help your team run like clockwork 
  • How To Write Bad Code
  • Agile and Knowledge Management: A match made in heaven, or hell on earth?
  • Success in business is short-sighted
  • ScrumBan vs Sprint

Also did we mention there will be significant speaker prizes on the night.

Incitement to murderous deeds and the throttling of flow

posted 3 Nov 2014, 15:09 by Neil McLaughlin   [ updated 3 Dec 2014, 02:35 by Royd Brayshay ]


The much abused term DevOps was the theme of the main presentation of the evening. Like Agile, DevOps seems to be an overloaded term appropriated to mean, variously, automation, system administration, build & deploy. Mathew, sporting a fantastic self made t-shirt emblazoned with the rallying cry "Death To The DevOps Team" proposed a more useful definition along the lines of "Highly effective, daily collaboration between software developers and IT operations people to produce relevant, working systems". He would also aspire to spread the collaboration net wider than just software developers to include QA/Testing, IT Service Desk, Programme Management, Commercial, Marketing. Tools were recognised as an an important facilitator (and sometime inhibitor) for collaboration. For example, Mathew proposed that the primary benefit of git was improved collaboration and, as such, all the artefacts of build and deployment should be made transparent using version control systems. Much of the presentation was taken up with descriptions of patterns and anti-patterns which emerge when organisation aim to achieve the hoped for benefits of the DevOps movement. From the "DevOps Team" anti-pattern of the title to the sublime "Smooth Collaboration" pattern via the "we don't need no ops team" anti-pattern dead end. There was also an interesting description of a variation of the ball point game popular with agile teams which had been adapted to show the effects of multiple teams on delivery of value. 


This tied in nicely with Steve Carter who filled the support slot with a presentation which discussed his attempts at grassroots agile adoption and his discovery of the principles of flow as described in the seminal book The Principles of Product Development Flow by Donald Reinertsen. After a high level view of the main concepts of flow (
variability, queues, utilisation, batch size, WIP, feedback and cross-functional synchronisation) Steve gave an entertaining run through of the things which Big Dumb Organisation's (BDO's) do to break the principles of flow which underpin agile practices. For example, making the product backlog a big queue (which is bad in flow) by committing to everything in the backlog. Steve's slides and transcript are available here and are well worth a read.

Slide links
Mathew has kindly offered a discount on his LeanPub book 'Build Quality In' book on DevOps & Continuous Delivery for Agile Yorkshire folk here as well as a 15% discount on the upcoming 'Effective DevOps for Leaders' seminar (use code 'AGILEYORKS') here.

As always our thanks go to the helpers and sponsors without whom the evenings would not be possible. After meeting beers were kindly provided by Matthew Wood of ISourceIT. Thanks to all our volunteer team who make the event happen and finally thanks to other main sponsors PikselCallcredit and NewRedo and to our prize sponsors O'ReillyJetBRAINSManningWrox and PluralSight.

The great photos are courtesy of @relentlessdev

Open spaces open minds

posted 1 Oct 2014, 00:57 by Neil McLaughlin   [ updated 3 Dec 2014, 02:32 by Royd Brayshay ]

Agile Yorkshire Open Space
September's Agile Yorkshire ditched the usual talks in favour of an 'Open Spaces' style gathering. The Open Spaces format gives those in attendance the opportunity to air their views on the topics that matter to them, with this month's theme being 'Organisational Culture'.
 
The first stage of the process was an invitation to submit proposals for topics of discussion. The board quickly filled with potential ideas, some of which needed a bit more elaboration than others! The topic owners gave us a brief overview of their idea, enabling us to group several of the proposals together where we saw enough commonality between them. Everyone was given three votes, and after a session of dot voting it was clear what people most wanted to talk about. Some of the winning topics were (roughly): 'Do we need managers?', 'Are all company cultures the same?' and 'Does agile work for predicting project costs/time-scales?’

The discussions were held in three sessions running concurrently in three rooms, with participants free to move about the rooms at will. Each session was hosted by the person who had proposed the talk, which elicited a few sad faces as the hosts realised they might not be able to join in with all the other conversations that they had been interested in.
 
Whilst the plan had been to run nine sessions in total (one at a time in each of the three rooms) we only ended up having time for two sessions per room, such was the level of lively discussion. There were some passionate voices to be heard and not everyone was always in agreement. Nonetheless, common threads were noted down in an attempt to address the issues at hand, and everyone seemed to enjoy the process.

Agile Yorkshire Open Space Meeting
We came back together at the end to reflect on the conversations that had been had and give everyone a chance to hear what had gone on in the sessions that they had been unable to attend. It was definitely interesting and informative to see what our community thought on different subjects -- a successful Open Spaces event for Agile Yorkshire.

The evening ended with the monthly prize draw and drinks in the Midnight Bell. Thanks to all our volunteer team who make the event happen and finally thanks to main sponsors iSource ITPikselCallcredit and NewRedo and to our prize sponsors O'ReillyJetBRAINSManningWrox and PluralSight.

Write up by Eleanor Chambers and Krystan Honour  

Pair presentation on pairing in software delivery teams plus the pared down framework - Nancy

posted 20 Aug 2014, 15:40 by Neil McLaughlin   [ updated 3 Dec 2014, 02:39 by Royd Brayshay ]

The main slot of the evening was delivered by Georgie Mannion and Kev McCabe as a business analyst and developer duet in perfect harmony singing the praises of cross discipline, and mixed skill level, pairing. They were drawing from their experiences of implementing mandatory pairing across the whole software delivery team starting on the first day of the new year after some radical 
New Years Day desk restructuring.

Rather than simply encouraging team members to pair when they could they adopted a 3 month period where nearly all activities across the software delivery team were carried out by pairs. There was plenty of discussion during the presentation about the various permutations and strategies adopted to ensure success. Although traditional XP pairing (two people working together with a single computer to solve a problem) was tried, so too were other techniques such as side by side pairing (two people working alongside each other to solve a problem by partition, XP style pairing and frequent close communication) and mob programming (single room, big screen, shared computers with representatives from several disciplines working closely to solve a problem).

The benefits of shorter feedback loops and better quality collaboration were stressed over email ping-pong or large meetings. The business benefit of the experiment was improved knowledge transfer in an environment with a high proportion of contractor staff. There was discussion of an interesting metric in the form of a matrix of skills and knowledge levels by team member and a drive to use pairing to reduce 'skill silo' risks. The experience levels of the participants making up a pair was felt to give different benefits; from exploration in novice-novice pairs through “up-skilling” in expert-average pairs through to crackling productivity in expert-expert pairs. The diversity of perspective was felt to be a particular benefit when pairing across disciplines with the cost of hand-offs between activities reduced.

As Gwen Diagram pointed out at the July meet up the tools an agile team chooses can impact on their ability to shorten feedback loops and increase confidence in making change. Anyone who has had to work with large enterprise tools (looking at you Oracle and Microsoft) will know how hard it is to deploy and test systems using them. Lightweight frameworks from the open source community have been a response to this and Nancy in .NET, along with it's cool Ruby cousin Sinatra, are two such frameworks. Matt McLoughlin gave us a whistle stop tour of some of the features of Nancy such as the conciseness of the resulting code, the fact that testing is a first class citizen of the framework, the simplicity of convention over configuration. All this is summed up by the goal of the Nancy team - keeping to the Super Duper Happy Path. As an agile developer I was encouraged by the idea that the Nancy community is friendly and responsive - qualities we often do not consider when selecting technologies but perhaps we should. Another plus would be Nancy's relaxed attitude to it's friends - want to use ASP.NET MVC and Nancy in the same solution, no problem, thus avoiding the common situation of having to decide which gang you are in and then having to stick with that decision come hell or high maintenance costs.

Write-up by Neil McLaughlin

As always thanks to our sponsors and helpers for their support iSource IT, Piksel, Callcredit and NewRedo and to our prize sponsors O'Reilly, JetBRAINS, Manning, Wrox and PluralSight - the evenings would not be possible without them.

An antipodean evening with David Evans and Gwen Diagram

posted 1 Aug 2014, 04:14 by Neil McLaughlin   [ updated 3 Dec 2014, 02:44 by Royd Brayshay ]

David Evans who, along with his partners at Neuri Consulting including Gojko Adzic, are blazing the trail in the world of Specification by Example (SBE) made some specific commitments at the start of his presentation to improve the artefacts coming out of the SBE process. These artefacts are examples which are in turn tests. He showed us how even when following the guide lines for good examples such as avoiding technical terms, using a formal notation like given/when/then and involving business stakeholders it can still fall short of the mark for a good example by hiding the essence of the business rule in a thicket of superfluous detail. This failure typically comes from having the example focusing on how to test rather than what to test.

In a nice slide (full slides available here) which neatly summarised for me how SBE artefacts are more than just tests - they are specifications, tests and living documentation. It also gave a way of thinking about their evolution over their lifetime: SBE artefacts should provide specifications now, regression tests soon and documentation later. He also contrasted the long lived nature of specifications versus the short lived (burn it!) nature of a user story.

Working through a number of examples of bad examples (see what I did there!) David brought out the desired qualities for artefacts of Focus, Balance and Contrast and why we should aim for hour-glass shaped scenarios with consistent levels of abstraction. Interestingly these are desirable qualities in all tests not just those of SBE.

In an interesting segment on the often debated topic of whether tests slow down development David made the pithy observation that tests slow down development in the same way that passengers slow down a bus. The speed of the bus (along with the speed of development) is not the point!

The final related segment addressed what will move organisations towards investing more in building a body of tests to support software making comparisons to with the costs of oil exploration. At this point in time the cost of tests is perceived to be high but as organisations start to realise additional value from tests either earlier in the software delivery life-cycle in the form of specifications or later in the form of live documentation then the value of the artefacts to an organisation increases and makes it more likely that time will be invested in building them.

The other half of the antipodean (dynamic) duo presenting on the evening was Gwen Diagram who gave a passionate presentation describing her journey to enlightenment from behind the waterfall into the world of multifunctional teams, close collaboration across the software delivery disciplines and high levels of tester autonomy. She stressed the need for testers to be able to chose their own tools and to not be afraid to ditch tools when they are no longer adding value. There was a lively debate on the issue of whether the testers in a team should all be technical and the need for developers to draw on testers experience and testers to pull in developers to help with test automation.


The lively discussions carried on afterwards in the pub (beers kindly sponsored by Sean Addy of iSourceIT) with both speakers present and actively engaged in the debates   

The evening ended with the monthly prize draw and drinks in the Midnight Bell. Thanks to all our volunteer team who make the event happen and finally thanks to main sponsors iSource IT, Piksel, Callcredit and NewRedo and to our prize sponsors O'Reilly, JetBRAINS, Manning, Wrox and PluralSight.

See you in August

The Agile Yorkshire Team

Nick McKenna disputes the existence of Agile and Craig Norton live codes in AngularJS

posted 29 Jun 2014, 14:30 by Neil McLaughlin   [ updated 3 Dec 2014, 02:46 by Royd Brayshay ]

"There is no Agile"? A bold statement to make to a group that meets under the name of Agile Yorkshire. Nick McKenna was the main speaker at this month's meetup, sharing with us some of his experiences as a Scrum Coach/Master/Professional. "There is no Agile" becomes an even bolder statement when it is being made by someone whose career is so obviously entrenched in the stuff. The point being made was that the label of 'Agile' does not necessarily mean an organization, project or even person is going to demonstrate the qualities one might expect of something 'Agile'. Nick told us that he had met plenty of Agile teams that don't question why something is done beyond saying 'because that's what we do in DSDM/Scrum...'. Perhaps a 'by the book' style is not right for every team, Nick pondered, showing us of some Agile tools he'd invented for himself which just happened to revolve around delicious, rewarding cups of coffee.

Focusing on Scrum in particular, Nick questions the value of sprints. The fact that a team may only evaluate their productivity once every couple weeks can be very limiting and result in sizeable chunks of work that gets scrapped, which in turn could lead to an unhappy team -- another thing Nick has been saddened to see. To combat team malaise, Nick recommends TINYpulse, a system for collecting anonymous feedback on the mood of a team via short, snappy surveys.

As a long term observation, Nick has also noticed that the velocity of Agile teams is generally on a downward trend. Another side-effect of time-boxed work, perhaps? An Agile regime can be relentless and draining, with few diversions and little opportunity to branch out and be creative. Nick's cure? Football stickers. Or whatever works for your team, but Nick reckons that a successful Agile team takes time out from work to celebrate their successes as well as regularly considering their shortcomings.

This month's support speaker was Craig Norton who gave us an introduction to Angular JS, an MV* framework used for building single page applications (SPAs). His half hour coding demo saw the construction of a 'ToDo' application based on the Angular-Seed project. A complaint often made about JavaScript projects in relation to their codebases is a lack of structure, with code that is difficult to read and difficult to maintain. Craig gave us a tour of some of the constructs Angular presents that are designed to add some of this desirable code structure. One such construct is a 'directive', which allows particular behaviours to be applied to a given DOM element. Whilst the behaviour of making the elements of your web page repeatedly appear and disappear (as jokingly shown by Craig) may not be the most useful application of this, it was a powerful demonstration of the speed with which one can develop a reusable function of this sort in Angular, and how cleanly it fits into the page markup, with its intention clear to developers and designers alike.

The concept of dependency injection pervades the framework's structure, which was designed with testability in mind. Craig showed us how he could run Jasmine tests against different components of his Angular application through Karma, the JavaScript test runner, which is a setup that comes as part of the Angular-Seed project itself. The decoupled nature of the different components of an Angular application that makes them so testable also eases the parallelisation of development work, which is a clear draw for bigger JavaScript projects.

So, maintainable, readable, testable code -- what's not to like? Well, as Craig points out, the latest version of Angular only works in IE9 onwards and of course, being a JavaScript framework, you definitely need your end user's browser to be able to run JavaScript for any of this to work. Not showstoppers for a lot of projects but certainly worth remembering.

Write-up by Eleanor Chambers

The evening ended with the monthly prize draw and drinks in the Midnight Bell. Thanks to all our volunteer team who make the event happen and finally thanks to main sponsors iSource IT, Piksel, Callcredit and NewRedo and to our prize sponsors O'Reilly, JetBRAINS, Manning, Wrox and PluralSight.

See you in July
The Agile Yorkshire Team

Geoff Watts on Servant Leadership & Stew Able on Architecture and Agile

posted 19 May 2014, 16:10 by Neil McLaughlin   [ updated 3 Dec 2014, 02:47 by Royd Brayshay ]

Our main speaker this month was Geoff Watts, giving some Agile Yorkshire airtime back to Scrum. Opting to forgo the usual accompaniment of slides, Geoff's face and flipchart were what we expected to look at for the next hour. Not so, we soon learned, as Geoff's presentation quickly had us on our feet lobbing rubber balls about to the tune of a last-letter-first game, a technique he uses to encourage team members to interact with each other more effectively.

As an experienced Scrum Master, Geoff has observed many teams working well (and not so well) together. No two teams are going to be the same, but there are predictable areas to consider when trying to get the best out of any one of them. A certain level of informality helps, Geoff suggests, as people tend to feel more accountable to those they know better. To this end, in another game we tried to make connections between members of small teams formed from the Agile Yorkshire audience. The team I was part of learnt that two of its members were connected by injuries sustained dancing to the music of Pulp! A lifelong bond was formed that night.

Geoff highlighted areas often overlooked in considering why a team is failing to meet its targets -- the targets themselves, for example. Too short a sprint and the team can end up too focused on that short-term goal, killing potential creativity and longer-term success. Then again, short sprints can provide a lot of feedback, building a more resilient, responsive team. Geoff's talk showed that there's a lot to consider in building a good Scrum team, and a good servant-leader should help teams to solve their own problems, getting them to figure out what works best for themselves.

Pick of the tweets

  • @Roarkiran Great #AgileYorkshire, thought provoking talks and discussions that carried on in train - jet brains voucher made up for cycling in rain!
  • @ianfnelson @geoffcwatts @agileyorkshire It was a great session, nice to get some interactivity and informality back into proceedings.
  • @northern_tester Servant leaders should go first, showing vulnerability is key to trust. #AgileYorkshire
  • @Scrum_Mistress Focus on creating a great team and you will achieve great things. @agileyorkshire @geoffcwatts
  • @edjannoo Slack allows small regular changes to software architecture #AgileYorkshire
  • @sweavoSo I don't have to wait 2 years for something I don't want? Hell i can give you something in a month you don't want! @agileyorkshire
  • @LeahJoanneShaw Kids in bed, brew made, cusions plumped, hubby at his @agileyorkshire geek club, so tonight i get to control the TV remote! Winner!
more
The other speaker for the evening was Agile Yorkshire regular Stew Able, with his talk entitled 'Architecture and Agile'. Good architecture aims to aid the building of effective software but also to give its developers ease of access to extend the system to which it is applied. It can however quickly become muddied by the need to consider cross-cutting concerns like auditing and logging. 

Stew posits that architecture is everyone's responsibility, and that team members of all levels of ability should be able to make valuable contributions. Questioning why certain patterns exist in the code base can lead to a better end result and shared understanding of the system amongst more people. Different views of the architecture should exist for the different parties involved, to enable as much contribution and understanding of it as possible. Its documentation should be lean and up to date so it is as inviting to read and as relevant as it can be. Stew's talk made it clear that Agile development at its best has architecture as part of the process, as a system's architecture will certainly affect the work taken on by any Agile team. Stew's slides are available here.

The evening ended with the monthly prize draw and drinks in the Midnight Bell. Thanks to all our volunteer team who make the event happen and finally thanks to main sponsors iSource IT, Piksel, Callcredit and NewRedo and to our prize sponsors O'Reilly, JetBRAINS, Manning, Wrox and PluralSight.

Eleanor Chambers

Announcing Piksel as a Sponsor

posted 17 Apr 2014, 01:50 by Royd Brayshay   [ updated 3 Dec 2014, 02:17 ]

Piksel logo
Agile Yorkshire has a new sponsor. Piksel have stepped forward to support the Agile Yorkshire community and hence the agile movement in are region. Agile Yorkshire is only able to run in the way it does, attracting some of the best speakers and developing local industry leadership, through the help of sponsors like Piksel. Here's what Piksel have said...

"Piksel is proud to sponsor Agile Yorkshire -  to support their mission to champion software development in the region and build a centre of excellence. Piksel has an extensive track record in the delivery of OTT Solutions to some of the world’s largest broadcasters and has been involved in some of the earliest pioneering implementations. Customers include; BSkyB, Liberty Global, OSN and 4oD. Delivering the best in OTT solutions, with the expertise to manage even the most complex integrations, Piksel stands with those redefining the frontiers of viewing.
 
Piksel's headquartered in New York with offices worldwide. Established in 2001 the UK Head Office is based in York Science Park. With circa 200 involved in software development and managed services, Piksel is an environment where technical people thrive, where they can be hands on and find variety from the breadth of high profile clients. The company continuously invests in new approaches and strives to improve its delivery processes. Piksel looks to Agile Yorkshire as one source of inspiration in a pragmatic approach to project delivery."

8th April - Jose Casal and Richard Tasker

posted 16 Apr 2014, 16:38 by Neil McLaughlin   [ updated 3 Dec 2014, 02:48 by Royd Brayshay ]

Once again a capacity audience of software delivery professionals, drawn from across the disciplines, came together for the monthly Agile Yorkshire meetup. The number of people arriving early for the great networking opportunity at the start of the evening seems to be increasing and there was already a substantial buzz in the room at 6:30.The main speaker for the evening was Jose Casal (@jose_casal) who, whilst being based in the south east, is a frequent visitor to Yorkshire for engagements with large and medium sized organisations. These organisation typically want some of the kool-aid associated with progressive software development processes but are often typified by islands of agility in more traditional organisational structures.



Jose asserted that, compared to the industrial revolution, the information revolution has barely started and is currently at the “Model T” stage. He posed the hypothesis that in order for organisations to transform to hyperproductivity then the low levels of efficiency of software delivery teams (given as between 1% and 5%) needs to be addressed. 
Jose emphasised the impact of people and culture in the transformation process which itself should be evolutionary not revolutionary. There was a lively debate in the Q&A session around the theme of “slack” and how organisations might best build that into their software delivery process. This debate carried on enthusiastically into the pub where the beers were kindly sponsored by iSourceIT.

Pick of the tweets

Twitter_logo_blue.png         
  • @clem_pickering High utilisation is the enemy of good flow. 100% utilisation = jammed and no capacity to react @jose_casal #AgileYorkshire

  • @stevecooperorg Another interesting concept from @jose_casal - Staff liquidity.

  • @markdkitch Just followed @jose_casal, great talk at @agileyorkshire tonight

  • @OneworksSimon: Interesting discussion about usefulness of defining user acceptance in Gherkin @agileyorkshire

  • @ArdLiath Great talk by @ritasker about BDD @agileyorkshire

  • @RoydBrayshay: Excellent, @ritasker brings live coding back to @agileyorkshire after a while in the wilderness

  • @OneworksSimon Lovely evening again at @agileyorkshire with new chums. two great speakers!

The support slot for the evening was taken up by Richard Tasker (@ritasker) - an exile from across the Pennines who is now resident in Yorkshire. Richard gave a tour of the different flavours of tools available in .NET for driving software development from examples (aka BDD - Behaviour Driven Development ). In the process he also gave a useful overview of the difference between TDD and BDD, the strengths of each and where BDD adds value to software delivery by clarifying requirements through examples which, in turn, can act as living documentation.
The evening ended with the monthly prize draw and drinks in the Midnight Bell. Thanks to all our volunteer team who make the event happen and finally thanks to main sponsors iSource IT, Piksel, Callcredit and NewRedo and to our prize sponsors O'Reilly, JetBRAINS, Manning, Wrox and PluralSight.

See you next month, Neil McLaughlin


1-10 of 36