- 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