posted 14 Jul 2010 05:59 by Neil McLaughlin
[
updated 14 Jul 2010 06:01
]
posted 3 Jun 2010 15:26 by Neil McLaughlin
[
updated 14 Jul 2010 06:05
]
Details
Agile software development depends on close collaboration. If we don't trust our team mates or our managers, this can block collaboration on the team. Being able to build trust is an essential skill for agile coaches which is covered in Rachel's Agile Coaching book. Come along to this talk to find out some simple ways that you can start building trust on the teams you work with.
Speaker
Rachel Davies has a wealth of experience through her work coaching agile teams. Her new book "Agile Coaching" shares many practical tips that can help you take your teams to the next level. Rachel supports the agile community as a long-serving director of the non-profit Agile Alliance and as an organiser of many Agile conferences.
Follow Rachel's blog at http://agilecoach.typepad.com/
Lightening Talk
Kiran Singh will also be talking about developer motivation and professional development
|
posted 25 May 2010 08:27 by Neil McLaughlin
[
updated 4 Jun 2010 00:34
]
Main Talk
Andy
Barker, a Technical Specialist in the Business Intelligence development
team at HML in Skipton, will provide an experience report on the team's
journey so far in bringing automated testing to data warehousing using
Fitnesse and dbFit: what has worked, what hasn't, and what is still
proving a challenge. It will include demo's of the tools in action. Lightning Talks
Ashley Moran: Risk management ideas drawn from Waltzing with Bears used on a recent software project leading to happy clients (http://patchspace.co.uk/) Neil McLaughlin: A journey from Google sites to Ruby micro-applications More volunteers welcome! If you want to do a short presentation (~10 mins) on some cool technology you have used or a new approach to developing software then drop an email to ideas@agileyorkshire.org.
|
posted 7 Apr 2010 17:00 by Neil McLaughlin
[
updated 14 Apr 2010 17:33
]
|
|
Have
we got object-orientation all wrong? "Object Thinking" (ISBN
0-7356-1965-4) by David West asserts that we have. Alan Dean explores
this assertion, and demonstrates self-describing objects /
self-evaluating rules with code examples.
http://www.alan-dean.com/about.en.html
|
|
posted 2 Mar 2010 03:28 by Neil McLaughlin
[
updated 9 Apr 2010 09:56
]
[Note: 6:45 start this month only]
Behaviour Driven Development using CucumberWhile tools for Behaviour Driven Development like Rspec in Ruby have
been aimed towards programmers and dealing with classes and objects,
Cucumber is aimed at filling the communication gap between customers,
programmers and testers. In Cucumber we build a personalised plain text
domain language to talk about the applications behaviour that
non-technical users can understand and write. With Ruby mappings we
turn the plain text into executable tests. We'll look at working
outside-in with Cucumber and the importance of having a customer's
business value as a direction,
which helps us drive towards producing the minimal marketable feature.
Looking also at how to use Cucumber with various programming languages.
And some of the challenges of trying to introduce Cucumber into an
agile environment.
 Joseph Wilk is a member of the core development team for Cucumber. He
has been developing for the web for 10 years in both big and small
companies and as an entrepreneur. After stints working with Java and
Python he finally found Ruby. He now spends his time in-between eating
Cucumbers working at songkick.com. Having more fun than is healthy
working as a Software Gardener building web systems and working on open
source projects. He suffers from test obsession and has given up hope
of any treatment. (http://blog.josephwilk.net/about) Agile Business Intelligence TestingAndy
Barker, a Technical Specialist in the Business Intelligence development
team at HML in Skipton, will provide an experience report on the team's
journey so far in bringing automated testing to data warehousing using
Fitnesse and dbFit: what has worked, what hasn't, and what is still
proving a challenge. It will include demo's of the tools in action. |
posted 2 Mar 2010 00:42 by Neil McLaughlin
[
updated 5 Mar 2010 17:04
]
Registration is now full - you can be placed on a reserve list here
Please note the agileyorkshire venue and date are changed for this meeting. See below for details. In the last decade or so we've seen a number
of new ideas added to
the mix to help us effectively design our
software. Patterns help us capture the solutions and
rationale for using them. Refactoring allows us to alter
the design of a system after the code is
written. Agile methods,
in particular Extreme Programming, give us a highly
iterative and evolutionary approach which is particularly well suited to
changing requirements and environments. Martin Fowler has been a
leading voice
in these techniques and will talk about his recent thinking
about how these and other developments affect our
software development.
Martin Fowler in his own words:
I'm an author, speaker, consultant and general loud-mouth on
software development. I concentrate on designing enterprise software -
looking at what makes a good design and what practices are needed to
come up with good design. I've been a pioneer of object-oriented
technology,
refactoring, patterns, agile methodologies, domain modeling, the
Unified Modeling Language (UML), and Extreme Programming. For the last
decade I've worked at ThoughtWorks,
a really rather good system delivery and consulting firm. From http://martinfowler.com/
Where: Upstairs at The Adelphi in Leeds (http://theadelphi.co.uk/) When: Wed, 17th March. Meet at 6:30 for a 7:00 start. Cost: Free
|
posted 28 Jan 2010 22:58 by Neil McLaughlin
[
updated 8 Feb 2010 23:10
]
Got
something cool to show to your peers, some experiences to report or a
discussion you want to have. Submit your idea here.Current proposed topics are: - REST and OpenRasta
- Silverlight
- F#
- Thoughts on Test Driven Development practices
- Behaviour Driven Development
|
posted 11 Jan 2010 11:24 by Neil McLaughlin
[
updated 11 Jan 2010 11:35
]
A social evening.
No fixed agenda but it would be good to get some discussion going around what do we want from the club and where do we want to go with it.
I suspect there will also be some discussion around Lean, Kanban and Systems Thinking.
|
posted 4 Nov 2009 14:32 by Neil McLaughlin
[
updated 15 Dec 2009 15:36
]
- David Joyce, BBC Worldwide, Kaban For Software Engineering
- Peter Camfield, BBC Worldwide, Why do we code?
This meeting will be a special end of year event held at Old Broadcasting House ( http://www.ntileeds.co.uk/old-broadcasting-house/) The evening will run from 6:30 until 9:00 with snacks and drinks provided. Afterwards the conversation will continue as we head down to the German Market at Millennium Square for some Bratwurst and mulled wine.
Kaban For Software Engineering
DetailsKanban focuses on becoming successful, which may lead to being Agile.
Lean is a set of principles that are being applied to software
engineering by a growing number of practitioners. Kanban is a true pull
system implementation in software engineering. The five pillars of
Lean, which Kanban fully implements are pull, continuous flow, customer
value, waste elimination and continuous improvement. The Principles of
Kanban are: to agree a team capacity, to limit WIP (Work in Process) to
that capacity, to pull value through the value stream, and to make both
work and workflow visible. It has proven easy to adopt and lowers resistance to change.
The result is a gradual, incremental approach to change that is empowering for everyone. SpeakerDavid is an agile development manager and coach with 12 years technical
team management and coaching experience, and 20 years software
development experience. In recent years, using Scrum and XP, David has coached onshore and
offshore development teams and successfully launched an internet video
startup from inception to launch. David currently works for BBC
Worldwide as a Development Manager, coaching teams on Scrum, Lean and
Kanban. David is a certified Scrum Master and Lean practitioner. http://leanandkanban.wordpress.com/
Why do we code? DetailsA group activity which explores the motivations for becoming/being software engineers. By understanding what motivates software developers we can learn more about others and ourselves. In particular we can learn what behaviours software developers should avoid, reduce or increase given our understanding. SpeakerPeter has been developing software professionally for the last 12 years. His current role as a software developer and coach is focused on improving the quality of the code developed at BBC Worldwide. http://leftshift.wordpress.com/ Resources from the presentationsSlides
Useful Links from DavidLean software development - Systems Thinking, Mary Poppendieck http://www.informit.com/articles/article.aspx?p=1409811Systems Thinking Cultural change is free http://leanandkanban.wordpress.com/2009/07/09/systems-thinking-cultural-change-is-free/Lean software development - achieving better requirements http://leanandkanban.wordpress.com/2009/06/10/lean-software-development-achieving-better-requirements/High level overview of Systems Thinking, Agile and Real Options for the executive level http://leanandkanban.wordpress.com/2009/09/26/systems-thinking-real-options-agile-principles/My talk which was filmed, coming soon http://skillsmatter.com/podcast/agile-scrum/a-journey-to-systemic-improvement-962Kanban training session http://skillsmatter.com/podcast/agile-scrum/kanban-for-software-engineering-and-kanban-open-spaceUseful links from PeteDan North - creator of Behaviour Driven Development explains Features and Scenarios including the Given - When - Then format http://dannorth.net/whats-in-a-storyThis one focuses on a understanding TDD and the reasons for creating BDD http://dannorth.net/introducing-bddHe also has a parable on metrics http://dannorth.net/2009/11/the-lady-in-the-taxi-a-parable-of-metricsHere a couple of links on Feature Injection - A technique that builds on Dan's original idea http://www.limitedwipsociety.org/tag/feature-injection/
Photos from "Why Do We Code" sessionhttp://tweetphoto.com/6155393
|
posted 14 Oct 2009 09:25 by Neil McLaughlin
[
updated 4 Nov 2009 14:49
]
Why is it so difficult to talk to customers? Why do managers often end
up making unrealistic demands on developers and encouraging them to
make promises that they can't keep? Why do so many software projects
end up in angry exchanges of accusation and counter accusation? Can
any of this be explained? Can anything be done to make it better?
Researchers at the "Harvard Negotiation Project" claim that a great
deal can be done to make things better. By understanding the structure
of "difficult conversations" we can be made aware of the various
points at which things can go badly wrong and sometimes avoid them. By
understanding our own contribution to the problem we can adopt
strategies that give us a chance to actually improve a situation.
Using as examples a particularly "difficult" conversation about the
development of a website that I overheard in a cafe, and my own
experiences in developing software over the last 15 years, I'd like to
explore how understanding the nature of "difficult conversations" and
some other basic negotiation strategies can help anybody involved in
the business of developing software.
Suitable for:
Suitable for anybody involved in the process of developing, managing
or commissioning software. Speaker
Mark Stringer is a trainer, coach and consultant in the use of Agile
methods. He's particularly interested in exploring project management
methods that emphasise the human nature of project management, because
he thinks they might actually work. ( http://www.agile-lab.co.uk/2007/06/agile-lab-people.html)
|
|